Run one iteration of a BMad unattended development loop, with optional route and review selections. The skill follows a generated workflow and reports a halt reason or command failure when execution cannot continue.
One iteration of an unattended development loop. Use when invoked by name
Review the instructions the agent will receive before you install.
Run the following command exactly once without changing the current working directory.
Replace {project-root} with the nearest folder containing _bmad/, from the working directory upward.
Replace {skill-root} with the absolute path to this skill's directory.
uv run --no-cache "{project-root}/_bmad/scripts/render_skill.py" --project-root "{project-root}" --skill "{skill-root}"
oneshot or full), append --set workflow.route=<value> to the command.none, quick, or thorough; "skip review" or "no review" mean none), append --set workflow.review=<value> to the command.HALT: <reason>: report the reason and stop.bmad skill, then run the command again. If you do not have the bmad skill, offer to install it first.uv being unavailable, report the command output and stop. Do not run any workflow source directly.No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Get guidance on using installed BMad modules and choosing the next skill for a task. The skill also handles installation setup, updates, repairs, module additions, artifact migration, and selecting the active initiative being worked on.
Revisit a recent answer, plan, draft, or decision using selected critique methods. The skill offers relevant approaches, explains what they reveal, and proposes improvements that are applied only after the user accepts them.
Work with Mary, a business analyst persona, to research markets, examine competitors, and clarify requirements. Use evidence-based discussion to turn vague needs into concrete specifications that can guide the next steps of a project.
Turn product requirements and user experience plans into technical architecture with Winston, a system architect persona. Discuss technology choices and their trade-offs, with an emphasis on established tools, developer productivity, and designs that can be implemented.
Implement approved development stories and code changes with Amelia, a senior software engineer persona. Follow a test-first process: write a failing test, make it pass, then improve the code while checking every acceptance criterion.
Work with John, a product manager persona, to clarify requirements through user interviews and stakeholder alignment. Turn a product vision into a PRD, a product requirements document, and small, validated increments for development.