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

package/src/modules/bmm/docs/workflows-planning.md

@@ -1,7 +1,5 @@
 # BMM Planning Workflows (Phase 2)
 
-**Reading Time:** ~10 minutes
-
 ## Overview
 
 Phase 2 (Planning) workflows are **required** for all projects. They transform strategic vision into actionable requirements using a **scale-adaptive system** that automatically selects the right planning depth based on project complexity.
@@ -12,101 +10,46 @@ Phase 2 (Planning) workflows are **required** for all projects. They transform s
 
 ---
 
-## Phase 2 Planning Workflow Map
-
-```mermaid
-%%{init: {'theme':'base', 'themeVariables': { 'primaryColor':'#fff','primaryTextColor':'#000','primaryBorderColor':'#000','lineColor':'#000','fontSize':'16px','fontFamily':'arial'}}}%%
-graph TB
-    Start["<b>START: workflow-init</b><br/>Discovery + routing"]
-
-    subgraph QuickFlow["<b>QUICK FLOW (Simple Planning)</b>"]
-        direction TB
-        TechSpec["<b>PM: tech-spec</b><br/>Technical document<br/>→ Story or Epic+Stories<br/>1-15 stories typically"]
-    end
-
-    subgraph BMadMethod["<b>BMAD METHOD (Recommended)</b>"]
-        direction TB
-        PRD["<b>PM: prd</b><br/>Strategic PRD with FRs/NFRs"]
-        GDD["<b>Game Designer: gdd</b><br/>Game design doc"]
-        Narrative["<b>Game Designer: narrative</b><br/>Story-driven design"]
-
-        UXDesign["<b>UX Designer: create-ux-design</b><br/>Optional UX specification"]
-    end
-
-    subgraph Solutioning["<b>PHASE 3: SOLUTIONING</b>"]
-        direction TB
-        Architecture["<b>Architect: architecture</b><br/>System design + decisions"]
-        Epics["<b>PM: create-epics-and-stories</b><br/>Epic+Stories breakdown<br/>(10-50+ stories typically)"]
-    end
-
-    subgraph Enterprise["<b>ENTERPRISE METHOD</b>"]
-        direction TB
-        EntNote["<b>Uses BMad Method Planning</b><br/>+<br/>Extended Phase 3 workflows<br/>(Architecture + Security + DevOps)<br/>30+ stories typically"]
-    end
-
-    subgraph Updates["<b>MID-STREAM UPDATES (Anytime)</b>"]
-        direction LR
-        CorrectCourse["<b>PM/SM: correct-course</b><br/>Update requirements/stories"]
-    end
-
-    Start -->|Bug fix, simple| QuickFlow
-    Start -->|Software product| PRD
-    Start -->|Game project| GDD
-    Start -->|Story-driven| Narrative
-    Start -->|Enterprise needs| Enterprise
-
-    PRD -.->|Optional| UXDesign
-    GDD -.->|Optional| UXDesign
-    Narrative -.->|Optional| UXDesign
-    PRD --> Architecture
-    GDD --> Architecture
-    Narrative --> Architecture
-    UXDesign --> Architecture
-    Architecture --> Epics
-
-    QuickFlow --> Phase4["<b>Phase 4: Implementation</b>"]
-    Epics --> ReadinessCheck["<b>Architect: implementation-readiness</b><br/>Gate check"]
-    Enterprise -.->|Uses BMad planning| Architecture
-    Enterprise --> Phase3Ext["<b>Phase 3: Extended</b><br/>(Arch + Sec + DevOps)"]
-    ReadinessCheck --> Phase4
-    Phase3Ext --> Phase4
-
-    Phase4 -.->|Significant changes| CorrectCourse
-    CorrectCourse -.->|Updates| Epics
-
-    style Start fill:#fff9c4,stroke:#f57f17,stroke-width:3px,color:#000
-    style QuickFlow fill:#c5e1a5,stroke:#33691e,stroke-width:3px,color:#000
-    style BMadMethod fill:#e1bee7,stroke:#6a1b9a,stroke-width:3px,color:#000
-    style Enterprise fill:#ffcdd2,stroke:#c62828,stroke-width:3px,color:#000
-    style Updates fill:#ffecb3,stroke:#ff6f00,stroke-width:3px,color:#000
-    style Phase3 fill:#90caf9,stroke:#0d47a1,stroke-width:2px,color:#000
-    style Phase4 fill:#ffcc80,stroke:#e65100,stroke-width:2px,color:#000
-
-    style TechSpec fill:#aed581,stroke:#1b5e20,stroke-width:2px,color:#000
-    style PRD fill:#ce93d8,stroke:#4a148c,stroke-width:2px,color:#000
-    style GDD fill:#ce93d8,stroke:#4a148c,stroke-width:2px,color:#000
-    style Narrative fill:#ce93d8,stroke:#4a148c,stroke-width:2px,color:#000
-    style UXDesign fill:#ce93d8,stroke:#4a148c,stroke-width:2px,color:#000
-    style Epics fill:#ba68c8,stroke:#6a1b9a,stroke-width:3px,color:#000
-    style EntNote fill:#ef9a9a,stroke:#c62828,stroke-width:2px,color:#000
-    style Phase3Ext fill:#ef5350,stroke:#c62828,stroke-width:2px,color:#000
-    style CorrectCourse fill:#ffb74d,stroke:#ff6f00,stroke-width:2px,color:#000
-```
+## Phase 2 Planning Workflow Overview
+
+Phase 2 Planning uses a scale-adaptive system with three tracks:
+
+### Quick Flow (Simple Planning)
+
+- Entry: `workflow-init` routes based on project complexity
+- Workflow: `tech-spec`
+- Output: Technical document with story/epic structure
+- Story count: 1-15 (typical)
+- Next: Phase 4 (Implementation) - skips Phase 3
+
+### BMad Method (Recommended)
+
+- Entry: `workflow-init` routes based on project complexity
+- Workflows: `prd` → (optional) `create-ux-design`
+- Output: PRD with FRs/NFRs
+- Story count: 10-50+ (typical)
+- Next: Phase 3 (Solutioning) → Phase 4
+
+### Enterprise Method
+
+- Planning: Same as BMad Method (`prd` workflow)
+- Solutioning: Extended Phase 3 workflows (Architecture + Security + DevOps)
+- Story count: 30+ (typical)
+- Next: Phase 4
+
+The `correct-course` workflow can be used anytime for significant requirement changes.
 
 ---
 
 ## Quick Reference
 
