bmad-method 6.0.0-alpha.4 → 6.0.0-alpha.6

package/package.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://json.schemastore.org/package.json",
   "name": "bmad-method",
-  "version": "6.0.0-alpha.4",
+  "version": "6.0.0-alpha.6",
   "description": "Breakthrough Method of Agile AI-driven Development",
   "keywords": [
     "agile",

package/src/core/tasks/workflow.xml

@@ -13,8 +13,7 @@
     <rule n="1">Steps execute in exact numerical order (1, 2, 3...)</rule>
     <rule n="2">Optional steps: Ask user unless #yolo mode active</rule>
     <rule n="3">Template-output tags: Save content → Show user → Get approval before continuing</rule>
-    <rule n="4">Elicit tags: Execute immediately unless #yolo mode (which skips ALL elicitation)</rule>
-    <rule n="5">User must approve each major section before continuing UNLESS #yolo mode active</rule>
+    <rule n="4">User must approve each major section before continuing UNLESS #yolo mode active</rule>
   </WORKFLOW-RULES>
 
   <flow>
@@ -75,14 +74,6 @@
           <action>Display generated content</action>
           <ask>Continue [c] or Edit [e]? WAIT for response</ask>
         </if>
-
-        <if tag="elicit-required">
-          <mandate critical="true">YOU MUST READ the file at {project-root}/bmad/core/tasks/adv-elicit.xml using Read tool BEFORE presenting
-            any elicitation menu</mandate>
-          <action>Load and run task {project-root}/bmad/core/tasks/adv-elicit.xml with current context</action>
-          <action>Show elicitation menu 5 relevant options (list 1-5 options, Continue [c] or Reshuffle [r])</action>
-          <mandate>HALT and WAIT for user selection</mandate>
-        </if>
       </substep>
 
       <substep n="2d" title="Step Completion">
@@ -123,7 +114,6 @@
     </execution>
     <output>
       <tag>template-output - Save content checkpoint</tag>
-      <tag>elicit-required - Trigger enhancement</tag>
       <tag>critical - Cannot be skipped</tag>
       <tag>example - Show example output</tag>
     </output>

package/src/modules/bmb/workflows/audit-workflow/instructions.md

@@ -161,7 +161,7 @@
     <action if="condition met">Do something</action>
     ```
 
-    <action>Scan instructions.md for nested tag references using pattern: &lt;(action|ask|check|template-output|invoke-workflow|goto|step|elicit-required)&gt; within text content</action>
+    <action>Scan instructions.md for nested tag references using pattern: &lt;(action|ask|check|template-output|invoke-workflow|invoke-task|goto|step)&gt; within text content</action>
     <action>Record any instances of nested tag references with line numbers</action>
     <action>Scan instructions.md for conditional execution antipattern: self-closing check tags</action>
     <action>Detect pattern: `&lt;check&gt;.*&lt;/check&gt;` on single line (self-closing check)</action>

package/src/modules/bmm/README.md

@@ -34,7 +34,7 @@ bmm/
 
 ### Agent Roster
 
-**Core Development:** PM, Analyst, Architect, SM, DEV, TEA, UX Designer, Paige
+**Core Development:** PM, Analyst, Architect, SM, DEV, TEA, UX Designer, Technical Writer
 **Game Development:** Game Designer, Game Developer, Game Architect
 **Orchestration:** BMad Master (from Core)
 

package/src/modules/bmm/_module-installer/install-config.yaml

@@ -49,6 +49,11 @@ dev_story_location:
   default: "docs/stories"
   result: "{project-root}/{value}"
 
+install_user_docs:
+  prompt: "Install user documentation to project directory?"
+  default: true
+  result: "{value}"
+
 # TEA Agent Configuration
 tea_use_mcp_enhancements:
   prompt: "Enable Playwright MCP capabilities (healing, exploratory, verification)?"

package/src/modules/bmm/agents/architect.agent.yaml

@@ -22,10 +22,6 @@ agent:
       workflow: "{project-root}/bmad/bmm/workflows/workflow-status/workflow.yaml"
       description: Check workflow status and get recommendations
 
-    - trigger: correct-course
-      workflow: "{project-root}/bmad/bmm/workflows/4-implementation/correct-course/workflow.yaml"
-      description: Course Correction Analysis
-
     - trigger: create-architecture
       workflow: "{project-root}/bmad/bmm/workflows/3-solutioning/architecture/workflow.yaml"
       description: Produce a Scale Adaptive Architecture

package/src/modules/bmm/agents/game-dev.agent.yaml

@@ -20,20 +20,16 @@ agent:
   menu:
     - trigger: workflow-status
       workflow: "{project-root}/bmad/bmm/workflows/workflow-status/workflow.yaml"
-      description: Check workflow status and get recommendations
+      description: "Check workflow status and get recommendations"
 
-    - trigger: create-story
-      workflow: "{project-root}/bmad/bmm/workflows/4-implementation/create-story/workflow.yaml"
-      description: Create Development Story
-
-    - trigger: dev-story
+    - trigger: develop-story
       workflow: "{project-root}/bmad/bmm/workflows/4-implementation/dev-story/workflow.yaml"
-      description: Implement Story with Context
+      description: "Execute Dev Story workflow, implementing tasks and tests, or performing updates to the story"
+
+    - trigger: story-done
+      workflow: "{project-root}/bmad/bmm/workflows/4-implementation/story-done/workflow.yaml"
+      description: "Mark story done after DoD complete"
 
     - trigger: code-review
       workflow: "{project-root}/bmad/bmm/workflows/4-implementation/code-review/workflow.yaml"
-      description: Review Story Implementation
-
-    - trigger: retro
-      workflow: "{project-root}/bmad/bmm/workflows/4-implementation/retrospective/workflow.yaml"
-      description: Sprint Retrospective
+      description: "Perform a thorough clean context QA code review on a story flagged Ready for Review"

package/src/modules/bmm/agents/sm.agent.yaml

@@ -31,7 +31,7 @@ agent:
 
     - trigger: epic-tech-context
       workflow: "{project-root}/bmad/bmm/workflows/4-implementation/epic-tech-context/workflow.yaml"
-      description: (Optional) Use the PRD and Architecture to create a Tech-Spec for a specific epic
+      description: (Optional) Use the PRD and Architecture to create a Epic-Tech-Spec for a specific epic
 
     - trigger: validate-epic-tech-context
       validate-workflow: "{project-root}/bmad/bmm/workflows/4-implementation/epic-tech-context/workflow.yaml"

package/src/modules/bmm/agents/{paige.agent.yaml → tech-writer.agent.yaml}

@@ -1,10 +1,10 @@
-# Paige - Documentation Guide Agent Definition
+# Technical Writer - Documentation Guide Agent Definition
 
 agent:
   metadata:
-    id: bmad/bmm/agents/paige.md
-    name: Paige
-    title: Documentation Guide
+    id: bmad/bmm/agents/tech-writer.md
+    name: paige
+    title: Technical Writer
     icon: 📚
     module: bmm
 

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

@@ -23,12 +23,12 @@ Complete guides for the BMad Method Module (BMM) - AI-powered agile development
 Understanding how BMM adapts to your needs:
 
 - **[Scale Adaptive System](./scale-adaptive-system.md)** - How BMM adapts to project size and complexity (42 min read)
-  - The five complexity levels (0-4)
-  - Automatic level detection
-  - Documentation requirements per level
+  - Three planning tracks (Quick Flow, BMad Method, Enterprise Method)
+  - Automatic track recommendation
+  - Documentation requirements per track
   - Planning workflow routing
 
-- **[Quick Spec Flow](./quick-spec-flow.md)** - Fast-track workflow for Level 0-1 projects (26 min read)
+- **[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
@@ -36,7 +36,7 @@ Understanding how BMM adapts to your needs:
 
 ---
 
-## 🤖 Agents & Collaboration
+## 🤖 Agents and Collaboration
 
 Complete guide to BMM's AI agent team:
 
@@ -62,7 +62,7 @@ Comprehensive guide for brownfield development:
 
 - **[Brownfield Development Guide](./brownfield-guide.md)** - Complete guide for existing codebases (53 min read)
   - Documentation phase strategies
-  - Level detection for brownfield
+  - Track selection for brownfield
   - Integration with existing patterns
   - Phase-by-phase workflow guidance
   - Common scenarios and troubleshooting
@@ -86,7 +86,7 @@ Essential reference materials:
 
 **Build something new (greenfield)**
 → Start with [Quick Start Guide](./quick-start.md)
-→ Then review [Scale Adaptive System](./scale-adaptive-system.md) to understand levels
+→ 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)
@@ -95,7 +95,7 @@ Essential reference materials:
 → Read [Brownfield Development Guide](./brownfield-guide.md)
 → Pay special attention to Phase 0 documentation requirements
 
-**Understand project complexity levels**
+**Understand planning tracks and methodology**
 → See [Scale Adaptive System](./scale-adaptive-system.md)
 
 **Find specific commands or answers**
@@ -114,12 +114,12 @@ Comprehensive documentation for all BMM workflows organized by phase:
 
 - **[Phase 2: Planning Workflows](./workflows-planning.md)** - Scale-adaptive planning (967 lines)
   - prd, tech-spec, gdd, narrative, ux
-  - Level 0-4 planning approach
+  - Track-based planning approach (Quick Flow, BMad Method, Enterprise Method)
   - Which planning workflow to use
 
 - **[Phase 3: Solutioning Workflows](./workflows-solutioning.md)** - Architecture and validation (638 lines)
   - architecture, solutioning-gate-check
-  - Required for Level 3-4 projects
+  - Required for BMad Method and Enterprise Method tracks
   - Preventing agent conflicts
 
 - **[Phase 4: Implementation Workflows](./workflows-implementation.md)** - Sprint-based development (1,634 lines)
@@ -127,7 +127,7 @@ Comprehensive documentation for all BMM workflows organized by phase:
   - Complete story lifecycle
   - One-story-at-a-time discipline
 
-- **[Testing & QA Workflows](./workflows-testing.md)** - Comprehensive quality assurance (1,420 lines)
+- **[Testing & QA Workflows](./test-architecture.md)** - Comprehensive quality assurance (1,420 lines)
   - Test strategy, automation, quality gates
   - TEA agent and test healing
   - BMad-integrated vs standalone modes
@@ -152,15 +152,16 @@ For detailed technical documentation on specific complex workflows:
 
 ---
 
-## 🧪 Testing & Quality
+## 🧪 Testing and Quality
 
 Quality assurance guidance:
 
-- **[Test Architect Guide](../testarch/README.md)** - Comprehensive testing strategy
-  - Test design workflows
-  - Quality gates
-  - Risk assessment
-  - NFR validation
+<!-- Test Architect documentation to be added -->
+
+- Test design workflows
+- Quality gates
+- Risk assessment
+- NFR validation
 
 ---
 
@@ -178,7 +179,7 @@ Understanding BMM components:
 
 ## 🌐 External Resources
 
-### Community & Support
+### Community and Support
 
 - **[Discord Community](https://discord.gg/gk8jAdXWmj)** - Get help from the community (#general-dev, #bugs-issues)
 - **[GitHub Issues](https://github.com/bmad-code-org/BMAD-METHOD/issues)** - Report bugs or request features

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

@@ -37,7 +37,7 @@ The BMad Method Module (BMM) provides a comprehensive team of specialized AI age
 - DEV (Developer)
 - TEA (Test Architect)
 - UX Designer
-- Paige (Documentation Guide)
+- Technical Writer
 
 **Game Development (3 agents):**
 
@@ -144,14 +144,9 @@ The BMad Method Module (BMM) provides a comprehensive team of specialized AI age
 **Workflows:**
 
 - `workflow-status` - Check what to do next
-- `create-architecture` - Decision-focused architecture with:
-  - Starter template intelligence
-  - Novel pattern design
-  - Implementation patterns for agent consistency
-  - Adaptive facilitation (beginner/expert)
+- `create-architecture` - Produce a Scale Adaptive Architecture
 - `validate-architecture` - Validate architecture document
 - `solutioning-gate-check` - Validate readiness for Phase 4
-- `correct-course` - Handle technical changes
 
 **Communication Style:** Comprehensive yet pragmatic. Uses architectural metaphors. Balances technical depth with accessibility. Connects decisions to business value.
 
@@ -177,7 +172,7 @@ The BMad Method Module (BMM) provides a comprehensive team of specialized AI age
 - Sprint planning and tracking initialization
 - Creating user stories
 - Assembling dynamic story context
-- Epic-level technical specifications (optional)
+- Epic-level technical context (optional)
 - Marking stories ready for development
 - Sprint retrospectives
 
@@ -187,8 +182,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 tech specs
-- `validate-epic-tech-context` - Validate epic tech spec
+- `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
@@ -231,7 +226,7 @@ The BMad Method Module (BMM) provides a comprehensive team of specialized AI age
   - Strict file boundary enforcement
 - `code-review` - Senior developer-level review with:
   - Story context awareness
-  - Epic tech-spec alignment
+  - Epic-tech-context alignment
   - Repository docs reference
   - MCP server best practices
   - Web search fallback
@@ -300,12 +295,13 @@ The BMad Method Module (BMM) provides a comprehensive team of specialized AI age
 - Testing is feature work, not overhead
 - Prioritize unit/integration over E2E
 - Flakiness is critical technical debt
+- ATDD tests first, AI implements, suite validates
 
 **Special Capabilities:**
 
-- **Test Healing:** Pattern-based + MCP-enhanced test fixing
-- **Dual Mode:** BMad-integrated (uses epic/story context) or standalone
-- **Knowledge Base:** Comprehensive testing best practices
+- **Knowledge Base Access:** Consults comprehensive testing best practices from `testarch/knowledge/` directory
+- **Framework Selection:** Smart framework selection (Playwright vs Cypress) with fixture architecture
+- **Cross-Platform Testing:** Supports testing across web, mobile, and API layers
 
 ---
 
@@ -345,7 +341,7 @@ The BMad Method Module (BMM) provides a comprehensive team of specialized AI age
 
 ---
 
-### Paige (Documentation Guide) - Paige 📚
+### Technical Writer - Paige 📚
 
 **Role:** Technical Documentation Specialist + Knowledge Curator
 
@@ -461,10 +457,9 @@ The BMad Method Module (BMM) provides a comprehensive team of specialized AI age
 **Workflows:**
 
 - `workflow-status` - Check what to do next
-- `create-story` - Create development story
-- `dev-story` - Implement story with tests
-- `code-review` - Review game implementation
-- `retro` - Sprint retrospective
+- `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.
 
@@ -555,71 +550,24 @@ The BMad Method Module (BMM) provides a comprehensive team of specialized AI age
 
 ## Party Mode: Multi-Agent Collaboration
 
-Party mode brings **all your installed agents together** for group discussions. Instead of working with one agent at a time, you engage with a dynamic team (19+ agents from BMM, CIS, BMB, and custom modules) that collaborates in real-time.
-
-### Quick Overview
-
-**How to Start:**
-
-1. Load BMad Master
-2. Run `*party-mode`
-3. Introduce your topic
-
-**What Happens:**
+Get all your installed agents in one conversation for multi-perspective discussions, retrospectives, and collaborative decision-making.
 
-- BMad Master loads ALL agents (with customizations)
-- For each message, 2-3 most relevant agents respond
-- Agents cross-talk, debate, and build on each other's ideas
-- BMad Master moderates and keeps discussion productive
-
-**Best For:**
-
-- Strategic decisions with trade-offs
-- Creative brainstorming sessions
-- Cross-functional alignment meetings
-- Complex problem-solving
-- Epic kickoff discussions
+**Quick Start:**
 
-**Example Parties:**
-
-- **Product Strategy:** PM + Innovation Strategist + Analyst
-- **Technical Design:** Architect + Game Architect + Creative Problem Solver
-- **User Experience:** UX Designer + Design Thinking Coach + Storyteller
-- **Quality & Testing:** TEA + Architect + DEV
-- **Full Team:** PM + Architect + SM + DEV
-
-### Why Party Mode is Powerful
-
-**Diverse Perspectives:**
-
-- Technical agents ground ideas in reality
-- Creative agents (CIS) push for innovation
-- Strategic agents ensure market fit
-
-**Emergent Insights:**
-
-- Cross-pollination across domains
-- Novel solutions from unexpected combinations
-- Deeper exploration through debate
+```bash
+/bmad:core:workflows:party-mode
+# OR from any agent: *party-mode
+```
 
-**Natural Collaboration:**
+**What happens:** BMad Master orchestrates 2-3 relevant agents per message. They discuss, debate, and collaborate in real-time.
 
-- Agents can agree, disagree, or build on each other
-- Healthy debate leads to better decisions
-- Multiple expert perspectives in one session
+**Best for:** Strategic decisions, creative brainstorming, post-mortems, sprint retrospectives, complex problem-solving.
 
-**For complete party mode documentation, see:**
+**Current BMM uses:** Powers `epic-retrospective` workflow, sprint planning discussions.
 
-👉 **[Party Mode Guide](./party-mode.md)** - Comprehensive 20-minute guide covering:
+**Future:** Advanced elicitation workflows will officially leverage party mode.
 
-- How party mode works (step-by-step process)
-- When to use party mode (strategic, creative, cross-functional, complex)
-- Getting started (quick start guide)
-- Agent selection dynamics
-- Multi-module integration (19+ agents)
-- 8+ example party compositions
-- Agent customization in party mode
-- Best practices and troubleshooting
+👉 **[Party Mode Guide](./party-mode.md)** - Complete guide with fun examples, tips, and troubleshooting
 
 ---
 
@@ -650,7 +598,7 @@ Some workflows are available to multiple agents:
 | `workflow-status`  | ALL agents                        | Check current state and get recommendations |
 | `workflow-init`    | PM, Analyst, Game Designer        | Initialize workflow tracking                |
 | `correct-course`   | PM, Architect, SM, Game Architect | Change management during implementation     |
-| `document-project` | Analyst, Paige                    | Brownfield documentation                    |
+| `document-project` | Analyst, Technical Writer         | Brownfield documentation                    |
 
 ### Validation Actions
 
@@ -662,7 +610,7 @@ Many workflows have optional validation workflows that perform independent revie
 | `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 specification       |
+| `validate-epic-tech-context` | SM          | Epic technical context             |
 | `validate-create-story`      | SM          | Story draft                        |
 | `validate-story-context`     | SM          | Story context XML                  |
 
@@ -846,12 +794,12 @@ Load the customized agent and verify the changes are reflected in its behavior a
 - **Phase 3 (Solutioning):** Architect, Game Architect
 - **Phase 4 (Implementation):** SM, DEV, Game Developer
 - **Testing:** TEA (all phases)
-- **Documentation:** Paige (all phases)
+- **Documentation:** Technical Writer (all phases)
 
 **3. Use specialists**
 
 - **Testing:** TEA for comprehensive quality strategy
-- **Documentation:** Paige for technical writing
+- **Documentation:** Technical Writer for technical writing
 - **Games:** Game Designer/Developer/Architect for game-specific needs
 - **UX:** UX Designer for user-centered design
 
@@ -907,7 +855,7 @@ Load the customized agent and verify the changes are reflected in its behavior a
 **Starting with Existing Code (Brownfield):**
 
 ```
-1. Analyst or Paige: *document-project
+1. Analyst or Technical Writer: *document-project
 2. PM or Analyst: *workflow-init
 3. PM: *create-prd or *tech-spec
 4. Architect: *create-architecture (if needed)
@@ -990,20 +938,20 @@ 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, gate-check                      | 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**          | 📚   | 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)          | dev-story, code-review                        | Game implementation                   |
-| **Game Architect** | 🏛️   | 3 (Games)          | architecture, gate-check                      | 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-design, validate-design                | UX-heavy projects, design             |
+| **Architect**           | 🏗️   | 3 (Solutioning)    | architecture, gate-check                      | 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, gate-check                      | Game systems architecture             |
+| **BMad Master**         | 🧙   | Meta               | party-mode, list tasks/workflows              | Orchestration, multi-agent            |
 
 ### Agent Capabilities Summary
 
@@ -1032,7 +980,7 @@ Quick reference for agent selection:
 **Support Agents (2):**
 
 - Analyst: Research and discovery
-- Paige: Documentation and diagrams
+- Technical Writer: Documentation and diagrams
 
 **Meta Agent (1):**
 
@@ -1048,7 +996,7 @@ Quick reference for agent selection:
 - [Phase 2: Planning Workflows](./workflows-planning.md)
 - [Phase 3: Solutioning Workflows](./workflows-solutioning.md)
 - [Phase 4: Implementation Workflows](./workflows-implementation.md)
-- [Testing & QA Workflows](./workflows-testing.md)
+<!-- Testing & QA Workflows documentation to be added -->
 
 **Advanced References:**
 
@@ -1083,7 +1031,7 @@ Quick reference for agent selection:
 **Starting a Project:**
 
 - [ ] Determine project type (greenfield vs brownfield)
-- [ ] If brownfield: Run `*document-project` (Analyst or Paige)
+- [ ] If brownfield: Run `*document-project` (Analyst or Technical Writer)
 - [ ] Load PM or Analyst → `*workflow-init`
 - [ ] Follow phase-appropriate workflows
 - [ ] Try `*party-mode` for strategic decisions