@devo-bmad-custom/agent-orchestration 1.0.1 → 1.0.3

package/src/bmm/workflows/3-solutioning/create-epics-and-stories/steps/step-02-design-epics.md

@@ -1,124 +1,124 @@
----
-name: 'step-02-design-epics'
-description: 'Design and approve the epics_list that will organize all requirements into user-value-focused epics'
-
-# Path Definitions
-workflow_path: '{project-root}/_bmad/bmm/workflows/3-solutioning/create-epics-and-stories'
-
-# File References
-thisStepFile: './step-02-design-epics.md'
-nextStepFile: './step-03-create-stories.md'
-workflowFile: '{workflow_path}/workflow.md'
-outputFile: '{planning_artifacts}/epics.md'
-
-# Task References
-advancedElicitationTask: '{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml'
-partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
-
-# Template References
-epicsTemplate: '{workflow_path}/templates/epics-template.md'
----
-
-# Step 2: Design Epic List
-
-**Goal:** Design and get explicit approval for the `epics_list` that organizes all requirements into user-value-focused epics.
-
-**Rules:** Read this entire file before acting. Focus only on the epics_list — do not create individual stories. Each epic must be standalone and enable future epics without requiring them.
-
----
-
-## EPIC DESIGN PROCESS
-
-### 1. Review Extracted Requirements
-
-Load {outputFile} and review FRs, NFRs, and additional requirements from Step 1.
-
-### 2. Epic Design Principles
-
-**Organize by USER VALUE, not technical layers:**
-
-✅ CORRECT — each epic delivers standalone user value:
-- Epic 1: User Authentication & Profiles (complete auth system)
-- Epic 2: Content Creation (uses auth, creates content)
-- Epic 3: Social Interaction (uses auth + content)
-
-❌ WRONG — technical milestones with no direct user value:
-- Epic 1: Database Setup
-- Epic 2: API Development
-- Epic 3: Frontend Components
-
-**Dependency rule:** Epic N+1 can build on previous epics but must deliver complete functionality for its own domain. Epic 2 must not require Epic 3 to function.
-
-### 3. Design Epic Structure
-
-**A. Identify user value themes** — look for natural FR groupings, user journeys, user types and goals.
-
-**B. For each proposed epic, define:**
-1. Epic title (user-centric)
-2. User outcome (what users can accomplish after this epic)
-3. FR coverage (which FR numbers it addresses)
-4. Any technical/UX notes
-
-**C. Format the epics_list:**
-
-```
-## Epic List
-
-### Epic 1: [Epic Title]
-[Epic goal — what users can accomplish]
-**FRs covered:** FR1, FR2, FR3
-
-### Epic 2: [Epic Title]
-[Epic goal]
-**FRs covered:** FR4, FR5, FR6
-```
-
-### 4. Create Requirements Coverage Map
-
-```
-### FR Coverage Map
-
-FR1: Epic 1 - [Brief description]
-FR2: Epic 1 - [Brief description]
-FR3: Epic 2 - [Brief description]
-```
-
-### 5. Collaborative Refinement
-
-Ask:
-- "Does this epic structure align with your product vision?"
-- "Are all user outcomes properly captured?"
-- "Should we adjust any epic groupings?"
-
-### 6. Get Final Approval
-
-**Must get explicit user approval:** "Do you approve this epic structure for proceeding to story creation?"
-
-If changes are requested: adjust, update epics_list, re-present for approval. Repeat until approved.
-
-### 7. Save and Present Menu
-
-After approval, update {outputFile}:
-1. Replace `{{epics_list}}` with the approved epic list
-2. Replace `{{requirements_coverage_map}}` with the coverage map
-
-Display: **`Select an Option: [A] Advanced Elicitation [P] Party Mode [AR] Adversarial Review [C] Continue`**
-
-**Menu handling:**
-- **A:** Read fully and follow: {advancedElicitationTask}
-- **P:** Read fully and follow: {partyModeWorkflow}
-- **AR:** Execute `{project-root}/_bmad/core/tasks/review-adversarial-general.xml` — display findings, then redisplay menu
-- **C:** Save approved epics_list to {outputFile}, update frontmatter, then read fully and follow: {nextStepFile}
-- **Any other input:** Respond, then redisplay menu
-
-Always halt and wait for user input at this menu.
-
----
-
-## SUCCESS METRICS
-
-- Epics organized around user value (not technical layers)
-- All FRs mapped to specific epics
-- Requirements coverage map completed
-- User gives explicit approval for epic structure
-- Document updated with approved epics
+---
+name: 'step-02-design-epics'
+description: 'Design and approve the epics_list that will organize all requirements into user-value-focused epics'
+
+# Path Definitions
+workflow_path: '{project-root}/_bmad/bmm/workflows/3-solutioning/create-epics-and-stories'
+
+# File References
+thisStepFile: './step-02-design-epics.md'
+nextStepFile: './step-03-create-stories.md'
+workflowFile: '{workflow_path}/workflow.md'
+outputFile: '{planning_artifacts}/epics.md'
+
+# Task References
+advancedElicitationTask: '{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml'
+partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
+
+# Template References
+epicsTemplate: '{workflow_path}/templates/epics-template.md'
+---
+
+# Step 2: Design Epic List
+
+**Goal:** Design and get explicit approval for the `epics_list` that organizes all requirements into user-value-focused epics.
+
+**Rules:** Read this entire file before acting. Focus only on the epics_list — do not create individual stories. Each epic must be standalone and enable future epics without requiring them.
+
+---
+
+## EPIC DESIGN PROCESS
+
+### 1. Review Extracted Requirements
+
+Load {outputFile} and review FRs, NFRs, and additional requirements from Step 1.
+
+### 2. Epic Design Principles
+
+**Organize by USER VALUE, not technical layers:**
+
+✅ CORRECT — each epic delivers standalone user value:
+- Epic 1: User Authentication & Profiles (complete auth system)
+- Epic 2: Content Creation (uses auth, creates content)
+- Epic 3: Social Interaction (uses auth + content)
+
+❌ WRONG — technical milestones with no direct user value:
+- Epic 1: Database Setup
+- Epic 2: API Development
+- Epic 3: Frontend Components
+
+**Dependency rule:** Epic N+1 can build on previous epics but must deliver complete functionality for its own domain. Epic 2 must not require Epic 3 to function.
+
+### 3. Design Epic Structure
+
+**A. Identify user value themes** — look for natural FR groupings, user journeys, user types and goals.
+
+**B. For each proposed epic, define:**
+1. Epic title (user-centric)
+2. User outcome (what users can accomplish after this epic)
+3. FR coverage (which FR numbers it addresses)
+4. Any technical/UX notes
+
+**C. Format the epics_list:**
+
+```
+## Epic List
+
+### Epic 1: [Epic Title]
+[Epic goal — what users can accomplish]
+**FRs covered:** FR1, FR2, FR3
+
+### Epic 2: [Epic Title]
+[Epic goal]
+**FRs covered:** FR4, FR5, FR6
+```
+
+### 4. Create Requirements Coverage Map
+
+```
+### FR Coverage Map
+
+FR1: Epic 1 - [Brief description]
+FR2: Epic 1 - [Brief description]
+FR3: Epic 2 - [Brief description]
+```
+
+### 5. Collaborative Refinement
+
+Ask:
+- "Does this epic structure align with your product vision?"
+- "Are all user outcomes properly captured?"
+- "Should we adjust any epic groupings?"
+
+### 6. Get Final Approval
+
+**Must get explicit user approval:** "Do you approve this epic structure for proceeding to story creation?"
+
+If changes are requested: adjust, update epics_list, re-present for approval. Repeat until approved.
+
+### 7. Save and Present Menu
+
+After approval, update {outputFile}:
+1. Replace `{{epics_list}}` with the approved epic list
+2. Replace `{{requirements_coverage_map}}` with the coverage map
+
+Display: **`Select an Option: [A] Advanced Elicitation [P] Party Mode [AR] Adversarial Review [C] Continue`**
+
+**Menu handling:**
+- **A:** Read fully and follow: {advancedElicitationTask}
+- **P:** Read fully and follow: {partyModeWorkflow}
+- **AR:** Execute `{project-root}/_bmad/core/tasks/review-adversarial-general.xml` — display findings, then redisplay menu
+- **C:** Save approved epics_list to {outputFile}, update frontmatter, then read fully and follow: {nextStepFile}
+- **Any other input:** Respond, then redisplay menu
+
+Always halt and wait for user input at this menu.
+
+---
+
+## SUCCESS METRICS
+
+- Epics organized around user value (not technical layers)
+- All FRs mapped to specific epics
+- Requirements coverage map completed
+- User gives explicit approval for epic structure
+- Document updated with approved epics