-| Workflow                     | Agent         | Track       | Purpose                                                   | Typical Stories |
-| ---------------------------- | ------------- | ----------- | --------------------------------------------------------- | --------------- |
-| **workflow-init**            | PM/Analyst    | All         | Entry point: discovery + routing                          | N/A             |
-| **tech-spec**                | PM            | Quick Flow  | Technical document → Story or Epic+Stories                | 1-15            |
-| **prd**                      | PM            | BMad Method | Strategic PRD with FRs/NFRs (no epic breakdown)           | 10-50+          |
-| **gdd**                      | Game Designer | BMad Method | Game Design Document with requirements                    | 10-50+          |
-| **narrative**                | Game Designer | BMad Method | Story-driven game/experience design                       | 10-50+          |
-| **create-ux-design**         | UX Designer   | BMad Method | Optional UX specification (after PRD)                     | N/A             |
-| **create-epics-and-stories** | PM            | BMad Method | Break requirements into Epic+Stories (AFTER architecture) | N/A             |
-| **correct-course**           | PM/SM         | All         | Mid-stream requirement changes                            | N/A             |
+| Workflow             | Agent       | Track                   | Purpose                                         | Typical Stories |
+| -------------------- | ----------- | ----------------------- | ----------------------------------------------- | --------------- |
+| **workflow-init**    | PM/Analyst  | All                     | Entry point: discovery + routing                | N/A             |
+| **tech-spec**        | PM          | Quick Flow              | Technical document → Story or Epic+Stories      | 1-15            |
+| **prd**              | PM          | BMad Method, Enterprise | Strategic PRD with FRs/NFRs (no epic breakdown) | 10-50+          |
+| **create-ux-design** | UX Designer | BMad Method, Enterprise | Optional UX specification (after PRD)           | N/A             |
+| **correct-course**   | PM/SM       | All                     | Mid-stream requirement changes                  | N/A             |
 
 **Note:** Story counts are guidance. V6 improvement: Epic+Stories are created AFTER architecture for better quality.
 
