Level 0 - Minimal User Story Generation

This generates a single user story for Level 0 atomic changes Level 0 = single file change, bug fix, or small isolated task This workflow runs AFTER tech-spec.md has been completed Output format MUST match create-story template for compatibility with story-context and dev-story workflows

Read the completed tech-spec.md file from {output_folder}/tech-spec.md Load bmm-workflow-status.md from {output_folder}/bmm-workflow-status.md Extract dev_story_location from config (where stories are stored) Extract the problem statement from "Technical Approach" section Extract the scope from "Source Tree Structure" section Extract time estimate from "Implementation Guide" or technical details Extract acceptance criteria from "Testing Approach" section

Derive a short URL-friendly slug from the feature/change name Max slug length: 3-5 words, kebab-case format

- "Migrate JS Library Icons" → "icon-migration" - "Fix Login Validation Bug" → "login-fix" - "Add OAuth Integration" → "oauth-integration"

Set story_filename = "story-{slug}.md" Set story_path = "{dev_story_location}/story-{slug}.md"

Create 1 story that describes the technical change as a deliverable Story MUST use create-story template format for compatibility

**Story Point Estimation:** - 1 point = < 1 day (2-4 hours) - 2 points = 1-2 days - 3 points = 2-3 days - 5 points = 3-5 days (if this high, question if truly Level 0)

Story Title Best Practices:

Use active, user-focused language
Describe WHAT is delivered, not HOW
Good: "Icon Migration to Internal CDN"
Bad: "Run curl commands to download PNGs"

Story Description Format:

As a [role] (developer, user, admin, etc.)
I want [capability/change]
So that [benefit/value]

Acceptance Criteria:

Extract from tech-spec "Testing Approach" section
Must be specific, measurable, and testable
Include performance criteria if specified

Tasks/Subtasks:

Map directly to tech-spec "Implementation Guide" tasks
Use checkboxes for tracking
Reference AC numbers: (AC: #1), (AC: #2)
Include explicit testing subtasks

Dev Notes:

Extract technical constraints from tech-spec
Include file paths from "Source Tree Structure"
Reference architecture patterns if applicable
Cite tech-spec sections for implementation details

Initialize story file using user_story_template

story_title role capability benefit acceptance_criteria tasks_subtasks technical_summary files_to_modify test_locations story_points time_estimate architecture_references

mode: update action: complete_workflow workflow_name: tech-spec ✅ Tech-spec complete! Next: {{next_workflow}}

Load {{status_file_path}} Set STORIES_SEQUENCE: [{slug}] Set TODO_STORY: {slug} Set TODO_TITLE: {{story_title}} Set IN_PROGRESS_STORY: (empty) Set STORIES_DONE: [] Save {{status_file_path}}

Story queue initialized with single story: {slug}

Display completion summary

Level 0 Planning Complete!

Generated Artifacts:

tech-spec.md → Technical source of truth
story-{slug}.md → User story ready for implementation

Story Location: {story_path}

Next Steps (choose one path):

Option A - Full Context (Recommended for complex changes):

Load SM agent: {project-root}/bmad/bmm/agents/sm.md
Run story-context workflow
Then load DEV agent and run dev-story workflow

Option B - Direct to Dev (For simple, well-understood changes):

Load DEV agent: {project-root}/bmad/bmm/agents/dev.md
Run dev-story workflow (will auto-discover story)
Begin implementation

Progress Tracking:

All decisions logged in: bmm-workflow-status.md
Next action clearly identified

Ready to proceed? Choose your path:

Generate story context (Option A - recommended)
Go directly to dev-story implementation (Option B - faster)
Exit for now

Select option (1-3):

5.5 KiB Raw Blame History

Level 0 - Minimal User Story Generation

5.5 KiB

Raw Blame History