bmad-method 6.0.0-alpha.12 → 6.0.0-alpha.14

package/src/modules/bmm/agents/tech-writer.agent.yaml

@@ -12,32 +12,19 @@ agent:
     role: Technical Documentation Specialist + Knowledge Curator
     identity: Experienced technical writer expert in CommonMark, DITA, OpenAPI. Master of clarity - transforms complex concepts into accessible structured documentation.
     communication_style: "Patient educator who explains like teaching a friend. Uses analogies that make complex simple, celebrates clarity when it shines."
-    principles: Documentation is teaching. Every doc helps someone accomplish a task. Clarity above all. Docs are living artifacts that evolve with code. Know when to simplify vs when to be detailed.
+    principles: |
+      - Documentation is teaching. Every doc helps someone accomplish a task. Clarity above all.
+      - Docs are living artifacts that evolve with code. Know when to simplify vs when to be detailed.
 
   critical_actions:
-    - "CRITICAL: Load COMPLETE file {project-root}/{bmad_folder}/bmm/workflows/techdoc/documentation-standards.md into permanent memory and follow ALL rules within"
+    - "CRITICAL: Load COMPLETE file {project-root}/{bmad_folder}/bmm/data/documentation-standards.md into permanent memory and follow ALL rules within"
+    - "Find if this exists, if it does, always treat it as the bible I plan and execute against: `**/project-context.md`"
 
   menu:
     - trigger: document-project
       workflow: "{project-root}/{bmad_folder}/bmm/workflows/document-project/workflow.yaml"
       description: Comprehensive project documentation (brownfield analysis, architecture scanning)
 
-    - trigger: create-api-docs
-      workflow: "todo"
-      description: Create API documentation with OpenAPI/Swagger standards
-
-    - trigger: create-architecture-docs
-      workflow: "todo"
-      description: Create architecture documentation with diagrams and ADRs
-
-    - trigger: create-user-guide
-      workflow: "todo"
-      description: Create user-facing guides and tutorials
-
-    - trigger: audit-docs
-      workflow: "todo"
-      description: Review documentation quality and suggest improvements
-
     - trigger: generate-mermaid
       action: "Create a Mermaid diagram based on user description. Ask for diagram type (flowchart, sequence, class, ER, state, git) and content, then generate properly formatted Mermaid syntax following CommonMark fenced code block standards."
       description: Generate Mermaid diagrams (architecture, sequence, flow, ER, class, state)
@@ -67,11 +54,11 @@ agent:
       description: Create clear technical explanations with examples
 
     - trigger: standards-guide
-      action: "Display the complete documentation standards from {project-root}/{bmad_folder}bmm/workflows/techdoc/documentation-standards.md in a clear, formatted way for the user."
+      action: "Display the complete documentation standards from {project-root}/{bmad_folder}bmm/data/documentation-standards.md in a clear, formatted way for the user."
       description: Show BMAD documentation standards reference (CommonMark, Mermaid, OpenAPI)
 
     - trigger: party-mode
-      workflow: "{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.yaml"
+      exec: "{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md"
       description: Bring the whole team in to chat with other expert agents from the party
 
     - trigger: advanced-elicitation

package/src/modules/bmm/agents/ux-designer.agent.yaml

@@ -12,21 +12,23 @@ agent:
     role: User Experience Designer + UI Specialist
     identity: Senior UX Designer with 7+ years creating intuitive experiences across web and mobile. Expert in user research, interaction design, AI-assisted tools.
     communication_style: "Paints pictures with words, telling user stories that make you FEEL the problem. Empathetic advocate with creative storytelling flair."
-    principles: Every decision serves genuine user needs. Start simple evolve through feedback. Balance empathy with edge case attention. AI tools accelerate human-centered design. Data-informed but always creative.
+    principles: |
+      - Every decision serves genuine user needs
+      - Start simple, evolve through feedback
+      - Balance empathy with edge case attention
+      - AI tools accelerate human-centered design
+      - Data-informed but always creative
 
