bmad-method 6.0.0-alpha.2 → 6.0.0-alpha.21

package/src/modules/bmm/workflows/4-implementation/dev-story/README.md

@@ -1,206 +0,0 @@
-# Dev Story Workflow
-
-The dev-story workflow is where v6's just-in-time context approach delivers its primary value, enabling the Developer (DEV) agent to implement stories with expert-level guidance injected directly into their context. This workflow is run EXCLUSIVELY by the DEV agent and operates on a single story that has been prepared by the SM through create-story and enhanced with story-context. The DEV loads both the story specification and the dynamically-generated story context XML, then proceeds through implementation with the combined knowledge of requirements and domain-specific expertise.
-
-The workflow operates with two critical inputs: the story file (created by SM's create-story) containing acceptance criteria, tasks, and requirements; and the story-context XML (generated by SM's story-context) providing just-in-time expertise injection tailored to the story's technical needs. This dual-input approach ensures the developer has both the "what" (from the story) and the "how" (from the context) needed for successful implementation. The workflow iterates through tasks sequentially, implementing code, writing tests, and updating the story document's allowed sections until all tasks are complete.
-
-A critical aspect of v6 flow is that dev-story may be run multiple times for the same story. Initially run to implement the story, it may be run again after code-review identifies issues that need correction. The workflow intelligently resumes from incomplete tasks, making it ideal for both initial implementation and post-review fixes. The DEV agent maintains strict boundaries on what can be modified in the story file—only Tasks/Subtasks checkboxes, Dev Agent Record, File List, Change Log, and Status may be updated, preserving the story's requirements integrity.
-
-## Usage
-
-```bash
-# Developer implements the story with injected context
-bmad dev *develop
-
-# Or if returning to fix review issues
-bmad dev *develop  # Will resume from incomplete tasks
-```
-
-The DEV runs this workflow:
-
-- After SM completes both create-story and story-context
-- When a story status is "Draft" or "Approved" (ready for development)
-- After code-review identifies issues requiring fixes
-- To resume work on a partially completed story
-
-## Inputs
-
-**Required Files:**
-
-- **Story Document** (`{story_dir}/story-{epic}.{story}.md`): Complete specification including:
-  - User story statement
-  - Acceptance criteria (immutable during dev)
-  - Tasks and subtasks (checkable during implementation)
-  - Dev Notes section (for context and guidance)
-  - Status field (Draft → In Progress → Ready for Review)
-
-- **Story Context XML** (`{story_dir}/story-{epic}.{story}-context.xml`): Domain expertise including:
-  - Technical patterns and best practices
-  - Gotchas and common pitfalls
-  - Testing strategies
-  - Relevant code references
-  - Architecture constraints
-
-**Configuration:**
-
-- `dev_story_location`: Directory containing story files (from bmm/config.yaml)
-- `story_selection_limit`: Number of recent stories to show (default: 10)
-- `run_tests_command`: Test command (default: auto-detected)
-- `strict`: Whether to halt on test failures (default: true)
-
-## Outputs
-
-**Code Implementation:**
-
-- Production code satisfying acceptance criteria
-- Unit, integration, and E2E tests as appropriate
-- Documentation updates
-- Migration scripts if needed
-
-**Story File Updates (allowed sections only):**
-
-- **Tasks/Subtasks**: Checkboxes marked complete as work progresses
-- **Dev Agent Record**: Debug log and completion notes
-- **File List**: All files created or modified
-- **Change Log**: Summary of implementation changes
-- **Status**: Updated to "Ready for Review" when complete
-
-**Validation:**
-
-- All tests passing (existing + new)
-- Acceptance criteria verified
-- Code quality checks passed
-- No regression in existing functionality
-
-## Key Features
-
-**Story-Context Integration**: The workflow loads and leverages the story-context XML throughout implementation, providing expert guidance without cluttering the main conversation. This ensures best practices are followed while maintaining developer autonomy.
-
-**Task-by-Task Iteration**: Implements one task at a time, marking completion before moving to the next. This granular approach enables progress tracking and clean resumption if interrupted or after review feedback.
-
-**Strict File Boundaries**: Only specific sections of the story file may be modified, preserving requirement integrity. The story's acceptance criteria, main description, and other planning sections remain immutable during development.
-
-**Test-Driven Approach**: For each task, the workflow emphasizes writing tests that verify acceptance criteria before or alongside implementation, ensuring requirements are actually met.
-
-**Resumable Implementation**: If the workflow is run again on a story with incomplete tasks (e.g., after code-review finds issues), it intelligently resumes from where it left off rather than starting over.
-
-## Integration with v6 Flow
-
-The dev-story workflow is step 3 in the v6 implementation cycle:
-
-1. SM: create-story (generates the story specification)
-2. SM: story-context (adds JIT technical expertise)
-3. **DEV: dev-story** ← You are here (initial implementation)
-4. DEV/SR: code-review (validates completion)
-5. If issues found: **DEV: dev-story** ← May return here for fixes
-6. After epic: retrospective (captures learnings)
-
-This workflow may be executed multiple times for the same story as part of the review-fix cycle. Each execution picks up from incomplete tasks, making it efficient for iterative improvement.
-
-## Workflow Process
-
-### Phase 1: Story Selection
-
-- If `story_path` provided: Use that story directly
-- Otherwise: List recent stories from `dev_story_location`
-- Parse story structure and validate format
-- Load corresponding story-context XML
-
-### Phase 2: Task Implementation Loop
-
-For each incomplete task:
-
-1. **Plan**: Log approach in Dev Agent Record
-2. **Implement**: Write code following story-context guidance
-3. **Test**: Create tests verifying acceptance criteria
-4. **Validate**: Run tests and quality checks
-5. **Update**: Mark task complete, update File List
-
-### Phase 3: Completion
-
-- Verify all tasks completed
-- Run full test suite
-- Update Status to "Ready for Review"
-- Add completion notes to Dev Agent Record
-
-## Story File Structure
-
-The workflow expects stories with this structure:
-
-```markdown
-# Story {epic}.{story}: {Title}
-
-**Status**: Draft|In Progress|Ready for Review|Done
-**Epic**: {epic_number}
-**Estimated Effort**: {estimate}
-
-## Story
-
-As a {role}, I want to {action} so that {benefit}
-
-## Acceptance Criteria
-
-- [ ] AC1...
-- [ ] AC2...
-
-## Tasks and Subtasks
-
-- [ ] Task 1
-  - [ ] Subtask 1.1
-- [ ] Task 2
-
-## Dev Notes
-
-{Context and guidance from story creation}
-
-## Dev Agent Record
-
-### Debug Log
-
-{Implementation notes added during development}
-
-### Completion Notes
-
-{Summary added when complete}
-
-## File List
-
-{Files created/modified}
-
-## Change Log
-
-{Implementation summary}
-```
-
-## Best Practices
-
-**Load Context First**: Always ensure the story-context XML is loaded at the start. This provides the expert guidance needed throughout implementation.
-
-**Follow Task Order**: Implement tasks in the order listed. Dependencies are typically structured in the task sequence.
-
-**Test Each Task**: Don't wait until the end to write tests. Test each task as you complete it to ensure it meets acceptance criteria.
-
-**Update Incrementally**: Update the story file after each task completion rather than batching updates at the end.
-
-**Respect Boundaries**: Never modify acceptance criteria or story description. If they seem wrong, that's a code-review or correct-course issue, not a dev-story fix.
-
-**Use Context Guidance**: Actively reference the story-context for patterns, gotchas, and best practices. It's there to help you succeed.
-
-## Troubleshooting
-
-**Story Not Found**: Ensure story exists in `dev_story_location` and follows naming pattern `story-{epic}.{story}.md`
-
-**Context XML Missing**: The story-context workflow must be run first. Check for `story-{epic}.{story}-context.xml`
-
-**Tests Failing**: If strict mode is on, the workflow halts. Fix tests before continuing or set strict=false for development iteration.
-
-**Can't Modify Story Section**: Remember only Tasks, Dev Agent Record, File List, Change Log, and Status can be modified. Other sections are immutable.
-
-**Resuming After Review**: If code-review found issues, the workflow automatically picks up from incomplete tasks when run again.
-
-## Related Workflows
-
-- **create-story**: Creates the story specification (run by SM)
-- **story-context**: Generates the context XML (run by SM)
-- **code-review**: Validates implementation (run by SR/DEV)
-- **correct-course**: Handles major issues or scope changes (run by SM)

