PRD Workflow - Small Projects (Level 0-1)

The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.xml You MUST have already loaded and processed: {installed_path}/workflow.yaml This is the SMALL instruction set for Level 0-1 projects - tech-spec with story generation Level 0: tech-spec + single user story | Level 1: tech-spec + epic/stories Project analysis already completed - proceeding directly to technical specification NO PRD generated - uses tech_spec_template + story templates

Load bmm-workflow-status.md from {output_folder}/bmm-workflow-status.md

Update Workflow Status Tracker: Set current_workflow = “tech-spec (Level 0 - generating tech spec)” Set current_workflow = “tech-spec (Level 1 - generating tech spec)” Set progress_percentage = 20% Save bmm-workflow-status.md

Confirm Level 0 - Single atomic change Please describe the specific change/fix you need to implement:

Confirm Level 1 - Coherent feature Please describe the feature you need to implement:

Generate tech-spec.md - this is the TECHNICAL SOURCE OF TRUTH ALL TECHNICAL DECISIONS MUST BE DEFINITIVE - NO AMBIGUITY ALLOWED

Update progress in bmm-workflow-status.md: Set progress_percentage = 40% Save bmm-workflow-status.md

Initialize tech-spec.md using tech_spec_template from workflow.yaml

DEFINITIVE DECISIONS REQUIRED:

BAD Examples (NEVER DO THIS):

GOOD Examples (ALWAYS DO THIS):

Source Tree Structure: EXACT file changes needed <template-output file=“tech-spec.md”>source_tree</template-output>

Technical Approach: SPECIFIC implementation for the change <template-output file=“tech-spec.md”>technical_approach</template-output>

Implementation Stack: DEFINITIVE tools and versions <template-output file=“tech-spec.md”>implementation_stack</template-output>

Technical Details: PRECISE change details <template-output file=“tech-spec.md”>technical_details</template-output>

Testing Approach: How to verify the change <template-output file=“tech-spec.md”>testing_approach</template-output>

Deployment Strategy: How to deploy the change <template-output file=“tech-spec.md”>deployment_strategy</template-output>

<invoke-task halt=“true”>{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>

Offer to run cohesion validation

Tech-spec complete! Before proceeding to implementation, would you like to validate project cohesion?

Cohesion Validation checks:

Run cohesion validation? (y/n)

Load {installed_path}/checklist.md Review tech-spec.md against “Cohesion Validation (All Levels)” section Focus on Section A (Tech Spec), Section D (Feature Sequencing) Apply Section B (Greenfield) or Section C (Brownfield) based on field_type Generate validation report with findings

Load bmm-workflow-status.md to determine project_level

Invoke instructions-level0-story.md to generate single user story Story will be saved to user-story.md Story links to tech-spec.md for technical implementation details

Invoke instructions-level1-stories.md to generate epic and stories Epic and stories will be saved to epic-stories.md Stories link to tech-spec.md implementation tasks

Confirm tech-spec is complete and definitive

Confirm user-story.md generated successfully

Confirm epic-stories.md generated successfully

Summary

- Level 0 Output: tech-spec.md + user-story.md - No PRD required - Direct to implementation with story tracking

- Level 1 Output: tech-spec.md + epic-stories.md - No PRD required - Ready for sprint planning with epic/story breakdown

Next Steps Checklist

Determine appropriate next steps for Level 0 atomic change

Optional Next Steps:

- [ ] Create simple UX documentation (if UI change is user-facing) - Note: Full instructions-ux workflow may be overkill for Level 0 - Consider documenting just the specific UI change

Recommended Next Steps:

Level 0 planning complete! Next action:

  1. Proceed to implementation
  2. Generate development task
  3. Create test plan
  4. Exit workflow

Select option (1-4):