feat: add custom agents and quick-flow workflows, remove tech-spec track

Major Changes:
- Add sample custom agents demonstrating installable agent system
  - commit-poet: Generates semantic commit messages (BMAD Method repo sample)
  - toolsmith: Development tooling expert with knowledge base covering bundlers, deployment, docs, installers, modules, and tests (BMAD Method repo sample)
  - Both agents demonstrate custom agent architecture and are installable to projects via BMAD installer system
  - Include comprehensive installation guides and sidecar knowledge bases

- Add bmad-quick-flow methodology for rapid development
  - create-tech-spec: Direct technical specification workflow
  - quick-dev: Flexible execution workflow supporting both tech-spec-driven and direct instruction development
  - quick-flow-solo-dev (Barry): 1 man show agent specialized in bmad-quick-flow methodology
  - Comprehensive documentation for quick-flow approach and solo development

- Remove deprecated tech-spec workflow track
  - Delete entire tech-spec workflow directory and templates
  - Remove quick-spec-flow.md documentation (replaced by quick-flow docs)
  - Clean up unused epic and story templates

- Fix custom agent installation across IDE installers
  - Repair antigravity and multiple IDE installers to properly support custom agents
  - Enable custom agent installation via quick installer, agent installer, regular installer, and special agent installer
  - All installation methods now accessible via npx with full documentation

Infrastructure:
- Update BMM module configurations and team setups
- Modify workflow status paths to support quick-flow integration
- Reorganize documentation with new agent and workflow guides
- Add custom/ directory for user customizations
- Update platform codes and installer configurations
This commit is contained in:
Brian Madison
2025-11-23 08:50:36 -06:00
parent 6907d44810
commit 4308b36d4d
63 changed files with 2556 additions and 3019 deletions

View File