-  menu:
-    - trigger: workflow-status
-      workflow: "{project-root}/{bmad_folder}/bmm/workflows/workflow-status/workflow.yaml"
-      description: Check workflow status and get recommendations (START HERE!)
+  critical_actions:
+    - "Find if this exists, if it does, always treat it as the bible I plan and execute against: `**/project-context.md`"
 
+  menu:
     - trigger: create-ux-design
-      workflow: "{project-root}/{bmad_folder}/bmm/workflows/2-plan-workflows/create-ux-design/workflow.yaml"
-      description: Conduct Design Thinking Workshop to Define the User Specification
+      exec: "{project-root}/{bmad_folder}/bmm/workflows/2-plan-workflows/create-ux-design/workflow.md"
+      description: Generate a UX Design and UI Plan from a PRD (Recommended before creating Architecture)
 
     - trigger: validate-design
       validate-workflow: "{project-root}/{bmad_folder}/bmm/workflows/2-plan-workflows/create-ux-design/workflow.yaml"
-      checklist: "{project-root}/{bmad_folder}/bmm/workflows/2-plan-workflows/create-ux-design/checklist.md"
-      document: "{output_folder}/ux-spec.md"
       description: Validate UX Specification and Design Artifacts
 
     - trigger: create-excalidraw-wireframe
@@ -34,7 +36,7 @@ agent:
       description: Create website or app wireframe (Excalidraw)
 
     - trigger: party-mode
-      workflow: "{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.yaml"
+      exec: "{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md"
       description: Bring the whole team in to chat with other expert agents from the party
 
     - trigger: advanced-elicitation

package/src/modules/bmm/data/README.md

@@ -0,0 +1,29 @@
+# BMM Module Data
+
+This directory contains module-specific data files used by BMM agents and workflows.
+
+## Files
+
+### `project-context-template.md`
+
+Template for project-specific brainstorming context. Used by:
+
+- Analyst agent `brainstorm-project` command
+- Core brainstorming workflow when called with context
+
+### `documentation-standards.md`
+
+BMAD documentation standards and guidelines. Used by:
+
+- Tech Writer agent (critical action loading)
+- Various documentation workflows
+- Standards validation and review processes
+
+## Purpose
+
+Separates module-specific data from core workflow implementations, maintaining clean architecture:
+
+- Core workflows remain generic and reusable
+- Module-specific templates and standards are properly scoped
+- Data files can be easily maintained and updated
+- Clear separation of concerns between core and module functionality

package/src/modules/bmm/data/project-context-template.md

@@ -0,0 +1,40 @@
+# Project Brainstorming Context Template
+
+## Project Focus Areas
+
+This brainstorming session focuses on software and product development considerations:
+
+### Key Exploration Areas
+
+- **User Problems and Pain Points** - What challenges do users face?
+- **Feature Ideas and Capabilities** - What could the product do?
+- **Technical Approaches** - How might we build it?
+- **User Experience** - How will users interact with it?
+- **Business Model and Value** - How does it create value?
+- **Market Differentiation** - What makes it unique?
+- **Technical Risks and Challenges** - What could go wrong?
+- **Success Metrics** - How will we measure success?
+
+### Integration with Project Workflow
+
+Brainstorming results will feed into:
+
+- Product Briefs for initial product vision
+- PRDs for detailed requirements
+- Technical Specifications for architecture plans
+- Research Activities for validation needs
+
+### Expected Outcomes
+
+Capture:
+
+1. Problem Statements - Clearly defined user challenges
+2. Solution Concepts - High-level approach descriptions
+3. Feature Priorities - Categorized by importance and feasibility
+4. Technical Considerations - Architecture and implementation thoughts
+5. Next Steps - Actions needed to advance concepts
+6. Integration Points - Connections to downstream workflows
+
+---
+
+_Use this template to provide project-specific context for brainstorming sessions. Customize the focus areas based on your project's specific needs and stage._

package/src/modules/bmm/docs/README.md

@@ -32,11 +32,18 @@ Understanding how BMM adapts to your needs:
   - Documentation requirements per track
   - Planning workflow routing
 
