diff --git a/src/bmm/workflows/3-solutioning/check-implementation-readiness/steps/step-01-document-discovery.md b/src/bmm/workflows/3-solutioning/check-implementation-readiness/steps/step-01-document-discovery.md index 877193f3d..1c829023c 100644 --- a/src/bmm/workflows/3-solutioning/check-implementation-readiness/steps/step-01-document-discovery.md +++ b/src/bmm/workflows/3-solutioning/check-implementation-readiness/steps/step-01-document-discovery.md @@ -81,6 +81,21 @@ Search for each document type using these patterns: - Whole: `{planning_artifacts}/*ux*.md` - Sharded: `{planning_artifacts}/*ux*/index.md` and related files +#### E. Enterprise Track Documents (if applicable) + +Check the PRD frontmatter for `track: enterprise`. If Enterprise track: + +- **StRS:** `{planning_artifacts}/*strs*.md` +- **SyRS:** `{planning_artifacts}/*syrs*.md` +- **RTM:** `{planning_artifacts}/*rtm*.md` + +Flag missing Enterprise documents: +``` +⚠️ ENTERPRISE TRACK: Required document not found +- StRS/SyRS/RTM document not found +- Enterprise track requires these for full readiness assessment +``` + ### 3. Organize Findings For each document type found: diff --git a/src/bmm/workflows/3-solutioning/check-implementation-readiness/steps/step-06-final-assessment.md b/src/bmm/workflows/3-solutioning/check-implementation-readiness/steps/step-06-final-assessment.md index d0e15bc02..f4a898f90 100644 --- a/src/bmm/workflows/3-solutioning/check-implementation-readiness/steps/step-06-final-assessment.md +++ b/src/bmm/workflows/3-solutioning/check-implementation-readiness/steps/step-06-final-assessment.md @@ -63,6 +63,48 @@ Check the {outputFile} for sections added by previous steps: - UX Alignment issues - Epic Quality violations +### 2b. Enterprise Track Additional Checks (if applicable) + +If the project is Enterprise track (check PRD frontmatter for `track: enterprise`), perform these additional validations: + +**StRS Completeness:** +- [ ] StRS document exists and follows ISO 29148 Clause 7 structure +- [ ] All 7 major sections present (Introduction, References, Business Mgmt, Operational, User, System Concept, Constraints) +- [ ] StRS status is at least 'review' (check frontmatter) + +**SyRS Completeness:** +- [ ] SyRS document exists and follows ISO 29148 Clause 8 structure +- [ ] System functional requirements mapped from PRD +- [ ] System interfaces defined +- [ ] Verification plan for each system requirement +- [ ] SyRS status is at least 'review' (check frontmatter) + +**RTM Integrity:** +- [ ] RTM document exists with bidirectional traceability +- [ ] StRS → SyRS traceability present (forward coverage > 90%) +- [ ] SyRS → PRD traceability present (forward coverage > 90%) +- [ ] PRD → Stories traceability present (forward coverage > 95%) +- [ ] No orphan requirements at any level +- [ ] All requirement statuses documented + +**Verification Method Assignment:** +- [ ] Every FR in PRD has a verification method assigned (Inspection / Analysis / Demonstration / Test) +- [ ] Every SyRS requirement has a verification method assigned +- [ ] Verification plan section exists in PRD + +**Cross-Document Consistency:** +- [ ] StRS scope aligns with PRD scope +- [ ] SyRS interfaces match Architecture interfaces +- [ ] No terminology contradictions across documents +- [ ] Requirement priorities consistent across levels + +**Baseline Status:** +- [ ] All requirement documents have version numbers in frontmatter +- [ ] Baseline version established (or ready to establish) +- [ ] Change history documented in each requirement document + +Add Enterprise assessment findings to the report under a dedicated "Enterprise Track Assessment" section. + ### 3. Add Final Assessment Section Append to {outputFile}: diff --git a/src/bmm/workflows/3-solutioning/create-epics-and-stories/steps/step-01-validate-prerequisites.md b/src/bmm/workflows/3-solutioning/create-epics-and-stories/steps/step-01-validate-prerequisites.md index c8d6b1330..85cbc64a6 100644 --- a/src/bmm/workflows/3-solutioning/create-epics-and-stories/steps/step-01-validate-prerequisites.md +++ b/src/bmm/workflows/3-solutioning/create-epics-and-stories/steps/step-01-validate-prerequisites.md @@ -91,6 +91,14 @@ Search for required documents using these patterns (sharded means a large docume 1. `{planning_artifacts}/*ux*.md` (whole document) 2. `{planning_artifacts}/*ux*/index.md` (sharded version) +**Enterprise Track Documents (if PRD frontmatter has `track: enterprise`):** + +1. **StRS:** `{planning_artifacts}/*strs*.md` - For requirement source traceability +2. **SyRS:** `{planning_artifacts}/*syrs*.md` - For system requirement references +3. **RTM:** `{planning_artifacts}/*rtm*.md` - For existing traceability matrix + +If Enterprise track: these documents provide source requirement IDs that stories MUST reference. + Before proceeding, Ask the user if there are any other documents to include for analysis, and if anything found should be excluded. Wait for user confirmation. Once confirmed, create the {outputFile} from the {epicsTemplate} and in the front matter list the files in the array of `inputDocuments: []`. ### 3. Extract Functional Requirements (FRs) diff --git a/src/bmm/workflows/3-solutioning/create-epics-and-stories/steps/step-03-create-stories.md b/src/bmm/workflows/3-solutioning/create-epics-and-stories/steps/step-03-create-stories.md index 2e13f9b2c..4f09cdcb4 100644 --- a/src/bmm/workflows/3-solutioning/create-epics-and-stories/steps/step-03-create-stories.md +++ b/src/bmm/workflows/3-solutioning/create-epics-and-stories/steps/step-03-create-stories.md @@ -112,6 +112,20 @@ So that {value_benefit}. **And** {additional_criteria} ``` +**ENTERPRISE TRACK: REQUIREMENT TRACEABILITY** + +If the project is Enterprise track (check PRD frontmatter for `track: enterprise`), each story MUST include a **Requirements Traceability** section after Acceptance Criteria: + +``` +**Requirements Traceability:** +- **PRD:** FR-AUTH-001, FR-AUTH-002 +- **SyRS:** SYS-FUNC-001 +- **StRS:** STK-BIZ-001 +- **Verification:** Test +``` + +This links each story back to its source requirements at all levels. The verification method indicates how this story's requirements will be validated (Inspection / Analysis / Demonstration / Test). + **✅ GOOD STORY EXAMPLES:** _Epic 1: User Authentication_ diff --git a/src/bmm/workflows/3-solutioning/create-epics-and-stories/steps/step-04-final-validation.md b/src/bmm/workflows/3-solutioning/create-epics-and-stories/steps/step-04-final-validation.md index 05e8d5d4e..424e28867 100644 --- a/src/bmm/workflows/3-solutioning/create-epics-and-stories/steps/step-04-final-validation.md +++ b/src/bmm/workflows/3-solutioning/create-epics-and-stories/steps/step-04-final-validation.md @@ -111,7 +111,27 @@ Review the complete epic and story breakdown to ensure EVERY FR is covered: - Foundation stories only setup what's needed - No big upfront technical work -### 5. Dependency Validation (CRITICAL) +### 5. Enterprise Track: Requirements Traceability Validation + +If the project is Enterprise track (check PRD frontmatter for `track: enterprise`): + +**Requirement ID Reference Check:** + +- [ ] Every story has a **Requirements Traceability** section +- [ ] Every story references at least one PRD FR by ID +- [ ] Every story references corresponding SyRS requirement ID (if SyRS exists) +- [ ] Every story references originating StRS requirement ID (if StRS exists) +- [ ] Every story specifies a verification method + +**RTM Forward Coverage Check:** + +- [ ] Every PRD FR is referenced by at least one story +- [ ] No stories reference non-existent requirement IDs +- [ ] FR Coverage Map is consistent with story requirement references + +If traceability gaps found, list them as Critical findings and require resolution before completion. + +### 6. Dependency Validation (CRITICAL) **Epic Independence Check:** @@ -131,7 +151,7 @@ For each epic, review stories in order: - ❌ WRONG: Story references features not yet implemented - ✅ RIGHT: Each story builds only on previous stories -### 6. Complete and Save +### 7. Complete and Save If all validations pass: diff --git a/src/bmm/workflows/3-solutioning/create-epics-and-stories/templates/epics-template.md b/src/bmm/workflows/3-solutioning/create-epics-and-stories/templates/epics-template.md index 05afe1f5f..789ee8099 100644 --- a/src/bmm/workflows/3-solutioning/create-epics-and-stories/templates/epics-template.md +++ b/src/bmm/workflows/3-solutioning/create-epics-and-stories/templates/epics-template.md @@ -1,6 +1,7 @@ --- stepsCompleted: [] inputDocuments: [] +track: "{{bmad|enterprise}}" --- # {{project_name}} - Epic Breakdown @@ -27,6 +28,10 @@ This document provides the complete epic and story breakdown for {{project_name} {{requirements_coverage_map}} + + + + ## Epic List {{epics_list}} @@ -54,4 +59,11 @@ So that {{value_benefit}}. **Then** {{expected_outcome}} **And** {{additional_criteria}} + + + + + + +