bmad-method 6.0.0-alpha.9 → 6.0.2

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

@@ -1,370 +0,0 @@
-# BMM Analysis Workflows (Phase 1)
-
-**Reading Time:** ~7 minutes
-
-## Overview
-
-Phase 1 (Analysis) workflows are **optional** exploration and discovery tools that help validate ideas, understand markets, and generate strategic context before planning begins.
-
-**Key principle:** Analysis workflows help you think strategically before committing to implementation. Skip them if your requirements are already clear.
-
-**When to use:** Starting new projects, exploring opportunities, validating market fit, generating ideas, understanding problem spaces.
-
-**When to skip:** Continuing existing projects with clear requirements, well-defined features with known solutions, strict constraints where discovery is complete.
-
----
-
-## Phase 1 Analysis Workflow Map
-
-```mermaid
-%%{init: {'theme':'base', 'themeVariables': { 'primaryColor':'#fff','primaryTextColor':'#000','primaryBorderColor':'#000','lineColor':'#000','fontSize':'16px','fontFamily':'arial'}}}%%
-graph TB
-    subgraph Discovery["<b>DISCOVERY & IDEATION (Optional)</b>"]
-        direction LR
-        BrainstormProject["<b>Analyst: brainstorm-project</b><br/>Multi-track solution exploration"]
-        BrainstormGame["<b>Analyst: brainstorm-game</b><br/>Game concept generation"]
-    end
-
-    subgraph Research["<b>RESEARCH & VALIDATION (Optional)</b>"]
-        direction TB
-        ResearchWF["<b>Analyst: research</b><br/>• market (TAM/SAM/SOM)<br/>• technical (framework evaluation)<br/>• competitive (landscape)<br/>• user (personas, JTBD)<br/>• domain (industry analysis)<br/>• deep_prompt (AI research)"]
-    end
-
-    subgraph Strategy["<b>STRATEGIC CAPTURE (Recommended for Greenfield)</b>"]
-        direction LR
-        ProductBrief["<b>Analyst: product-brief</b><br/>Product vision + strategy<br/>(Interactive or YOLO mode)"]
-        GameBrief["<b>Game Designer: game-brief</b><br/>Game vision capture<br/>(Interactive or YOLO mode)"]
-    end
-
-    Discovery -.->|Software| ProductBrief
-    Discovery -.->|Games| GameBrief
-    Discovery -.->|Validate ideas| Research
-    Research -.->|Inform brief| ProductBrief
-    Research -.->|Inform brief| GameBrief
-    ProductBrief --> Phase2["<b>Phase 2: prd workflow</b>"]
-    GameBrief --> Phase2Game["<b>Phase 2: gdd workflow</b>"]
-    Research -.->|Can feed directly| Phase2
-
-    style Discovery fill:#e1f5fe,stroke:#01579b,stroke-width:3px,color:#000
-    style Research fill:#fff9c4,stroke:#f57f17,stroke-width:3px,color:#000
-    style Strategy fill:#f3e5f5,stroke:#4a148c,stroke-width:3px,color:#000
-    style Phase2 fill:#c8e6c9,stroke:#2e7d32,stroke-width:2px,color:#000
-    style Phase2Game fill:#c8e6c9,stroke:#2e7d32,stroke-width:2px,color:#000
-
-    style BrainstormProject fill:#81d4fa,stroke:#0277bd,stroke-width:2px,color:#000
-    style BrainstormGame fill:#81d4fa,stroke:#0277bd,stroke-width:2px,color:#000
-    style ResearchWF fill:#fff59d,stroke:#f57f17,stroke-width:2px,color:#000
-    style ProductBrief fill:#ce93d8,stroke:#6a1b9a,stroke-width:2px,color:#000
-    style GameBrief fill:#ce93d8,stroke:#6a1b9a,stroke-width:2px,color:#000
-```
-
----
-
-## Quick Reference
-
-| Workflow               | Agent         | Required    | Purpose                                                        | Output                       |
-| ---------------------- | ------------- | ----------- | -------------------------------------------------------------- | ---------------------------- |
-| **brainstorm-project** | Analyst       | No          | Explore solution approaches and architectures                  | Solution options + rationale |
-| **brainstorm-game**    | Analyst       | No          | Generate game concepts using creative techniques               | Game concepts + evaluation   |
-| **research**           | Analyst       | No          | Multi-type research (market/technical/competitive/user/domain) | Research reports             |
-| **product-brief**      | Analyst       | Recommended | Define product vision and strategy (interactive)               | Product Brief document       |
-| **game-brief**         | Game Designer | Recommended | Capture game vision before GDD (interactive)                   | Game Brief document          |
-
----
-
-## Workflow Descriptions
-
-### brainstorm-project
-
-**Purpose:** Generate multiple solution approaches through parallel ideation tracks (architecture, UX, integration, value).
-
-**Agent:** Analyst
-
-**When to Use:**
-
-- Unclear technical approach with business objectives
-- Multiple solution paths need evaluation
-- Hidden assumptions need discovery
-- Innovation beyond obvious solutions
-
-**Key Outputs:**
-
-- Architecture proposals with trade-off analysis
-- Value framework (prioritized features)
-- Risk analysis (dependencies, challenges)
-- Strategic recommendation with rationale
-
-**Example:** "We need a customer dashboard" → Options: Monolith SSR (faster), Microservices SPA (scalable), Hybrid (balanced) with recommendation.
-
----
-
-### brainstorm-game
-
-**Purpose:** Generate game concepts through systematic creative exploration using five brainstorming techniques.
-
-**Agent:** Analyst
-
-**When to Use:**
-
-- Generating original game concepts
-- Exploring variations on themes
-- Breaking creative blocks
-- Validating game ideas against constraints
-
-**Techniques Used:**
-
-- SCAMPER (systematic modification)
-- Mind Mapping (hierarchical exploration)
-- Lotus Blossom (radial expansion)
-- Six Thinking Hats (multi-perspective)
-- Random Word Association (lateral thinking)
-
-**Key Outputs:**
-
-- Method-specific artifacts (5 separate documents)
-- Consolidated concept document with feasibility
-- Design pillar alignment matrix
-
-**Example:** "Roguelike with psychological themes" → Emotions as characters, inner demons as enemies, therapy sessions as rest points, deck composition affects narrative.
-
----
-
-### research
-
-**Purpose:** Comprehensive multi-type research system consolidating market, technical, competitive, user, and domain analysis.
-
-**Agent:** Analyst
-
-**Research Types:**
-
-| Type            | Purpose                                                | Use When                            |
-| --------------- | ------------------------------------------------------ | ----------------------------------- |
-| **market**      | TAM/SAM/SOM, competitive analysis                      | Need market viability validation    |
-| **technical**   | Technology evaluation, ADRs                            | Choosing frameworks/platforms       |
-| **competitive** | Deep competitor analysis                               | Understanding competitive landscape |
-| **user**        | Customer insights, personas, JTBD                      | Need user understanding             |
-| **domain**      | Industry deep dives, trends                            | Understanding domain/industry       |
-| **deep_prompt** | Generate AI research prompts (ChatGPT, Claude, Gemini) | Need deeper AI-assisted research    |
-
-**Key Features:**
-
-- Real-time web research
-- Multiple analytical frameworks (Porter's Five Forces, SWOT, Technology Adoption Lifecycle)
-- Platform-specific optimization for deep_prompt type
-- Configurable research depth (quick/standard/comprehensive)
-
-**Example (market):** "SaaS project management tool" → TAM $50B, SAM $5B, SOM $50M, top competitors (Asana, Monday), positioning recommendation.
-
----
-
-### product-brief
-
-**Purpose:** Interactive product brief creation that guides strategic product vision definition.
-
-**Agent:** Analyst
-
-**When to Use:**
-
-- Starting new product/major feature initiative
-- Aligning stakeholders before detailed planning
-- Transitioning from exploration to strategy
-- Need executive-level product documentation
-
-**Modes:**
-
-- **Interactive Mode** (Recommended): Step-by-step collaborative development with probing questions
-- **YOLO Mode**: AI generates complete draft from context, then iterative refinement
-
-**Key Outputs:**
-
-- Executive summary
-- Problem statement with evidence
-- Proposed solution and differentiators
-- Target users (segmented)
-- MVP scope (ruthlessly defined)
-- Financial impact and ROI
-- Strategic alignment
-- Risks and open questions
-
-**Integration:** Feeds directly into PRD workflow (Phase 2).
-
----
-
-### game-brief
-
-**Purpose:** Lightweight interactive brainstorming session capturing game vision before Game Design Document.
-
-**Agent:** Game Designer
-
-**When to Use:**
-
-- Starting new game project
-- Exploring game ideas before committing
-- Pitching concepts to team/stakeholders
-- Validating market fit and feasibility
-
-**Game Brief vs GDD:**
-
-| Aspect       | Game Brief         | GDD                       |
-| ------------ | ------------------ | ------------------------- |
-| Purpose      | Validate concept   | Design for implementation |
-| Detail Level | High-level vision  | Detailed specs            |
-| Format       | Conversational     | Structured                |
-| Output       | Concise vision doc | Comprehensive design      |
-
-**Key Outputs:**
-
-- Game vision (concept, pitch)
-- Target market and positioning
-- Core gameplay pillars
-- Scope and constraints
-- Reference framework
-- Risk assessment
-- Success criteria
-
-**Integration:** Feeds into GDD workflow (Phase 2).
-
----
-
-## Decision Guide
-
-### Starting a Software Project
-
-```
-brainstorm-project (if unclear) → research (market/technical) → product-brief → Phase 2 (prd)
-```
-
-### Starting a Game Project
-
-```
-brainstorm-game (if generating concepts) → research (market/competitive) → game-brief → Phase 2 (gdd)
-```
-
-### Validating an Idea
-
-```
-research (market type) → product-brief or game-brief → Phase 2
-```
-
-### Technical Decision Only
-
-```
-research (technical type) → Use findings in Phase 3 (architecture)
-```
-
-### Understanding Market
-
-```
-research (market/competitive type) → product-brief → Phase 2
-```
-
----
-
-## Integration with Phase 2 (Planning)
-
-Analysis outputs feed directly into Planning:
-
-| Analysis Output             | Planning Input             |
-| --------------------------- | -------------------------- |
-| product-brief.md            | **prd** workflow           |
-| game-brief.md               | **gdd** workflow           |
-| market-research.md          | **prd** context            |
-| technical-research.md       | **architecture** (Phase 3) |
-| competitive-intelligence.md | **prd** positioning        |
-
-Planning workflows automatically load these documents if they exist in the output folder.
-
----
-
-## Best Practices
-
-### 1. Don't Over-Invest in Analysis
-
-Analysis is optional. If requirements are clear, skip to Phase 2 (Planning).
-
-### 2. Iterate Between Workflows
-
-Common pattern: brainstorm → research (validate) → brief (synthesize)
-
-### 3. Document Assumptions
-
-Analysis surfaces and validates assumptions. Document them explicitly for planning to challenge.
-
-### 4. Keep It Strategic
-
-Focus on "what" and "why", not "how". Leave implementation for Planning and Solutioning.
-
-### 5. Involve Stakeholders
-
-Use analysis workflows to align stakeholders before committing to detailed planning.
-
----
-
-## Common Patterns
-
-### Greenfield Software (Full Analysis)
-
-```
-1. brainstorm-project - explore approaches
-2. research (market) - validate viability
-3. product-brief - capture strategic vision
-4. → Phase 2: prd
-```
-
-### Greenfield Game (Full Analysis)
-
-```
-1. brainstorm-game - generate concepts
-2. research (competitive) - understand landscape
-3. game-brief - capture vision
-4. → Phase 2: gdd
-```
-
-### Skip Analysis (Clear Requirements)
-
-```
-→ Phase 2: prd or tech-spec directly
-```
-
-### Technical Research Only
-
-```
-1. research (technical) - evaluate technologies
-2. → Phase 3: architecture (use findings in ADRs)
-```
-
----
-
-## Related Documentation
-
-- [Phase 2: Planning Workflows](./workflows-planning.md) - Next phase
-- [Phase 3: Solutioning Workflows](./workflows-solutioning.md)
-- [Phase 4: Implementation Workflows](./workflows-implementation.md)
-- [Scale Adaptive System](./scale-adaptive-system.md) - Understanding project complexity
-- [Agents Guide](./agents-guide.md) - Complete agent reference
-
----
-
-## Troubleshooting
-
-**Q: Do I need to run all analysis workflows?**
-A: No! Analysis is entirely optional. Use only workflows that help you think through your problem.
-
-**Q: Which workflow should I start with?**
-A: If unsure, start with `research` (market type) to validate viability, then move to `product-brief` or `game-brief`.
-
-**Q: Can I skip straight to Planning?**
-A: Yes! If you know what you're building and why, skip Phase 1 entirely and start with Phase 2 (prd/gdd/tech-spec).
-
-**Q: How long should Analysis take?**
-A: Typically hours to 1-2 days. If taking longer, you may be over-analyzing. Move to Planning.
-
-**Q: What if I discover problems during Analysis?**
-A: That's the point! Analysis helps you fail fast and pivot before heavy planning investment.
-
-**Q: Should brownfield projects do Analysis?**
-A: Usually no. Start with `document-project` (Phase 0), then skip to Planning (Phase 2).
-
----
-
-_Phase 1 Analysis - Optional strategic thinking before commitment._

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

@@ -1,284 +0,0 @@
-# BMM Implementation Workflows (Phase 4)
-
-**Reading Time:** ~8 minutes
-
-## Overview
-
-Phase 4 (Implementation) workflows manage the iterative sprint-based development cycle using a **story-centric workflow** where each story moves through a defined lifecycle from creation to completion.
-
-**Key principle:** One story at a time, move it through the entire lifecycle before starting the next.
-
----
-
-## Phase 4 Workflow Lifecycle
-
-```mermaid
-%%{init: {'theme':'base', 'themeVariables': { 'primaryColor':'#fff','primaryTextColor':'#000','primaryBorderColor':'#000','lineColor':'#000','fontSize':'16px','fontFamily':'arial'}}}%%
-graph TB
-    subgraph Setup["<b>SPRINT SETUP - Run Once</b>"]
-        direction TB
-        SprintPlanning["<b>SM: sprint-planning</b><br/>Initialize sprint status file"]
-    end
-
-    subgraph EpicCycle["<b>EPIC CYCLE - Repeat Per Epic</b>"]
-        direction TB
-        EpicContext["<b>SM: epic-tech-context</b><br/>Generate epic technical guidance"]
-        ValidateEpic["<b>SM: validate-epic-tech-context</b><br/>(Optional validation)"]
-
-        EpicContext -.->|Optional| ValidateEpic
-        ValidateEpic -.-> StoryLoopStart
-        EpicContext --> StoryLoopStart[Start Story Loop]
-    end
-
-    subgraph StoryLoop["<b>STORY LIFECYCLE - Repeat Per Story</b>"]
-        direction TB
-
-        CreateStory["<b>SM: create-story</b><br/>Create next story from queue"]
-        ValidateStory["<b>SM: validate-create-story</b><br/>(Optional validation)"]
-        StoryContext["<b>SM: story-context</b><br/>Assemble dynamic context"]
-        StoryReady["<b>SM: story-ready-for-dev</b><br/>Mark ready without context"]
-        ValidateContext["<b>SM: validate-story-context</b><br/>(Optional validation)"]
-        DevStory["<b>DEV: develop-story</b><br/>Implement with tests"]
-        CodeReview["<b>DEV: code-review</b><br/>Senior dev review"]
-        StoryDone["<b>DEV: story-done</b><br/>Mark complete, advance queue"]
-
-        CreateStory -.->|Optional| ValidateStory
-        ValidateStory -.-> StoryContext
-        CreateStory --> StoryContext
-        CreateStory -.->|Alternative| StoryReady
-        StoryContext -.->|Optional| ValidateContext
-        ValidateContext -.-> DevStory
-        StoryContext --> DevStory
-        StoryReady -.-> DevStory
-        DevStory --> CodeReview
-        CodeReview -.->|Needs fixes| DevStory
-        CodeReview --> StoryDone
-        StoryDone -.->|Next story| CreateStory
-    end
-
-    subgraph EpicClose["<b>EPIC COMPLETION</b>"]
-        direction TB
-        Retrospective["<b>SM: epic-retrospective</b><br/>Post-epic lessons learned"]
-    end
-
-    subgraph Support["<b>SUPPORTING WORKFLOWS</b>"]
-        direction TB
-        CorrectCourse["<b>SM: correct-course</b><br/>Handle mid-sprint changes"]
-        WorkflowStatus["<b>Any Agent: workflow-status</b><br/>Check what's next"]
-    end
-
-    Setup --> EpicCycle
-    EpicCycle --> StoryLoop
-    StoryLoop --> EpicClose
-    EpicClose -.->|Next epic| EpicCycle
-    StoryLoop -.->|If issues arise| CorrectCourse
-    StoryLoop -.->|Anytime| WorkflowStatus
-    EpicCycle -.->|Anytime| WorkflowStatus
-
-    style Setup fill:#e3f2fd,stroke:#1565c0,stroke-width:3px,color:#000
-    style EpicCycle fill:#c5e1a5,stroke:#33691e,stroke-width:3px,color:#000
-    style StoryLoop fill:#f3e5f5,stroke:#6a1b9a,stroke-width:3px,color:#000
-    style EpicClose fill:#ffcc80,stroke:#e65100,stroke-width:3px,color:#000
-    style Support fill:#fff3e0,stroke:#e65100,stroke-width:3px,color:#000
-
-    style SprintPlanning fill:#90caf9,stroke:#0d47a1,stroke-width:2px,color:#000
-    style EpicContext fill:#aed581,stroke:#1b5e20,stroke-width:2px,color:#000
-    style ValidateEpic fill:#c5e1a5,stroke:#33691e,stroke-width:1px,color:#000
-    style CreateStory fill:#ce93d8,stroke:#4a148c,stroke-width:2px,color:#000
-    style ValidateStory fill:#e1bee7,stroke:#6a1b9a,stroke-width:1px,color:#000
-    style StoryContext fill:#ce93d8,stroke:#4a148c,stroke-width:2px,color:#000
-    style StoryReady fill:#ce93d8,stroke:#4a148c,stroke-width:2px,color:#000
-    style ValidateContext fill:#e1bee7,stroke:#6a1b9a,stroke-width:1px,color:#000
-    style DevStory fill:#a5d6a7,stroke:#1b5e20,stroke-width:2px,color:#000
-    style CodeReview fill:#a5d6a7,stroke:#1b5e20,stroke-width:2px,color:#000
-    style StoryDone fill:#a5d6a7,stroke:#1b5e20,stroke-width:2px,color:#000
-    style Retrospective fill:#ffb74d,stroke:#e65100,stroke-width:2px,color:#000
-```
-
----
-
-## Quick Reference
-
-| Workflow                       | Agent | When                             | Purpose                                     |
-| ------------------------------ | ----- | -------------------------------- | ------------------------------------------- |
-| **sprint-planning**            | SM    | Once at Phase 4 start            | Initialize sprint tracking file             |
-| **epic-tech-context**          | SM    | Per epic                         | Generate epic-specific technical guidance   |
-| **validate-epic-tech-context** | SM    | Optional after epic-tech-context | Validate tech spec against checklist        |
-| **create-story**               | SM    | Per story                        | Create next story from epic backlog         |
-| **validate-create-story**      | SM    | Optional after create-story      | Independent validation of story draft       |
-| **story-context**              | SM    | Optional per story               | Assemble dynamic story context XML          |
-| **validate-story-context**     | SM    | Optional after story-context     | Validate story context against checklist    |
-| **story-ready-for-dev**        | SM    | Optional per story               | Mark story ready without generating context |
-| **develop-story**              | DEV   | Per story                        | Implement story with tests                  |
-| **code-review**                | DEV   | Per story                        | Senior dev quality review                   |
-| **story-done**                 | DEV   | Per story                        | Mark complete and advance queue             |
-| **epic-retrospective**         | SM    | After epic complete              | Review lessons and extract insights         |
-| **correct-course**             | SM    | When issues arise                | Handle significant mid-sprint changes       |
-| **workflow-status**            | Any   | Anytime                          | Check "what should I do now?"               |
-
----
-
-## Agent Roles
-
-### SM (Scrum Master) - Primary Implementation Orchestrator
-
-**Workflows:** sprint-planning, epic-tech-context, validate-epic-tech-context, create-story, validate-create-story, story-context, validate-story-context, story-ready-for-dev, epic-retrospective, correct-course
-
-**Responsibilities:**
-
-- Initialize and maintain sprint tracking
-- Generate technical context (epic and story level)
-- Orchestrate story lifecycle with optional validations
-- Mark stories ready for development
-- Handle course corrections
-- Facilitate retrospectives
-
-### DEV (Developer) - Implementation and Quality
-
-**Workflows:** develop-story, code-review, story-done
-
-**Responsibilities:**
-
-- Implement stories with tests
-- Perform senior developer code reviews
-- Mark stories complete and advance queue
-- Ensure quality and adherence to standards
-
----
-
-## Story Lifecycle States
-
-Stories move through these states in the sprint status file:
-
-1. **TODO** - Story identified but not started
-2. **IN PROGRESS** - Story being implemented (create-story → story-context → dev-story)
-3. **READY FOR REVIEW** - Implementation complete, awaiting code review
-4. **DONE** - Accepted and complete
-
----
-
-## Typical Sprint Flow
-
-### Sprint 0 (Planning Phase)
-
-- Complete Phases 1-3 (Analysis, Planning, Solutioning)
-- PRD/GDD + Architecture + Epics ready
-
-### Sprint 1+ (Implementation Phase)
-
-**Start of Phase 4:**
-
-1. SM runs `sprint-planning` (once)
-
-**Per Epic:**
-
-1. SM runs `epic-tech-context`
-2. SM optionally runs `validate-epic-tech-context`
-
-**Per Story (repeat until epic complete):**
-
-1. SM runs `create-story`
-2. SM optionally runs `validate-create-story`
-3. SM runs `story-context` OR `story-ready-for-dev` (choose one)
-4. SM optionally runs `validate-story-context` (if story-context was used)
-5. DEV runs `develop-story`
-6. DEV runs `code-review`
-7. If code review passes: DEV runs `story-done`
-8. If code review finds issues: DEV fixes in `develop-story`, then back to code-review
-
-**After Epic Complete:**
-
-- SM runs `epic-retrospective`
-- Move to next epic (start with `epic-tech-context` again)
-
-**As Needed:**
-
-- Run `workflow-status` anytime to check progress
-- Run `correct-course` if significant changes needed
-
----
-
-## Key Principles
-
-### One Story at a Time
-
-Complete each story's full lifecycle before starting the next. This prevents context switching and ensures quality.
-
-### Epic-Level Technical Context
-
-Generate detailed technical guidance per epic (not per story) using `epic-tech-context`. This provides just-in-time architecture without upfront over-planning.
-
-### Story Context (Optional)
-
-Use `story-context` to assemble focused context XML for each story, pulling from PRD, architecture, epic context, and codebase docs. Alternatively, use `story-ready-for-dev` to mark a story ready without generating context XML.
-
-### Quality Gates
-
-Every story goes through `code-review` before being marked done. No exceptions.
-
-### Continuous Tracking
-
-The `sprint-status.yaml` file is the single source of truth for all implementation progress.
-
----
-
-## Common Patterns
-
-### Level 0-1 (Quick Flow)
-
-```
-tech-spec (PM)
-  → sprint-planning (SM)
-  → story loop (SM/DEV)
-```
-
-### Level 2-4 (BMad Method / Enterprise)
-
-```
-PRD + Architecture (PM/Architect)
-  → solutioning-gate-check (Architect)
-  → sprint-planning (SM, once)
-  → [Per Epic]:
-      epic-tech-context (SM)
-      → story loop (SM/DEV)
-      → epic-retrospective (SM)
-  → [Next Epic]
-```
-
----
-
-## Related Documentation
-
-- [Phase 2: Planning Workflows](./workflows-planning.md)
-- [Phase 3: Solutioning Workflows](./workflows-solutioning.md)
-- [Quick Spec Flow](./quick-spec-flow.md) - Level 0-1 fast track
-- [Scale Adaptive System](./scale-adaptive-system.md) - Understanding project levels
-
----
-
-## Troubleshooting
-
-**Q: Which workflow should I run next?**
-A: Run `workflow-status` - it reads the sprint status file and tells you exactly what to do.
-
-**Q: Story needs significant changes mid-implementation?**
-A: Run `correct-course` to analyze impact and route appropriately.
-
-**Q: Do I run epic-tech-context for every story?**
-A: No! Run once per epic, not per story. Use `story-context` or `story-ready-for-dev` per story instead.
-
-**Q: Do I have to use story-context for every story?**
-A: No, it's optional. You can use `story-ready-for-dev` to mark a story ready without generating context XML.
-
-**Q: Can I work on multiple stories in parallel?**
-A: Not recommended. Complete one story's full lifecycle before starting the next. Prevents context switching and ensures quality.
-
-**Q: What if code review finds issues?**
-A: DEV runs `develop-story` to make fixes, re-runs tests, then runs `code-review` again until it passes.
-
-**Q: When do I run validations?**
-A: Validations are optional quality gates. Use them when you want independent review of epic tech specs, story drafts, or story context before proceeding.
-
----
-
-_Phase 4 Implementation - One story at a time, done right._