bmad-dev-auto
One iteration of an unattended development loop. Use when invoked by name.
- License 许可
- MIT
- 最近更新
- 2026-10-23
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- bmad-dev-auto
- description
- One iteration of an unattended development loop. Use when invoked by name.
02 资源文件 7
- 参考文档compile-epic-context.md2.9 KB
- 其他customize.toml872 B
- 参考文档spec-template.md4.0 KB
- 参考文档step-01-clarify-and-route.md6.1 KB
- 参考文档step-02-plan.md2.1 KB
- 参考文档step-03-implement.md2.3 KB
- 参考文档step-04-review.md6.6 KB
03 SKILL.md 正文
Dev Auto Workflow
Goal: Turn intent into a hardened, reviewable artifact, without human interaction.
CRITICAL: If a step says "read fully and follow step-XX", you read and follow step-XX. No exceptions.
HALT
To HALT with a final status and optional blocking condition:
-
If
{spec_file}is known and exists, updatestatusin frontmatter and append missing result details under## Auto Run Result. -
If
{spec_file}is unknown or missing, create{implementation_artifacts}/bmad-dev-auto-result-<slug-or-timestamp>.mdwith:--- status: <final status> --- # BMad Dev Auto Result Status: <final status> Blocking condition: <blocking condition, if any> -
Run:
python3 {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --key workflow.on_complete -
If the resolved
workflow.on_completeis non-empty, follow it as the final instruction before exiting. -
Stop the workflow.
Subagents
Using subagents when instructed is mandatory. If you cannot, HALT with status blocked and blocking condition no subagents.
Invoke every subagent synchronously: launch it, wait for it to return within the same turn, then continue with its result. When a step says to run subagents "in parallel" (e.g. the reviewers), that means several blocking calls awaited together in one turn — not detached execution. Never run a subagent in the background / detached / async (e.g. run_in_background: true), and never end your turn to "await a completion notification." This workflow runs unattended: there is no event loop to resume a yielded turn, so a backgrounded subagent never hands control back and the run stalls. The only sanctioned way to end a turn is the HALT protocol above with an explicit terminal status.
READY FOR DEVELOPMENT STANDARD
A specification is "Ready for Development" when:
- Actionable: Every task has a file path and specific action.
- Logical: Tasks ordered by dependency.
- Testable: All ACs use Given/When/Then.
- Complete: No placeholders or TBDs.
- Sufficient: No known requirement, acceptance, dependency, or implementation gaps remain unresolved.
- Coherent: No unresolved ambiguities or internal contradictions.
Conventions
- Bare paths (e.g.
step-01-clarify-and-route.md) resolve from the skill root. {skill-root}resolves to this skill's installed directory (wherecustomize.tomllives).{project-root}-prefixed paths resolve from the project working directory.{skill-name}resolves to the skill directory's basename.
On Activation
Step 1: Resolve the Workflow Block
Run: python3 {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --key workflow
If the script fails, resolve the workflow block yourself by reading these three files in base → team → user order and applying the same structural merge rules as the resolver:
{skill-root}/customize.toml— defaults{project-root}/_bmad/custom/{skill-name}.toml— team overrides{project-root}/_bmad/custom/{skill-name}.user.toml— personal overrides
Any missing file is skipped. Scalars override, tables deep-merge, arrays of tables keyed by code or id replace matching entries and append new entries, and all other arrays append.
Step 2: Execute Prepend Steps
Execute each entry in {workflow.activation_steps_prepend} in order before proceeding.
Step 3: Load Persistent Facts
Treat every entry in {workflow.persistent_facts} as foundational context you carry for the rest of the workflow run. Entries prefixed file: are paths or globs under {project-root} -- load the referenced contents as facts. All other entries are facts verbatim.
Step 4: Load Config
Load config from {project-root}/_bmad/bmm/config.yaml and resolve:
project_name,planning_artifacts,implementation_artifacts,user_namecommunication_language,document_output_language,user_skill_leveldateas system-generated current datetimeproject_context=**/project-context.md(load if exists)- YOU MUST ALWAYS SPEAK OUTPUT in your Agent communication style with the config
{communication_language} - Language MUST be tailored to
{user_skill_level} - Generate all documents in
{document_output_language}
Step 5: Execute Append Steps
Execute each entry in {workflow.activation_steps_append} in order.
Activation is complete after all activation steps have run.
Workflow Execution
Follow the step files in order. Read one step fully, execute it, then load the next step only when directed. Do not skip, reorder, or pre-load steps.
First workflow step
Read fully and follow: ./step-01-clarify-and-route.md to begin the workflow.
04 同仓库更多 Skills
wds-agent-saga-analyst
Strategic business analyst and product discovery partner for WDS. Use when the user asks to talk to Saga or requests the WDS analyst.
wds-agent-mimir-builder
Implementation agent. Owns the tech audit, the PRD, and the build. Reads Freya's Work Orders and turns them into working code — one verified task at a time.
wds-agent-freya-ux
Strategic UX designer and design thinking partner for WDS. Use when the user asks to talk to Freya or requests the WDS designer.
wds-8-product-evolution
Brownfield improvements — the full WDS pipeline in miniature for existing products
wds-7-design-system
Create, import, browse, and maintain design system components and tokens
wds-6-asset-generation
Generate visual and text assets from specifications through AI-powered creative production