package/src/modules/bmm/workflows/4-implementation/dev-story/instructions.md

@@ -1,262 +0,0 @@
-# Develop Story - Workflow Instructions
-
-```xml
-<critical>The workflow execution engine is governed by: {project-root}/bmad/core/tasks/workflow.xml</critical>
-<critical>You MUST have already loaded and processed: {installed_path}/workflow.yaml</critical>
-<critical>Communicate all responses in {communication_language} and language MUST be tailored to {user_skill_level}</critical>
-<critical>Generate all documents in {document_output_language}</critical>
-<critical>Only modify the story file in these areas: Tasks/Subtasks checkboxes, Dev Agent Record (Debug Log, Completion Notes), File List, Change Log, and Status</critical>
-<critical>Execute ALL steps in exact order; do NOT skip steps</critical>
-<critical>Absolutely DO NOT stop because of "milestones", "significant progress", or "session boundaries". Continue in a single execution until the story is COMPLETE (all ACs satisfied and all tasks/subtasks checked) UNLESS a HALT condition is triggered or the USER gives other instruction.</critical>
-<critical>Do NOT schedule a "next session" or request review pauses unless a HALT condition applies. Only Step 6 decides completion.</critical>
-
-<critical>User skill level ({user_skill_level}) affects conversation style ONLY, not code updates.</critical>
-
-<workflow>
-
-  <step n="1" goal="Find next ready story and load it" tag="sprint-status">
-    <check if="{{story_path}} is provided">
-      <action>Use {{story_path}} directly</action>
-      <action>Read COMPLETE story file</action>
-      <action>Extract story_key from filename or metadata</action>
-      <goto>task_check</goto>
-    </check>
-
-    <critical>MUST read COMPLETE sprint-status.yaml file from start to end to preserve order</critical>
-    <action>Load the FULL file: {{output_folder}}/sprint-status.yaml</action>
-    <action>Read ALL lines from beginning to end - do not skip any content</action>
-    <action>Parse the development_status section completely to understand story order</action>
-
-    <action>Find the FIRST story (by reading in order from top to bottom) where:
-      - Key matches pattern: number-number-name (e.g., "1-2-user-auth")
-      - NOT an epic key (epic-X) or retrospective (epic-X-retrospective)
-      - Status value equals "ready-for-dev"
-    </action>
-
-    <check if="no ready-for-dev or in-progress story found">
-      <output>📋 No ready-for-dev stories found in sprint-status.yaml
-**Options:**
-1. Run `story-context` to generate context file and mark drafted stories as ready
-2. Run `story-ready` to quickly mark drafted stories as ready without generating context
-3. Run `create-story` if no incomplete stories are drafted yet
-4. Check {output-folder}/sprint-status.yaml to see current sprint status
-      </output>
-      <action>HALT</action>
-    </check>
-
-    <action>Store the found story_key (e.g., "1-2-user-authentication") for later status updates</action>
-    <action>Find matching story file in {{story_dir}} using story_key pattern: {{story_key}}.md</action>
-    <action>Read COMPLETE story file from discovered path</action>
-
-    <anchor id="task_check" />
-
-    <action>Parse sections: Story, Acceptance Criteria, Tasks/Subtasks, Dev Notes, Dev Agent Record, File List, Change Log, Status</action>
-
-    <action>Check if context file exists at: {{story_dir}}/{{story_key}}.context.xml</action>
-    <check if="context file exists">
-      <action>Read COMPLETE context file</action>
-      <action>Parse all sections: story details, artifacts (docs, code, dependencies), interfaces, constraints, tests</action>
-      <action>Use this context to inform implementation decisions and approaches</action>
-    </check>
-    <check if="context file does NOT exist">
-      <output>ℹ️ No context file found for {{story_key}}
-
-Proceeding with story file only. For better context, consider running `story-context` workflow first.
-      </output>
-    </check>
-
-    <action>Identify first incomplete task (unchecked [ ]) in Tasks/Subtasks</action>
-
-    <action if="no incomplete tasks"><goto step="6">Completion sequence</goto></action>
-    <action if="story file inaccessible">HALT: "Cannot develop story without access to story file"</action>
-    <action if="incomplete task or subtask requirements ambiguous">ASK user to clarify or HALT</action>
-  </step>
-
-  <step n="1.5" goal="Detect review continuation and extract review context">
-    <critical>Determine if this is a fresh start or continuation after code review</critical>
-
-    <action>Check if "Senior Developer Review (AI)" section exists in the story file</action>
-    <action>Check if "Review Follow-ups (AI)" subsection exists under Tasks/Subtasks</action>
-
-    <check if="Senior Developer Review section exists">
-      <action>Set review_continuation = true</action>
-      <action>Extract from "Senior Developer Review (AI)" section:
-        - Review outcome (Approve/Changes Requested/Blocked)
-        - Review date
-        - Total action items with checkboxes (count checked vs unchecked)
-        - Severity breakdown (High/Med/Low counts)
-      </action>
-      <action>Count unchecked [ ] review follow-up tasks in "Review Follow-ups (AI)" subsection</action>
-      <action>Store list of unchecked review items as {{pending_review_items}}</action>
-
-      <output>⏯️ **Resuming Story After Code Review** ({{review_date}})
-
-**Review Outcome:** {{review_outcome}}
-**Action Items:** {{unchecked_review_count}} remaining to address
-**Priorities:** {{high_count}} High, {{med_count}} Medium, {{low_count}} Low
-
-**Strategy:** Will prioritize review follow-up tasks (marked [AI-Review]) before continuing with regular tasks.
-      </output>
-    </check>
-
-    <check if="Senior Developer Review section does NOT exist">
-      <action>Set review_continuation = false</action>
-      <action>Set {{pending_review_items}} = empty</action>
-
-      <output>🚀 **Starting Fresh Implementation**
-
-Story: {{story_key}}
-Context file: {{context_available}}
-First incomplete task: {{first_task_description}}
-      </output>
-    </check>
-  </step>
-
-  <step n="1.6" goal="Mark story in-progress" tag="sprint-status">
-    <action>Load the FULL file: {{output_folder}}/sprint-status.yaml</action>
-    <action>Read all development_status entries to find {{story_key}}</action>
-    <action>Get current status value for development_status[{{story_key}}]</action>
-
-    <check if="current status == 'ready-for-dev'">
-      <action>Update the story in the sprint status report to = "in-progress"</action>
-      <output>🚀 Starting work on story {{story_key}}
-Status updated: ready-for-dev → in-progress
-      </output>
-    </check>
-
-    <check if="current status == 'in-progress'">
-      <output>⏯️ Resuming work on story {{story_key}}
-Story is already marked in-progress
-      </output>
-    </check>
-
-    <check if="current status is neither ready-for-dev nor in-progress">
-      <output>⚠️ Unexpected story status: {{current_status}}
-Expected ready-for-dev or in-progress. Continuing anyway...
-      </output>
-    </check>
-  </step>
-
-  <step n="2" goal="Plan and implement task">
-    <action>Review acceptance criteria and dev notes for the selected task</action>
-    <action>Plan implementation steps and edge cases; write down a brief plan in Dev Agent Record → Debug Log</action>
-    <action>Implement the task COMPLETELY including all subtasks, critically following best practices, coding patterns and coding standards in this repo you have learned about from the story and context file or your own critical agent instructions</action>
-    <action>Handle error conditions and edge cases appropriately</action>
-    <action if="new or different than what is documented dependencies are needed">ASK user for approval before adding</action>
-    <action if="3 consecutive implementation failures occur">HALT and request guidance</action>
-    <action if="required configuration is missing">HALT: "Cannot proceed without necessary configuration files"</action>
-    <critical>Do not stop after partial progress; continue iterating tasks until all ACs are satisfied and tested or a HALT condition triggers</critical>
-    <critical>Do NOT propose to pause for review, stand-ups, or validation until Step 6 gates are satisfied</critical>
-  </step>
-
-  <step n="3" goal="Author comprehensive tests">
-    <action>Create unit tests for business logic and core functionality introduced/changed by the task</action>
-    <action>Add integration tests for component interactions where desired by test plan or story notes</action>
-    <action>Include end-to-end tests for critical user flows where desired by test plan or story notes</action>
-    <action>Cover edge cases and error handling scenarios noted in the test plan or story notes</action>
-  </step>
-
-  <step n="4" goal="Run validations and tests">
-    <action>Determine how to run tests for this repo (infer or use {{run_tests_command}} if provided)</action>
-    <action>Run all existing tests to ensure no regressions</action>
-    <action>Run the new tests to verify implementation correctness</action>
-    <action>Run linting and code quality checks if configured</action>
-    <action>Validate implementation meets ALL story acceptance criteria; if ACs include quantitative thresholds (e.g., test pass rate), ensure they are met before marking complete</action>
-    <action if="regression tests fail">STOP and fix before continuing, consider how current changes made broke regression</action>
-    <action if="new tests fail">STOP and fix before continuing</action>
-  </step>
-
-  <step n="5" goal="Mark task complete, track review resolutions, and update story">
-    <critical>If task is a review follow-up, must mark BOTH the task checkbox AND the corresponding action item in the review section</critical>
-
-    <action>Check if completed task has [AI-Review] prefix (indicates review follow-up task)</action>
-
-    <check if="task is review follow-up">
-      <action>Extract review item details (severity, description, related AC/file)</action>
-      <action>Add to resolution tracking list: {{resolved_review_items}}</action>
-
-      <!-- Mark task in Review Follow-ups section -->
-      <action>Mark task checkbox [x] in "Tasks/Subtasks → Review Follow-ups (AI)" section</action>
-
-      <!-- CRITICAL: Also mark corresponding action item in review section -->
-      <action>Find matching action item in "Senior Developer Review (AI) → Action Items" section by matching description</action>
-      <action>Mark that action item checkbox [x] as resolved</action>
-
-      <action>Add to Dev Agent Record → Completion Notes: "✅ Resolved review finding [{{severity}}]: {{description}}"</action>
-    </check>
-
-    <action>ONLY mark the task (and subtasks) checkbox with [x] if ALL tests pass and validation succeeds</action>
-    <action>Update File List section with any new, modified, or deleted files (paths relative to repo root)</action>
-    <action>Add completion notes to Dev Agent Record if significant changes were made (summarize intent, approach, and any follow-ups)</action>
-
-    <check if="review_continuation == true and {{resolved_review_items}} is not empty">
-      <action>Count total resolved review items in this session</action>
-      <action>Add Change Log entry: "Addressed code review findings - {{resolved_count}} items resolved (Date: {{date}})"</action>
-    </check>
-
-    <action>Save the story file</action>
-    <action>Determine if more incomplete tasks remain</action>
-    <action if="more tasks remain"><goto step="2">Next task</goto></action>
-    <action if="no tasks remain"><goto step="6">Completion</goto></action>
-  </step>
-
-  <step n="6" goal="Story completion and mark for review" tag="sprint-status">
-    <action>Verify ALL tasks and subtasks are marked [x] (re-scan the story document now)</action>
-    <action>Run the full regression suite (do not skip)</action>
-    <action>Confirm File List includes every changed file</action>
-    <action>Execute story definition-of-done checklist, if the story includes one</action>
-    <action>Update the story Status to: review</action>
-
-    <!-- Mark story ready for review -->
-    <action>Load the FULL file: {{output_folder}}/sprint-status.yaml</action>
-    <action>Find development_status key matching {{story_key}}</action>
-    <action>Verify current status is "in-progress" (expected previous state)</action>
-    <action>Update development_status[{{story_key}}] = "review"</action>
-    <action>Save file, preserving ALL comments and structure including STATUS DEFINITIONS</action>
-
-    <check if="story key not found in file">
-      <output>⚠️ Story file updated, but sprint-status update failed: {{story_key}} not found
-
-Story is marked Ready for Review in file, but sprint-status.yaml may be out of sync.
-      </output>
-    </check>
-
-    <action if="any task is incomplete">Return to step 1 to complete remaining work (Do NOT finish with partial progress)</action>
-    <action if="regression failures exist">STOP and resolve before completing</action>
-    <action if="File List is incomplete">Update it before completing</action>
-  </step>
-
-  <step n="7" goal="Completion communication and user support">
-    <action>Optionally run the workflow validation task against the story using {project-root}/bmad/core/tasks/validate-workflow.xml</action>
-    <action>Prepare a concise summary in Dev Agent Record → Completion Notes</action>
-
-    <action>Communicate to {user_name} that story implementation is complete and ready for review</action>
-    <action>Summarize key accomplishments: story ID, story key, title, key changes made, tests added, files modified</action>
-    <action>Provide the story file path and current status (now "review", was "in-progress")</action>
-
-    <action>Based on {user_skill_level}, ask if user needs any explanations about:
-      - What was implemented and how it works
-      - Why certain technical decisions were made
-      - How to test or verify the changes
-      - Any patterns, libraries, or approaches used
-      - Anything else they'd like clarified
-    </action>
-
-    <check if="user asks for explanations">
-      <action>Provide clear, contextual explanations tailored to {user_skill_level}</action>
-      <action>Use examples and references to specific code when helpful</action>
-    </check>
-
-    <action>Once explanations are complete (or user indicates no questions), suggest logical next steps</action>
-    <action>Common next steps to suggest (but allow user flexibility):
-      - Review the implemented story yourself and test the changes
-      - Verify all acceptance criteria are met
-      - Ensure deployment readiness if applicable
-      - Run `code-review` workflow for peer review
-      - Check sprint-status.yaml to see project progress
-    </action>
-    <action>Remain flexible - allow user to choose their own path or ask for other assistance</action>
-  </step>
-
-</workflow>
-```

