BMAD-METHOD/bmad/bmm/workflows/2-plan/tech-spec/instructions-sm.md

PRD Workflow - Small Projects (Level 0)

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 projects - tech-spec only Project analysis already completed - proceeding directly to technical specification NO PRD generated - uses tech_spec_template only

Load project-workflow-analysis.md Confirm Level 0 - Single atomic change

Please describe the specific change/fix you need to implement:

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

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

DEFINITIVE DECISIONS REQUIRED:

BAD Examples (NEVER DO THIS):

• "Python 2 or 3" ❌
• "Use a logger like pino or winston" ❌

GOOD Examples (ALWAYS DO THIS):

• "Python 3.11" ✅
• "winston v3.8.2 for logging" ✅

Source Tree Structure: EXACT file changes needed source_tree

Technical Approach: SPECIFIC implementation for the change technical_approach

Implementation Stack: DEFINITIVE tools and versions implementation_stack

Technical Details: PRECISE change details technical_details

Testing Approach: How to verify the change testing_approach

Deployment Strategy: How to deploy the change deployment_strategy

Offer to run cohesion validation

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

Cohesion Validation checks:

• Tech spec completeness and definitiveness
• Feature sequencing and dependencies
• External dependencies properly planned
• User/agent responsibilities clear
• Greenfield/brownfield-specific considerations

Run cohesion validation? (y/n)

If yes: 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

Confirm tech-spec is complete and definitive No PRD needed for Level 0 Ready for implementation

Summary

• Level 0 Output: tech-spec.md only
• No PRD required
• Direct to implementation

Next Steps Checklist

Determine appropriate next steps for Level 0 atomic change

If change involves UI components:

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

• Generate implementation task

  • Command: workflow task-generation
  • Uses: tech-spec.md

If change is backend/API only:

Recommended Next Steps:

• Create test plan for the change

  • Unit tests for the specific change
  • Integration test if affects other components

• Generate implementation task

  • Command: workflow task-generation
  • Uses: tech-spec.md

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):