@@ -195,7 +138,7 @@ The system guides but never forces. You can override recommendations.
 
 **Agent:** PM (orchestrates others as needed)
 
-**Always Use:** This is your planning starting point. Don't call prd/gdd/tech-spec directly unless skipping discovery.
+**Always Use:** This is your planning starting point. Don't call prd/tech-spec directly unless skipping discovery.
 
 **Process:**
 
@@ -268,70 +211,7 @@ The system guides but never forces. You can override recommendations.
 
 ---
 
-### gdd (Game Design Document)
-
-**Purpose:** Complete game design document for game projects (BMad Method track).
-
-**Agent:** Game Designer
-
-**When to Use:**
-
-- Designing any game (any genre)
-- Need comprehensive design documentation
-- Team needs shared vision
-- Publisher/stakeholder communication
-
-**BMM GDD vs Traditional:**
-
-- Scale-adaptive detail (not waterfall)
-- Agile epic structure
-- Direct handoff to implementation
-- Integrated with testing workflows
-
-**Key Outputs:**
-
-- GDD.md (complete game design)
-- Epic breakdown (Core Loop, Content, Progression, Polish)
-
-**Integration:** Feeds into Architecture (Phase 3)
-
-**Example:** Roguelike card game → Core concept (Slay the Spire meets Hades), 3 characters, 120 cards, 50 enemies, Epic breakdown with 26 stories.
-
----
-
-### narrative (Narrative Design)
-
-**Purpose:** Story-driven design workflow for games/experiences where narrative is central (BMad Method track).
-
-**Agent:** Game Designer (Narrative Designer persona) + Creative Problem Solver (CIS)
-
-**When to Use:**
-
-- Story is central to experience
-- Branching narrative with player choices
-- Character-driven games
-- Visual novels, adventure games, RPGs
-
-**Combine with GDD:**
-
-1. Run `narrative` first (story structure)
-2. Then run `gdd` (integrate story with gameplay)
-
-**Key Outputs:**
-
-- narrative-design.md (complete narrative spec)
-- Story structure (acts, beats, branching)
-- Characters (profiles, arcs, relationships)
-- Dialogue system design
-- Implementation guide
-
-**Integration:** Combine with GDD, then feeds into Architecture (Phase 3)
-
-**Example:** Choice-driven RPG → 3 acts, 12 chapters, 5 choice points, 3 endings, 60K words, 40 narrative scenes.
-
----
-
-### ux (UX-First Design)
+### create-ux-design (UX Design)
 
 **Purpose:** UX specification for projects where user experience is the primary differentiator (BMad Method track).
 
@@ -367,31 +247,6 @@ The system guides but never forces. You can override recommendations.
 
 ---
 
-### create-epics-and-stories
-
-**Purpose:** Break requirements into bite-sized stories organized in epics (BMad Method track).
-
-**Agent:** PM
-
-**When to Use:**
-
-- **REQUIRED:** After Architecture workflow is complete (Phase 3)
-- After PRD defines FRs/NFRs and Architecture defines HOW to build
-- Optional: Can also run earlier (after PRD, after UX) for basic structure, then refined after Architecture
-
-**Key Outputs:**
-
-- epics.md (all epics with story breakdown)
-- Epic files (epic-1-\*.md, etc.)
-
-**V6 Improvement:** Epics+Stories are now created AFTER architecture for better quality:
-
-- Architecture decisions inform story breakdown (tech choices affect implementation)
-- Stories have full context (PRD + UX + Architecture)
-- Better sequencing with technical dependencies considered
-
----
-
 ### correct-course
 
 **Purpose:** Handle significant requirement changes during implementation (all tracks).