package/src/modules/bmm/workflows/4-implementation/epic-tech-context/README.md

@@ -1,195 +0,0 @@
-# Technical Specification Workflow
-
-## Overview
-
-Generate a comprehensive Technical Specification for a single epic from PRD, Epics file and Architecture to produce a document with full acceptance criteria and traceability mapping. Creates detailed implementation guidance that bridges business requirements with technical execution.
-
-## Key Features
-
-- **PRD-Architecture Integration** - Synthesizes business requirements with technical constraints
-- **Traceability Mapping** - Links acceptance criteria to technical components and tests
-- **Multi-Input Support** - Leverages PRD, architecture, front-end specs, and brownfield notes
-- **Implementation Focus** - Provides concrete technical guidance for development teams
-- **Testing Integration** - Includes test strategy aligned with acceptance criteria
-- **Validation Ready** - Generates specifications suitable for architectural review
-
-## Usage
-
-### Basic Invocation
-
-```bash
-workflow tech-spec
-```
-
-### With Input Documents
-
-```bash
-# With specific PRD and architecture
-workflow tech-spec --input PRD.md --input architecture.md
-
-# With comprehensive inputs
-workflow tech-spec --input PRD.md --input architecture.md --input front-end-spec.md
-```
-
-### Configuration
-
-- **output_folder**: Location for generated technical specification
-- **epic_id**: Used in output filename (extracted from PRD or prompted)
-- **recommended_inputs**: PRD, architecture, front-end spec, brownfield notes
-
-## Workflow Structure
-
-### Files Included
-
-```
-tech-spec/
-├── workflow.yaml           # Configuration and metadata
-├── instructions.md         # Step-by-step execution guide
-├── template.md            # Technical specification structure
-├── checklist.md           # Validation criteria
-└── README.md              # This file
-```
-
-## Workflow Process
-
-### Phase 1: Input Collection and Analysis (Steps 1-2)
-
-- **Document Discovery**: Locates PRD and Architecture documents
-- **Epic Extraction**: Identifies epic title and ID from PRD content
-- **Template Initialization**: Creates tech-spec document from template
-- **Context Analysis**: Reviews complete PRD and architecture for alignment
-
-### Phase 2: Technical Design Specification (Step 3)
-
-- **Service Architecture**: Defines services/modules with responsibilities and interfaces
-- **Data Modeling**: Specifies entities, schemas, and relationships
-- **API Design**: Documents endpoints, request/response models, and error handling
-- **Workflow Definition**: Details sequence flows and data processing patterns
-
-### Phase 3: Non-Functional Requirements (Step 4)
-
-- **Performance Specs**: Defines measurable latency, throughput, and scalability targets
-- **Security Requirements**: Specifies authentication, authorization, and data protection
-- **Reliability Standards**: Documents availability, recovery, and degradation behavior
-- **Observability Framework**: Defines logging, metrics, and tracing requirements
-
-### Phase 4: Dependencies and Integration (Step 5)
-
-- **Dependency Analysis**: Scans repository for package manifests and frameworks
-- **Integration Mapping**: Identifies external systems and API dependencies
-- **Version Management**: Documents version constraints and compatibility requirements
-- **Infrastructure Needs**: Specifies deployment and runtime dependencies
-
-### Phase 5: Acceptance and Testing (Step 6)
-
-- **Criteria Normalization**: Extracts and refines acceptance criteria from PRD
-- **Traceability Matrix**: Maps acceptance criteria to technical components
-- **Test Strategy**: Defines testing approach for each acceptance criterion
-- **Component Mapping**: Links requirements to specific APIs and modules
-
-### Phase 6: Risk and Validation (Steps 7-8)
-
-- **Risk Assessment**: Identifies technical risks, assumptions, and open questions
-- **Mitigation Planning**: Provides strategies for addressing identified risks
-- **Quality Validation**: Ensures specification meets completeness criteria
-- **Checklist Verification**: Validates against workflow quality standards
-
-## Output
-
-### Generated Files
-
-- **Primary output**: tech-spec-{epic_id}-{date}.md
-- **Traceability data**: Embedded mapping tables linking requirements to implementation
-
-### Output Structure
-
-1. **Overview and Scope** - Project context and boundaries
-2. **System Architecture Alignment** - Connection to architecture
-3. **Detailed Design** - Services, data models, APIs, and workflows
-4. **Non-Functional Requirements** - Performance, security, reliability, observability
-5. **Dependencies and Integrations** - External systems and technical dependencies
-6. **Acceptance Criteria** - Testable requirements from PRD
-7. **Traceability Mapping** - Requirements-to-implementation mapping
-8. **Test Strategy** - Testing approach and framework alignment
-9. **Risks and Assumptions** - Technical risks and mitigation strategies
-
-## Requirements
-
-- **PRD Document**: Product Requirements Document with clear acceptance criteria
-- **Architecture Document**: architecture or technical design
-- **Repository Access**: For dependency analysis and framework detection
-- **Epic Context**: Clear epic identification and scope definition
-
-## Best Practices
-
-### Before Starting
-
-1. **Validate Inputs**: Ensure PRD and architecture documents are complete and current
-2. **Review Requirements**: Confirm acceptance criteria are specific and testable
-3. **Check Dependencies**: Verify repository structure supports automated dependency analysis
-
-### During Execution
-
-1. **Maintain Traceability**: Ensure every acceptance criterion maps to implementation
-2. **Be Implementation-Specific**: Provide concrete technical guidance, not high-level concepts
-3. **Consider Constraints**: Factor in existing system limitations and brownfield challenges
-
-### After Completion
-
-1. **Architect Review**: Have technical lead validate design decisions
-2. **Developer Walkthrough**: Ensure implementation team understands specifications
-3. **Test Planning**: Use traceability matrix for test case development
-
-## Troubleshooting
-
-### Common Issues
-
-**Issue**: Missing or incomplete technical details
-
-- **Solution**: Review architecture document for implementation specifics
-- **Check**: Ensure PRD contains sufficient functional requirements detail
-
-**Issue**: Acceptance criteria don't map cleanly to technical components
-
-- **Solution**: Break down complex criteria into atomic, testable statements
-- **Check**: Verify PRD acceptance criteria are properly structured
-
-**Issue**: Dependency analysis fails or is incomplete
-
-- **Solution**: Check repository structure and manifest file locations
-- **Check**: Verify repository contains standard dependency files (package.json, etc.)
-
-**Issue**: Non-functional requirements are too vague
-
-- **Solution**: Extract specific performance and quality targets from architecture
-- **Check**: Ensure architecture document contains measurable NFR specifications
-
-## Customization
-
-To customize this workflow:
-
-1. **Modify Template**: Update template.md to match organizational technical spec standards
-2. **Extend Dependencies**: Add support for additional package managers or frameworks
-3. **Enhance Validation**: Extend checklist.md with company-specific technical criteria
-4. **Add Sections**: Include additional technical concerns like DevOps or monitoring
-
-## Version History
-
-- **v6.0.0** - Comprehensive technical specification with traceability
-  - PRD-Architecture integration
-  - Automated dependency detection
-  - Traceability mapping
-  - Test strategy alignment
-
-## Support
-
-For issues or questions:
-
-- Review the workflow creation guide at `/bmad/bmb/workflows/create-workflow/workflow-creation-guide.md`
-- Validate output using `checklist.md`
-- Ensure PRD and architecture documents are complete before starting
-- Consult BMAD documentation for technical specification standards
-
----
-
-_Part of the BMad Method v6 - BMM (Method) Module_