菜单
This skill activates when the user asks about "story creation", "sprint planning", "story development cycle", "story validation", "code review workflow", "dev story", "create next story", "story template", or needs guidance on BMAD's implementation workflow patterns.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
This skill should be used when the user asks to "use the VAMFI templates", "get the proposal template", "find the PRD template", "use the HLD template", "load the runbook template", "access artifact templates", or needs a blank template for any VAMFI consultancy document.
This skill should be used when the user asks to "shape stories", "create a backlog", "break this epic into stories", "write user stories with acceptance criteria", "define the product backlog", "estimate stories", or needs to convert a PRD or delivery plan into an executable sprint backlog.
This skill should be used when the user asks to "implement this feature", "write the code for this story", "execute this implementation plan", "make this code change", "add this functionality", or needs hands-on code implementation following a VAMFI implementation plan.
This skill should be used when the user asks to "review this code", "review the PR", "check code quality", "refactor this module", "improve this code", "run a code review", or needs systematic review of recently written or changed code before it merges.
This skill should be used when the user asks to "optimise costs", "reduce cloud spend", "improve performance", "fix slow queries", "analyse FinOps", "reduce latency", "optimise infrastructure", "right-size resources", or needs to improve the efficiency of a running system.
This skill should be used when the user asks to "assess the current architecture", "document the existing system", "analyse the codebase", "identify technical debt", "review the legacy system", "produce a current-state report", or needs to understand what exists before designing a target architecture.
| name | BMAD Workflow Execution |
| description | This skill activates when the user asks about "story creation", "sprint planning", "story development cycle", "story validation", "code review workflow", "dev story", "create next story", "story template", or needs guidance on BMAD's implementation workflow patterns. |
| version | 1.0.0 |
Every BMAD story lives in docs/stories/ and follows a standard template with these sections:
Stories are numbered by epic and sequence: story-E1.S1.md, story-E1.S2.md, etc.
The implementation phase runs a repeating cycle for each story:
Bob reads the PRD and architecture docs, then:
James picks up the next Ready story, then:
Quinn picks up In Review stories, then:
If QA Fail:
Before implementation begins, bob-sm plans the sprint:
docs/prd.mdEach agent can only edit specific sections of a story file:
| Agent | Can Edit |
|---|---|
| bob-sm | Story, Acceptance Criteria, Tasks, Dev Notes, Status (to Ready) |
| james-dev | Tasks (checkboxes), Dev Agent Record, Status (to In Review) |
| quinn-qa | QA Results, Status (to QA Pass or QA Fail) |
No agent should modify sections owned by another agent except through the defined handoff (status change).
Before a story is marked Ready, bob-sm validates:
James-dev should NOT begin a story if:
When blocked, james-dev should message bob-sm via SendMessage to resolve the blocker.