package/src/bmm/workflows/3-solutioning/create-epics-and-stories/steps/step-03-create-stories.md

@@ -1,122 +1,122 @@
----
-name: 'step-03-create-stories'
-description: 'Generate all epics with their stories following the template structure'
-
-# Path Definitions
-workflow_path: '{project-root}/_bmad/bmm/workflows/3-solutioning/create-epics-and-stories'
-
-# File References
-thisStepFile: './step-03-create-stories.md'
-nextStepFile: './step-04-final-validation.md'
-workflowFile: '{workflow_path}/workflow.md'
-outputFile: '{planning_artifacts}/epics.md'
-
-# Task References
-advancedElicitationTask: '{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml'
-partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
-
-# Template References
-epicsTemplate: '{workflow_path}/templates/epics-template.md'
----
-
-# Step 3: Generate Epics and Stories
-
-**Goal:** Generate all epics with their stories based on the approved epics_list, following the template structure exactly.
-
-**Rules:** Process epics sequentially. Each story must be completable by a single dev agent. Stories must NOT depend on future stories within the same epic.
-
----
-
-## STORY GENERATION PROCESS
-
-### 1. Load Approved Epic Structure
-
-Load {outputFile} and review: approved epics_list, FR coverage map, all requirements, and template structure.
-
-### 2. Story Creation Guidelines
-
-**Database/entity principle:** Create tables/entities ONLY when needed by the story — not all upfront in Epic 1.
-
-**Story dependency principle:** Each story must be completable based only on previous stories. No forward dependencies.
-
-**Story format:**
-
-```
-### Story {N}.{M}: {story_title}
-
-As a {user_type},
-I want {capability},
-So that {value_benefit}.
-
-**Acceptance Criteria:**
-
-**Given** {precondition}
-**When** {action}
-**Then** {expected_outcome}
-**And** {additional_criteria}
-```
-
-✅ Good stories: "User Registration with Email", "User Login with Password", "Create New Blog Post"
-❌ Bad stories: "Set up database", "Create all models", "Login UI (depends on Story 1.3 API)"
-
-### 3. Process Epics Sequentially
-
-For each epic in the approved list:
-
-**A. Epic Overview** — display epic number, title, goal, FRs covered, relevant NFRs.
-
-**B. Story Breakdown** — work with user to identify distinct user capabilities, ensure logical flow, size stories appropriately.
-
-**C. For each story:**
-1. Story title (clear, action-oriented)
-2. User story (As a / I want / So that)
-3. Acceptance criteria (Given/When/Then — specific, independently testable, include edge cases)
-
-**D. Collaborative Review** — present each story and ask:
-- "Does this story capture the requirement correctly?"
-- "Is the scope appropriate for a single dev session?"
-- "Are the acceptance criteria complete and testable?"
-
-**E. Append to {outputFile}** when approved — use correct numbering and proper markdown.
-
-### 4. Epic Completion
-
-After all stories for an epic are complete: display epic summary, story count, verify FR coverage, confirm with user before proceeding to next epic.
-
-### 5. Final Document Check
-
-After all epics and stories are generated, verify:
-- Template structure followed exactly
-- All placeholders replaced
-- All FRs covered
-- Formatting consistent
-
-**Required structure:**
-1. Overview section with project name
-2. Requirements Inventory (all three subsections populated)
-3. FR Coverage Map
-4. Epic List with approved structure
-5. Epic sections (each with goal + stories with Given/When/Then ACs)
-
-### 6. Present Final Menu
-
-Display: **`Select an Option: [A] Advanced Elicitation [P] Party Mode [AR] Adversarial Review [C] Continue`**
-
-**Menu handling:**
-- **A:** Read fully and follow: {advancedElicitationTask}
-- **P:** Read fully and follow: {partyModeWorkflow}
-- **AR:** Execute `{project-root}/_bmad/core/tasks/review-adversarial-general.xml` — display findings, then redisplay menu
-- **C:** Save content to {outputFile}, update frontmatter, then read fully and follow: {nextStepFile}
-- **Any other input:** Respond, then redisplay menu
-
-Always halt and wait for user input at this menu.
-
----
-
-## SUCCESS METRICS
-
-- All epics processed in sequence
-- Stories created for each epic following template exactly
-- All FRs covered by stories
-- Stories appropriately sized with specific, testable acceptance criteria
-- Document complete and ready for development
+---
+name: 'step-03-create-stories'
+description: 'Generate all epics with their stories following the template structure'
+
+# Path Definitions
+workflow_path: '{project-root}/_bmad/bmm/workflows/3-solutioning/create-epics-and-stories'
+
+# File References
+thisStepFile: './step-03-create-stories.md'
+nextStepFile: './step-04-final-validation.md'
+workflowFile: '{workflow_path}/workflow.md'
+outputFile: '{planning_artifacts}/epics.md'
+
+# Task References
+advancedElicitationTask: '{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml'
+partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
+
+# Template References
+epicsTemplate: '{workflow_path}/templates/epics-template.md'
+---
+
+# Step 3: Generate Epics and Stories
+
+**Goal:** Generate all epics with their stories based on the approved epics_list, following the template structure exactly.
+
+**Rules:** Process epics sequentially. Each story must be completable by a single dev agent. Stories must NOT depend on future stories within the same epic.
+
+---
+
+## STORY GENERATION PROCESS
+
+### 1. Load Approved Epic Structure
+
+Load {outputFile} and review: approved epics_list, FR coverage map, all requirements, and template structure.
+
+### 2. Story Creation Guidelines
+
+**Database/entity principle:** Create tables/entities ONLY when needed by the story — not all upfront in Epic 1.
+
+**Story dependency principle:** Each story must be completable based only on previous stories. No forward dependencies.
+
+**Story format:**
+
+```
+### Story {N}.{M}: {story_title}
+
+As a {user_type},
+I want {capability},
+So that {value_benefit}.
+
+**Acceptance Criteria:**
+
+**Given** {precondition}
+**When** {action}
+**Then** {expected_outcome}
+**And** {additional_criteria}
+```
+
+✅ Good stories: "User Registration with Email", "User Login with Password", "Create New Blog Post"
+❌ Bad stories: "Set up database", "Create all models", "Login UI (depends on Story 1.3 API)"
+
+### 3. Process Epics Sequentially
+
+For each epic in the approved list:
+
+**A. Epic Overview** — display epic number, title, goal, FRs covered, relevant NFRs.
+
+**B. Story Breakdown** — work with user to identify distinct user capabilities, ensure logical flow, size stories appropriately.
+
+**C. For each story:**
+1. Story title (clear, action-oriented)
+2. User story (As a / I want / So that)
+3. Acceptance criteria (Given/When/Then — specific, independently testable, include edge cases)
+
+**D. Collaborative Review** — present each story and ask:
+- "Does this story capture the requirement correctly?"
+- "Is the scope appropriate for a single dev session?"
+- "Are the acceptance criteria complete and testable?"
+
+**E. Append to {outputFile}** when approved — use correct numbering and proper markdown.
+
+### 4. Epic Completion
+
+After all stories for an epic are complete: display epic summary, story count, verify FR coverage, confirm with user before proceeding to next epic.
+
+### 5. Final Document Check
+
+After all epics and stories are generated, verify:
+- Template structure followed exactly
+- All placeholders replaced
+- All FRs covered
+- Formatting consistent
+
+**Required structure:**
+1. Overview section with project name
+2. Requirements Inventory (all three subsections populated)
+3. FR Coverage Map
+4. Epic List with approved structure
+5. Epic sections (each with goal + stories with Given/When/Then ACs)
+
+### 6. Present Final Menu
+
+Display: **`Select an Option: [A] Advanced Elicitation [P] Party Mode [AR] Adversarial Review [C] Continue`**
+
+**Menu handling:**
+- **A:** Read fully and follow: {advancedElicitationTask}
+- **P:** Read fully and follow: {partyModeWorkflow}
+- **AR:** Execute `{project-root}/_bmad/core/tasks/review-adversarial-general.xml` — display findings, then redisplay menu
+- **C:** Save content to {outputFile}, update frontmatter, then read fully and follow: {nextStepFile}
+- **Any other input:** Respond, then redisplay menu
+
+Always halt and wait for user input at this menu.
+
+---
+
+## SUCCESS METRICS
+
+- All epics processed in sequence
+- Stories created for each epic following template exactly
+- All FRs covered by stories
+- Stories appropriately sized with specific, testable acceptance criteria
+- Document complete and ready for development

