dev-story
The dev-story command automates story implementation by loading a project's core workflow configuration and applying it to a specific story specification file. Use this when implementing user stories from sprint plans by invoking "dev this story [filename]" or "implement the next story in the sprint plan" to execute structured development workflows with templated outputs.
mkdir -p ~/.claude/commands && curl -fsSL https://raw.githubusercontent.com/UfoMiao/zcf/HEAD/.claude/commands/bmad-bmm-dev-story.md -o ~/.claude/commands/dev-story.mdbmad-bmm-dev-story.md
IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
<steps CRITICAL="TRUE">
1. Always LOAD the FULL {project-root}/_bmad/core/tasks/workflow.xml
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config {project-root}/_bmad/bmm/workflows/4-implementation/dev-story/workflow.yaml
3. Pass the yaml path {project-root}/_bmad/bmm/workflows/4-implementation/dev-story/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
5. Save outputs after EACH section when generating any documents from templates
</steps>TypeScript CLI architecture specialist for ZCF project
Advanced configuration management and backup system architect for ZCF project
Build, deployment, and release management specialist for ZCF project
Advanced i18next internationalization specialist for ZCF project
Template system and workflow configuration specialist for ZCF project
Comprehensive testing architecture specialist for ZCF project using Vitest
CCR, Cometix, and CCusage integration specialist for ZCF project
bmad-master agent