-- **[Quick Spec Flow](./quick-spec-flow.md)** - Fast-track workflow for Quick Flow track (26 min read)
-  - Bug fixes and small features
-  - Rapid prototyping approach
-  - Auto-detection of stack and patterns
-  - Minutes to implementation
+- **[BMAD Quick Flow](./bmad-quick-flow.md)** - Fast-track development workflow (32 min read)
+  - 3-step process: spec → dev → optional review
+  - Perfect for bug fixes and small features
+  - Rapid prototyping with production quality
+  - Hours to implementation, not days
+  - Barry (Quick Flow Solo Dev) agent owned
+
+- **[Quick Flow Solo Dev Agent](./quick-flow-solo-dev.md)** - Elite solo developer for rapid development (18 min read)
+  - Barry is an elite developer who thrives on autonomous execution
+  - Lives and breathes the BMAD Quick Flow workflow
+  - Takes projects from concept to deployment with ruthless efficiency
+  - No handoffs, no delays - just pure focused development
 
 ---
 
@@ -92,11 +99,12 @@ Essential reference materials:
 → Then review [Scale Adaptive System](./scale-adaptive-system.md) to understand tracks
 
 **Fix a bug or add small feature**
-→ Go directly to [Quick Spec Flow](./quick-spec-flow.md)
+→ Go to [BMAD Quick Flow](./bmad-quick-flow.md) for rapid development
+→ Or use [Quick Flow Solo Dev](./quick-flow-solo-dev.md) directly
 
 **Work with existing codebase (brownfield)**
 → Read [Brownfield Development Guide](./brownfield-guide.md)
-→ Pay special attention to Phase 0 documentation requirements
+→ Pay special attention to documentation requirements for brownfield projects
 
 **Understand planning tracks and methodology**
 → See [Scale Adaptive System](./scale-adaptive-system.md)
@@ -131,6 +139,9 @@ Comprehensive documentation for all BMM workflows organized by phase:
   - Complete story lifecycle
   - One-story-at-a-time discipline
 
+<<<<<<< Updated upstream
+<<<<<<< Updated upstream
+
 - **[Testing & QA Workflows](./test-architecture.md)** - Comprehensive quality assurance (1,420 lines)
   - Test strategy, automation, quality gates
   - TEA agent and test healing
@@ -138,6 +149,14 @@ Comprehensive documentation for all BMM workflows organized by phase:
 
 **Total: 34 workflows documented across all phases**
 
+=======
+
+> > > > > > > Stashed changes
+
+=======
+
+> > > > > > > Stashed changes
+
 ### Advanced Workflow References
 
 For detailed technical documentation on specific complex workflows:
@@ -162,10 +181,21 @@ Quality assurance guidance:
 
 <!-- Test Architect documentation to be added -->
 
+<<<<<<< Updated upstream
+
+<<<<<<< Updated upstream
+
 - Test design workflows
 - Quality gates
 - Risk assessment
-- NFR validation
+- # NFR validation
+  =======
+  > > > > > > > Stashed changes
+  - Test design workflows
+  - Quality gates
+  - Risk assessment
+  - NFR validation
+    > > > > > > > Stashed changes
 
 ---
 
@@ -209,11 +239,13 @@ flowchart TD
 
     QS --> DECIDE{What are you building?}
 
-    DECIDE -->|Bug fix or<br/>small feature| QSF[Quick Spec Flow]
+    DECIDE -->|Bug fix or<br/>small feature| QF[BMAD Quick Flow]
+    DECIDE -->|Need rapid<br/>development| PE[Principal Engineer]
     DECIDE -->|New project| SAS[Scale Adaptive System]
     DECIDE -->|Existing codebase| BF[Brownfield Guide]
 
-    QSF --> IMPL[Implementation]
+    QF --> IMPL[Implementation]
+    PE --> IMPL
     SAS --> IMPL
     BF --> IMPL
 
@@ -222,6 +254,8 @@ flowchart TD
     style START fill:#bfb,stroke:#333,stroke-width:2px,color:#000
     style QS fill:#bbf,stroke:#333,stroke-width:2px,color:#000
     style DECIDE fill:#ffb,stroke:#333,stroke-width:2px,color:#000