package/src/bmm/workflows/3-solutioning/create-epics-and-stories/steps/step-04-final-validation.md

@@ -1,84 +1,84 @@
----
-name: 'step-04-final-validation'
-description: 'Validate complete coverage of all requirements and ensure implementation readiness'
-
-# Path Definitions
-workflow_path: '{project-root}/_bmad/bmm/workflows/3-solutioning/create-epics-and-stories'
-
-# File References
-thisStepFile: './step-04-final-validation.md'
-workflowFile: '{workflow_path}/workflow.md'
-outputFile: '{planning_artifacts}/epics.md'
-
-# Task References
-advancedElicitationTask: '{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml'
-partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
-
-# Template References
-epicsTemplate: '{workflow_path}/templates/epics-template.md'
----
-
-# Step 4: Final Validation
-
-**Goal:** Validate complete requirements coverage and confirm stories are ready for development. This step is automated — run all checks and fix any issues found, then auto-proceed to completion.
-
----
-
-## VALIDATION PROCESS
-
-Run all checks sequentially. Fix any issues found before finalizing.
-
-### 1. FR Coverage Validation
-
-Go through each FR from the Requirements Inventory — verify it appears in at least one story with acceptance criteria that fully address it. No FRs may be uncovered.
-
-### 2. Architecture Implementation Validation
-
-**Starter template check:** If Architecture specifies a starter template, Epic 1 Story 1 must be "Set up initial project from starter template."
-
-**Database validation:** Tables/entities must be created only when first needed by a story — not all upfront in Epic 1.
-
-### 3. Story Quality Validation
-
-Each story must:
-- Be completable by a single dev agent
-- Have clear acceptance criteria
-- Have no forward dependencies (can only depend on previous stories)
-- Be implementable without waiting for future stories
-
-### 4. Epic Structure Validation
-
-- Epics deliver user value, not technical milestones
-- Dependencies flow naturally
-- No big upfront technical work
-
-### 5. Dependency Validation
-
-**Epic independence:** Each epic delivers complete functionality for its domain. Epic 2 must not require Epic 3 to function.
-
-**Within-epic story order:** Story N.2 uses only Story N.1 output; Story N.3 uses only Stories N.1 and N.2 outputs. No story references features not yet implemented.
-
-### 6. Fix Issues and Finalize
-
-If any validation fails, fix the issue in {outputFile} before proceeding.
-
-When all validations pass:
-- Update any remaining placeholders
-- Ensure proper formatting
-- Save the final {outputFile}
-
-### 7. Complete
-
-Write the validated output to {outputFile}, update frontmatter, then immediately load and execute: `{project-root}/_bmad/core/tasks/help.md`
-
-Upon completion, offer to answer any questions about the Epics and Stories.
-
----
-
-## SUCCESS METRICS
-
-- All FRs covered by at least one story
-- No forward story dependencies
-- Epics deliver user value
-- Starter template handled in Epic 1 Story 1 (if applicable)
-- Document finalized and ready for development
+---
+name: 'step-04-final-validation'
+description: 'Validate complete coverage of all requirements and ensure implementation readiness'
+
+# Path Definitions
+workflow_path: '{project-root}/_bmad/bmm/workflows/3-solutioning/create-epics-and-stories'
+
+# File References
+thisStepFile: './step-04-final-validation.md'
+workflowFile: '{workflow_path}/workflow.md'
+outputFile: '{planning_artifacts}/epics.md'
+
+# Task References
+advancedElicitationTask: '{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml'
+partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
+
+# Template References
+epicsTemplate: '{workflow_path}/templates/epics-template.md'
+---
+
+# Step 4: Final Validation
+
+**Goal:** Validate complete requirements coverage and confirm stories are ready for development. This step is automated — run all checks and fix any issues found, then auto-proceed to completion.
+
+---
+
+## VALIDATION PROCESS
+
+Run all checks sequentially. Fix any issues found before finalizing.
+
+### 1. FR Coverage Validation
+
+Go through each FR from the Requirements Inventory — verify it appears in at least one story with acceptance criteria that fully address it. No FRs may be uncovered.
+
+### 2. Architecture Implementation Validation
+
+**Starter template check:** If Architecture specifies a starter template, Epic 1 Story 1 must be "Set up initial project from starter template."
+
+**Database validation:** Tables/entities must be created only when first needed by a story — not all upfront in Epic 1.
+
+### 3. Story Quality Validation
+
+Each story must:
+- Be completable by a single dev agent
+- Have clear acceptance criteria
+- Have no forward dependencies (can only depend on previous stories)
+- Be implementable without waiting for future stories
+
+### 4. Epic Structure Validation
+
+- Epics deliver user value, not technical milestones
+- Dependencies flow naturally
+- No big upfront technical work
+
+### 5. Dependency Validation
+
+**Epic independence:** Each epic delivers complete functionality for its domain. Epic 2 must not require Epic 3 to function.
+
+**Within-epic story order:** Story N.2 uses only Story N.1 output; Story N.3 uses only Stories N.1 and N.2 outputs. No story references features not yet implemented.
+
+### 6. Fix Issues and Finalize
+
+If any validation fails, fix the issue in {outputFile} before proceeding.
+
+When all validations pass:
+- Update any remaining placeholders
+- Ensure proper formatting
+- Save the final {outputFile}
+
+### 7. Complete
+
+Write the validated output to {outputFile}, update frontmatter, then immediately load and execute: `{project-root}/_bmad/core/tasks/help.md`
+
+Upon completion, offer to answer any questions about the Epics and Stories.
+
+---
+
+## SUCCESS METRICS
+
+- All FRs covered by at least one story
+- No forward story dependencies
+- Epics deliver user value
+- Starter template handled in Epic 1 Story 1 (if applicable)
+- Document finalized and ready for development