@@ -426,9 +281,7 @@ The system guides but never forces. You can override recommendations.
 
 - **Bug fix or single change** → `tech-spec` (Quick Flow)
 - **Software product** → `prd` (BMad Method)
-- **Game (gameplay-first)** → `gdd` (BMad Method)
-- **Game (story-first)** → `narrative` + `gdd` (BMad Method)
-- **UX innovation project** → `ux` + `prd` (BMad Method)
+- **UX innovation project** → `create-ux-design` + `prd` (BMad Method)
 - **Enterprise with compliance** → Choose track in `workflow-init` → Enterprise Method
 
 ---
@@ -437,14 +290,12 @@ The system guides but never forces. You can override recommendations.
 
 Planning outputs feed into Solutioning:
 
-| Planning Output     | Solutioning Input                    | Track Decision               |
-| ------------------- | ------------------------------------ | ---------------------------- |
-| tech-spec.md        | Skip Phase 3 → Phase 4 directly      | Quick Flow (no architecture) |
-| PRD.md              | **architecture** (Level 3-4)         | BMad Method (recommended)    |
-| GDD.md              | **architecture** (game tech)         | BMad Method (recommended)    |
-| narrative-design.md | **architecture** (narrative systems) | BMad Method                  |
-| ux-spec.md          | **architecture** (frontend design)   | BMad Method                  |
-| Enterprise docs     | **architecture** + security/ops      | Enterprise Method (required) |
+| Planning Output | Solutioning Input                  | Track Decision               |
+| --------------- | ---------------------------------- | ---------------------------- |
+| tech-spec.md    | Skip Phase 3 → Phase 4 directly    | Quick Flow (no architecture) |
+| PRD.md          | **architecture** (Level 3-4)       | BMad Method (recommended)    |
+| ux-spec.md      | **architecture** (frontend design) | BMad Method                  |
+| Enterprise docs | **architecture** + security/ops    | Enterprise Method (required) |
 
 **Key Decision Points:**
 
@@ -468,11 +319,11 @@ If `workflow-init` suggests BMad Method, there's likely complexity you haven't c
 
 ### 3. Iterate on Requirements
 
-Planning documents are living. Refine PRDs/GDDs as you learn during Solutioning and Implementation.
+Planning documents are living. Refine PRDs as you learn during Solutioning and Implementation.
 
 ### 4. Involve Stakeholders Early
 
-Review PRDs/GDDs with stakeholders before Solutioning. Catch misalignment early.
+Review PRDs with stakeholders before Solutioning. Catch misalignment early.
 
 ### 5. Focus on "What" Not "How"
 
@@ -492,9 +343,8 @@ Always run `document-project` before planning brownfield projects. AI agents nee
 1. (Optional) Analysis: product-brief, research
 2. workflow-init → routes to prd
 3. PM: prd workflow
-4. (Optional) UX Designer: ux workflow
-5. PM: create-epics-and-stories (may be automatic)
-6. → Phase 3: architecture
+4. (Optional) UX Designer: create-ux-design workflow
+5. → Phase 3: architecture
 ```
 
 ### Brownfield Software (BMad Method)
@@ -503,28 +353,17 @@ Always run `document-project` before planning brownfield projects. AI agents nee
 1. Technical Writer or Analyst: document-project
 2. workflow-init → routes to prd
 3. PM: prd workflow
-4. PM: create-epics-and-stories
-5. → Phase 3: architecture (recommended for focused solution design)
+4. → Phase 3: architecture (recommended for focused solution design)
 ```
 
 ### Bug Fix (Quick Flow)
 
 ```
 1. workflow-init → routes to tech-spec
-2. Architect: tech-spec workflow
+2. PM: tech-spec workflow
 3. → Phase 4: Implementation (skip Phase 3)
 ```
 