+    style QF fill:#e1f5fe,stroke:#333,stroke-width:2px,color:#000
+    style PE fill:#fff3e0,stroke:#333,stroke-width:2px,color:#000
     style IMPL fill:#f9f,stroke:#333,stroke-width:2px,color:#000
 ```
 

package/src/modules/bmm/docs/agents-guide.md

@@ -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
 
 ---
 
@@ -75,8 +76,7 @@ The BMad Method Module (BMM) provides a comprehensive team of specialized AI age
 - `create-prd` - Create PRD for Level 2-4 projects (creates FRs/NFRs only)
 - `tech-spec` - Quick spec for Level 0-1 projects
 - `create-epics-and-stories` - Break PRD into implementable pieces (runs AFTER architecture)
-- `validate-prd` - Validate PRD completeness
-- `validate-tech-spec` - Validate Technical Specification
+- `implementation-readiness` - Validate PRD + Architecture + Epics + UX (optional)
 - `correct-course` - Handle mid-project changes
 - `workflow-init` - Initialize workflow tracking
 
@@ -102,7 +102,6 @@ The BMad Method Module (BMM) provides a comprehensive team of specialized AI age
 - Creating product briefs for strategic planning
 - Conducting research (market, technical, competitive)
 - Documenting existing projects (brownfield)
-- Phase 0 documentation needs
 
 **Primary Phase:** Phase 1 (Analysis)
 
@@ -136,7 +135,7 @@ The BMad Method Module (BMM) provides a comprehensive team of specialized AI age
 - Creating system architecture for Level 2-4 projects
 - Making technical design decisions
 - Validating architecture documents
-- Validating readiness for implementation phase (Phase 3→4 transition)
+- Validating readiness for implementation phase (Phase 3 to Phase 4 transition)
 - Course correction during implementation
 
 **Primary Phase:** Phase 3 (Solutioning)
@@ -145,8 +144,7 @@ The BMad Method Module (BMM) provides a comprehensive team of specialized AI age
 
 - `workflow-status` - Check what to do next
 - `create-architecture` - Produce a Scale Adaptive Architecture
-- `validate-architecture` - Validate architecture document
-- `implementation-readiness` - Validate readiness for Phase 4
+- `implementation-readiness` - Validate PRD + Architecture + Epics + UX (optional)
 
 **Communication Style:** Comprehensive yet pragmatic. Uses architectural metaphors. Balances technical depth with accessibility. Connects decisions to business value.
 
@@ -182,13 +180,8 @@ The BMad Method Module (BMM) provides a comprehensive team of specialized AI age
 
 - `workflow-status` - Check what to do next
 - `sprint-planning` - Initialize `sprint-status.yaml` tracking
-- `epic-tech-context` - Optional epic-specific technical context
-- `validate-epic-tech-context` - Validate epic technical context
 - `create-story` - Draft next story from epic
 - `validate-create-story` - Independent story validation
-- `story-context` - Assemble dynamic technical context XML
-- `validate-story-context` - Validate story context
-- `story-ready-for-dev` - Mark story ready without context generation
 - `epic-retrospective` - Post-epic review
 - `correct-course` - Handle changes during implementation
 
@@ -230,7 +223,6 @@ The BMad Method Module (BMM) provides a comprehensive team of specialized AI age
   - Repository docs reference
   - MCP server best practices
   - Web search fallback
-- `story-done` - Mark story complete and advance queue
 
 **Communication Style:** Succinct and checklist-driven. Cites file paths and acceptance criteria IDs. Only asks questions when inputs are missing.
 
@@ -321,7 +313,7 @@ The BMad Method Module (BMM) provides a comprehensive team of specialized AI age
 **Workflows:**
 
 - `workflow-status` - Check what to do next
-- `create-design` - Conduct design thinking workshop to define UX specification with:
+- `create-ux-design` - Conduct design thinking workshop to define UX specification with:
   - Visual exploration and generation
   - Collaborative decision-making
   - AI-assisted design tools (v0, Lovable)
@@ -347,7 +339,7 @@ The BMad Method Module (BMM) provides a comprehensive team of specialized AI age
 
 **When to Use:**
 
-- Documenting brownfield projects (Phase 0)
+- Documenting brownfield projects (Documentation prerequisite)
 - Creating API documentation
 - Generating architecture documentation
 - Writing user guides and tutorials
@@ -458,7 +450,6 @@ The BMad Method Module (BMM) provides a comprehensive team of specialized AI age
 
 - `workflow-status` - Check what to do next
 - `develop-story` - Execute Dev Story workflow, implementing tasks and tests
-- `story-done` - Mark story done after DoD complete
 - `code-review` - Perform thorough clean context QA code review on a story
 
 **Communication Style:** Direct and energetic. Execution-focused. Breaks down complex game challenges into actionable steps. Celebrates performance wins.
@@ -491,7 +482,7 @@ The BMad Method Module (BMM) provides a comprehensive team of specialized AI age
 
 - `workflow-status` - Check what to do next
 - `create-architecture` - Game systems architecture
-- `implementation-readiness` - Validate Phase 3→4 transition
+- `implementation-readiness` - Validate Phase 3 to Phase 4 transition
 - `correct-course` - Handle technical changes
 
 **Communication Style:** Calm and measured. Systematic thinking about complex systems. Uses chess metaphors and military strategy. Emphasizes balance and elegance.
@@ -506,6 +497,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 🧙
@@ -604,15 +640,11 @@ Some workflows are available to multiple agents:
 
 Many workflows have optional validation workflows that perform independent review:
 
-| Validation                   | Agent       | Validates                        |
-| ---------------------------- | ----------- | -------------------------------- |
-| `validate-prd`               | PM          | PRD completeness (FRs/NFRs only) |
-| `validate-tech-spec`         | PM          | Technical specification quality  |
-| `validate-architecture`      | Architect   | Architecture document            |
-| `validate-design`            | UX Designer | UX specification and artifacts   |
-| `validate-epic-tech-context` | SM          | Epic technical context           |
-| `validate-create-story`      | SM          | Story draft                      |
-| `validate-story-context`     | SM          | Story context XML                |
+| Validation                 | Agent       | Validates                                  |
+| -------------------------- | ----------- | ------------------------------------------ |
+| `implementation-readiness` | Architect   | PRD + Architecture + Epics + UX (optional) |
+| `validate-design`          | UX Designer | UX specification and artifacts             |
+| `validate-create-story`    | SM          | Story draft                                |
 
 **When to use validation:**
 
@@ -867,13 +899,10 @@ Load the customized agent and verify the changes are reflected in its behavior a
 **Story Development Cycle:**
 
 ```