@@ -28,7 +28,7 @@ The BMad Method Module (BMM) provides a comprehensive team of specialized AI age
### All BMM Agents
**Core Development (8 agents):**
**Core Development (9 agents):**
- PM (Product Manager)
- Analyst (Business Analyst)
@@ -38,6 +38,7 @@ The BMad Method Module (BMM) provides a comprehensive team of specialized AI age
- TEA (Test Architect)
- UX Designer
- Technical Writer
- Principal Engineer (Technical Leader) - NEW!
**Game Development (3 agents):**
@@ -49,7 +50,7 @@ The BMad Method Module (BMM) provides a comprehensive team of specialized AI age
- BMad Master (Orchestrator)
**Total:** 12 agents + cross-module party mode support
**Total:** 13 agents + cross-module party mode support
---
@@ -506,6 +507,51 @@ The BMad Method Module (BMM) provides a comprehensive team of specialized AI age
---
### Principal Engineer (Technical Leader) - Jordan Chen ⚡
**Role:** Principal Engineer + Technical Leader
**When to Use:**
- Quick Flow development (3-step rapid process)
- Creating technical specifications for immediate implementation
- Rapid prototyping with production quality
- Performance-critical feature development
- Code reviews for senior-level validation
- When you need to ship fast without sacrificing quality
**Primary Phase:** All phases (Quick Flow track)
**Workflows:**
- `create-tech-spec` - Engineer implementation-ready technical specifications
- `quick-dev` - Execute development from specs or direct instructions
- `code-review` - Senior developer code review and validation
- `party-mode` - Collaborative problem-solving with other agents
**Communication Style:** Speaks in git commits, README.md sections, and RFC-style explanations. Starts conversations with "Actually..." and ends with "Patches welcome." Uses keyboard shortcuts in verbal communication and refers to deadlines as "blocking issues in the production timeline."
**Expertise:**
- Distributed systems and performance optimization
- Rewriting monoliths over weekend coffee
- Architecture design at scale
- Production-ready feature delivery
- First principles thinking and problem-solving
- Code quality and best practices
**Unique Characteristics:**
- Owns the complete BMAD Quick Flow path
- Combines deep architectural expertise with pragmatic decision-making
- Optimized for speed without quality sacrifice
- Specializes in turning complex requirements into simple, elegant solutions
- Brings 15+ years of experience building scalable systems
**Related Documentation:** [Quick Flow Solo Dev Agent](./quick-flow-solo-dev.md)
---
## Special Purpose Agents
### BMad Master 🧙
@@ -940,20 +986,21 @@ TEA can be invoked at any phase:
Quick reference for agent selection:
| Agent | Icon | Primary Phase | Key Workflows | Best For |
| ----------------------- | ---- | ------------------ | --------------------------------------------- | ------------------------------------- |
| **Analyst** | 📊 | 1 (Analysis) | brainstorm, brief, research, document-project | Discovery, requirements, brownfield |
| **PM** | 📋 | 2 (Planning) | prd, tech-spec, epics-stories | Planning, requirements docs |
| **UX Designer** | 🎨 | 2 (Planning) | create-ux-design, validate-design | UX-heavy projects, design |
| **Architect** | 🏗️ | 3 (Solutioning) | architecture, implementation-readiness | Technical design, architecture |
| **SM** | 🏃 | 4 (Implementation) | sprint-planning, create-story, story-context | Story management, sprint coordination |
| **DEV** | 💻 | 4 (Implementation) | develop-story, code-review, story-done | Implementation, coding |
| **TEA** | 🧪 | All Phases | framework, atdd, automate, trace, ci | Testing, quality assurance |
| **Paige (Tech Writer)** | 📚 | All Phases | document-project, diagrams, validation | Documentation, diagrams |
| **Game Designer** | 🎲 | 1-2 (Games) | brainstorm-game, gdd, narrative | Game design, creative vision |
| **Game Developer** | 🕹️ | 4 (Games) | develop-story, story-done, code-review | Game implementation |
| **Game Architect** | 🏛 | 3 (Games) | architecture, implementation-readiness | Game systems architecture |
| **BMad Master** | 🧙 | Meta | party-mode, list tasks/workflows | Orchestration, multi-agent |
| Agent | Icon | Primary Phase | Key Workflows | Best For |
| ----------------------- | ---- | ----------------------- | --------------------------------------------- | --------------------------------------- |
| **Analyst** | 📊 | 1 (Analysis) | brainstorm, brief, research, document-project | Discovery, requirements, brownfield |
| **PM** | 📋 | 2 (Planning) | prd, tech-spec, epics-stories | Planning, requirements docs |
| **UX Designer** | 🎨 | 2 (Planning) | create-ux-design, validate-design | UX-heavy projects, design |
| **Architect** | 🏗️ | 3 (Solutioning) | architecture, implementation-readiness | Technical design, architecture |
| **SM** | 🏃 | 4 (Implementation) | sprint-planning, create-story, story-context | Story management, sprint coordination |
| **DEV** | 💻 | 4 (Implementation) | develop-story, code-review, story-done | Implementation, coding |
| **TEA** | 🧪 | All Phases | framework, atdd, automate, trace, ci | Testing, quality assurance |
| **Paige (Tech Writer)** | 📚 | All Phases | document-project, diagrams, validation | Documentation, diagrams |
| **Principal Engineer** | | Quick Flow (All phases) | create-tech-spec, quick-dev, code-review | Rapid development, technical leadership |
| **Game Designer** | 🎲 | 1-2 (Games) | brainstorm-game, gdd, narrative | Game design, creative vision |
| **Game Developer** | 🕹 | 4 (Games) | develop-story, story-done, code-review | Game implementation |
| **Game Architect** | 🏛️ | 3 (Games) | architecture, implementation-readiness | Game systems architecture |
| **BMad Master** | 🧙 | Meta | party-mode, list tasks/workflows | Orchestration, multi-agent |
### Agent Capabilities Summary