-### Game Project (BMad Method)
-
-```
-1. (Optional) Analysis: game-brief, research
-2. workflow-init → routes to gdd
-3. Game Designer: gdd workflow (or narrative + gdd if story-first)
-4. Game Designer creates epic breakdown
-5. → Phase 3: architecture (game systems)
-```
-
 ### Enterprise Project (Enterprise Method)
 
 ```
@@ -602,7 +441,7 @@ A: Run `correct-course` workflow. It analyzes impact and updates planning artifa
 A: Recommended! Architecture distills massive codebase into focused solution design for your specific project.
 
 **Q: When do I run create-epics-and-stories?**
-A: Usually automatic during PRD/GDD. Can also run standalone later to regenerate epics.
+A: In Phase 3 (Solutioning), after architecture is complete.
 
 **Q: Should I use product-brief before PRD?**
 A: Optional but recommended for greenfield. Helps strategic thinking. `workflow-init` offers it based on context.

package/src/modules/bmm/docs/workflows-solutioning.md

@@ -1,7 +1,5 @@
 # BMM Solutioning Workflows (Phase 3)
 
-**Reading Time:** ~8 minutes
-
 ## Overview
 
 Phase 3 (Solutioning) workflows translate **what** to build (from Planning) into **how** to build it (technical design). This phase prevents agent conflicts in multi-epic projects by documenting architectural decisions before implementation begins.
@@ -14,73 +12,30 @@ Phase 3 (Solutioning) workflows translate **what** to build (from Planning) into
 
 ---
 
-## Phase 3 Solutioning Workflow Map
-
-```mermaid
-%%{init: {'theme':'base', 'themeVariables': { 'primaryColor':'#fff','primaryTextColor':'#000','primaryBorderColor':'#000','lineColor':'#000','fontSize':'16px','fontFamily':'arial'}}}%%
-graph TB
-    FromPlanning["<b>FROM Phase 2 Planning</b><br/>PRD (FRs/NFRs) complete"]
-
-    subgraph QuickFlow["<b>QUICK FLOW PATH</b>"]
-        direction TB
-        SkipArch["<b>Skip Phase 3</b><br/>Go directly to Implementation"]
-    end
-
-    subgraph BMadEnterprise["<b>BMAD METHOD + ENTERPRISE (Same Start)</b>"]
-        direction TB
-        OptionalUX["<b>UX Designer: create-ux-design</b><br/>(Optional)"]
-        Architecture["<b>Architect: architecture</b><br/>System design + ADRs"]
-
-        subgraph Optional["<b>ENTERPRISE ADDITIONS (Optional)</b>"]
-            direction LR
-            SecArch["<b>Architect: security-architecture</b><br/>(Future)"]
-            DevOps["<b>Architect: devops-strategy</b><br/>(Future)"]
-        end
-
-        EpicsStories["<b>PM: create-epics-and-stories</b><br/>Break down FRs/NFRs into epics"]
-        GateCheck["<b>Architect: implementation-readiness</b><br/>Validation before Phase 4"]
-
-        OptionalUX -.-> Architecture
-        Architecture -.->|Enterprise only| Optional
-        Architecture --> EpicsStories
-        Optional -.-> EpicsStories
-        EpicsStories --> GateCheck
-    end
-
-    subgraph Result["<b>GATE CHECK RESULTS</b>"]
-        direction LR
-        Pass["✅ PASS<br/>Proceed to Phase 4"]
-        Concerns["⚠️ CONCERNS<br/>Proceed with caution"]
-        Fail["❌ FAIL<br/>Resolve issues first"]
-    end
-
-    FromPlanning -->|Quick Flow| QuickFlow
-    FromPlanning -->|BMad Method<br/>or Enterprise| OptionalUX
-
-    QuickFlow --> Phase4["<b>Phase 4: Implementation</b>"]
-    GateCheck --> Result
-    Pass --> Phase4
-    Concerns --> Phase4
-    Fail -.->|Fix issues| Architecture
-
-    style FromPlanning fill:#e1bee7,stroke:#6a1b9a,stroke-width:2px,color:#000
-    style QuickFlow fill:#c5e1a5,stroke:#33691e,stroke-width:3px,color:#000
-    style BMadEnterprise fill:#90caf9,stroke:#0d47a1,stroke-width:3px,color:#000
-    style Optional fill:#ffcdd2,stroke:#c62828,stroke-width:3px,color:#000
-    style Result fill:#fff9c4,stroke:#f57f17,stroke-width:3px,color:#000
-    style Phase4 fill:#ffcc80,stroke:#e65100,stroke-width:2px,color:#000
-
-    style SkipArch fill:#aed581,stroke:#1b5e20,stroke-width:2px,color:#000
-    style OptionalUX fill:#64b5f6,stroke:#0d47a1,stroke-width:2px,color:#000
-    style Architecture fill:#42a5f5,stroke:#0d47a1,stroke-width:2px,color:#000
-    style SecArch fill:#ef9a9a,stroke:#c62828,stroke-width:2px,color:#000
-    style DevOps fill:#ef9a9a,stroke:#c62828,stroke-width:2px,color:#000
-    style EpicsStories fill:#42a5f5,stroke:#0d47a1,stroke-width:2px,color:#000
-    style GateCheck fill:#42a5f5,stroke:#0d47a1,stroke-width:2px,color:#000
-    style Pass fill:#81c784,stroke:#388e3c,stroke-width:2px,color:#000
-    style Concerns fill:#ffb74d,stroke:#f57f17,stroke-width:2px,color:#000
-    style Fail fill:#e57373,stroke:#d32f2f,stroke-width:2px,color:#000
-```
+## Phase 3 Solutioning Workflow Overview
+
+Phase 3 Solutioning has different paths based on the planning track selected:
+
+### Quick Flow Path
+
+- From Planning: tech-spec complete
+- Action: Skip Phase 3 entirely
+- Next: Phase 4 (Implementation)
+
+### BMad Method & Enterprise Path
+
+- From Planning: PRD with FRs/NFRs complete
+- Optional: create-ux-design (if UX is critical)
+- Required: architecture - System design with ADRs
+- Required: create-epics-and-stories - Break requirements into implementable stories
+- Required: implementation-readiness - Gate check validation
+- Enterprise additions: Optional security-architecture and devops-strategy (future workflows)
+
+### Gate Check Results
+
+- **PASS** - All criteria met, proceed to Phase 4
+- **CONCERNS** - Minor gaps identified, proceed with caution
+- **FAIL** - Critical issues, must resolve before Phase 4
 
 ---
 
@@ -469,13 +424,13 @@ Architecture documents are living. Update them as you learn during implementatio
 
 - **Planning:** prd (PM) - creates FRs/NFRs only, NOT epics
 - **Solutioning:** Optional UX → architecture (Architect) → create-epics-and-stories (PM) → implementation-readiness (Architect)
-- **Implementation:** sprint-planning → epic-tech-context → dev-story
+- **Implementation:** sprint-planning → create-story → dev-story
 
 ### Enterprise
 
 - **Planning:** prd (PM) - creates FRs/NFRs only (same as BMad Method)
 - **Solutioning:** Optional UX → architecture (Architect) → Optional extended workflows (security-architecture, devops-strategy) → create-epics-and-stories (PM) → implementation-readiness (Architect)
-- **Implementation:** sprint-planning → epic-tech-context → dev-story
+- **Implementation:** sprint-planning → create-story → dev-story
 
 **Key Difference:** Enterprise adds optional extended workflows AFTER architecture but BEFORE create-epics-and-stories. Everything else is identical to BMad Method.
 

package/src/modules/bmm/tasks/daily-standup.xml

@@ -0,0 +1,85 @@
+<task id="bmad/bmm/tasks/daily-standup.xml" name="Daily Standup">
+  <llm critical="true">
+    <i>MANDATORY: Execute ALL steps in the flow section IN EXACT ORDER</i>
+    <i>DO NOT skip steps or change the sequence</i>
+    <i>HALT immediately when halt-conditions are met</i>
+    <i>Each action tag within a step tag is a REQUIRED action to complete that step</i>
+    <i>Sections outside flow (validation, output, critical-context) provide essential context - review and apply throughout execution</i>
+  </llm>
+  <flow>
+    <step n="1" title="Project Context Discovery">
+      <action>Check for stories folder at {project-root}{output_folder}/stories/</action>
+      <action>Find current story by identifying highest numbered story file</action>
+      <action>Read story status (In Progress, Ready for Review, etc.)</action>
+      <action>Extract agent notes from Dev Agent Record, TEA Results, PO Notes sections</action>
+      <action>Check for next story references from epics</action>
+      <action>Identify blockers from story sections</action>
+    </step>
+
+    <step n="2" title="Initialize Standup with Context">
+      <output>
+        🏃 DAILY STANDUP - Story-{{number}}: {{title}}
+
+        Current Sprint Status:
+        - Active Story: story-{{number}} ({{status}} - {{percentage}}% complete)
+        - Next in Queue: story-{{next-number}}: {{next-title}}
+        - Blockers: {{blockers-from-story}}
+
+        Team assembled based on story participants:
+        {{ List Agents from {project-root}/bmad/_cfg/agent-manifest.csv }}
+      </output>
+    </step>
+
+    <step n="3" title="Structured Standup Discussion">
+      <action>Each agent provides three items referencing real story data</action>
+      <action>What I see: Their perspective on current work, citing story sections (1-2 sentences)</action>
+      <action>What concerns me: Issues from their domain or story blockers (1-2 sentences)</action>
+      <action>What I suggest: Actionable recommendations for progress (1-2 sentences)</action>
+    </step>
+
+    <step n="4" title="Create Standup Summary">
+      <output>
+        📋 STANDUP SUMMARY:
+        Key Items from Story File:
+        - {{completion-percentage}}% complete ({{tasks-complete}}/{{total-tasks}} tasks)
+        - Blocker: {{main-blocker}}
+        - Next: {{next-story-reference}}
+
+        Action Items:
+        - {{agent}}: {{action-item}}
+        - {{agent}}: {{action-item}}
+        - {{agent}}: {{action-item}}
+
+        Need extended discussion? Use *party-mode for detailed breakout.
+      </output>
+    </step>
+  </flow>
+
+  <agent-selection>
+    <context type="prd-review">
+      <i>Primary: Sarah (PO), Mary (Analyst), Winston (Architect)</i>
+      <i>Secondary: Murat (TEA), James (Dev)</i>
+    </context>
+    <context type="story-planning">
+      <i>Primary: Sarah (PO), Bob (SM), James (Dev)</i>
+      <i>Secondary: Murat (TEA)</i>
+    </context>
+    <context type="validate-architecture">
+      <i>Primary: Winston (Architect), James (Dev), Murat (TEA)</i>
+      <i>Secondary: Sarah (PO)</i>
+    </context>
+    <context type="implementation">
+      <i>Primary: James (Dev), Murat (TEA), Winston (Architect)</i>
+      <i>Secondary: Sarah (PO)</i>
+    </context>
+  </agent-selection>
+
+  <llm critical="true">
+    <i>This task extends party-mode with agile-specific structure</i>
+    <i>Time-box responses (standup = brief)</i>
+    <i>Focus on actionable items from real story data when available</i>
+    <i>End with clear next steps</i>
+    <i>No deep dives (suggest breakout if needed)</i>
+    <i>If no stories folder detected, run general standup format</i>
+  </llm>
+</task>