-1. SM: *epic-tech-context (optional, once per epic)
-2. SM: *create-story
-3. SM: *story-context
-4. DEV: *develop-story
-5. DEV: *code-review
-6. DEV: *story-done
-7. Repeat steps 2-6 for next story
+1. SM: *create-story
+2. DEV: *develop-story
+3. DEV: *code-review
+4. Repeat steps 1-3 for next story
 ```
 
 **Testing Strategy:**
@@ -912,9 +941,8 @@ Agent analyzes project state → recommends next workflow
 
 ```
 Each phase has validation gates:
-- Phase 2→3: validate-prd, validate-tech-spec
-- Phase 3→4: implementation-readiness
-Run validation before advancing
+- Phase 3 to 4: implementation-readiness (validates PRD + Architecture + Epics + UX (optional))
+Run validation before advancing to implementation
 ```
 
 **Course correction:**
@@ -940,20 +968,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-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 management, sprint coordination   |
+| **DEV**                 | 💻   | 4 (Implementation)      | develop-story, code-review                    | 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, 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
 
@@ -1041,10 +1070,8 @@ Quick reference for agent selection:
 
 - [ ] SM: `*sprint-planning` (once)
 - [ ] SM: `*create-story`
-- [ ] SM: `*story-context`
 - [ ] DEV: `*develop-story`
 - [ ] DEV: `*code-review`
-- [ ] DEV: `*story-done`
 
 **Testing Strategy:**