Turns implementation work into working code, reviewed and verified. Use when the user delegates a feature, story, bug fix, or meaningful change; a bare story or issue link counts. Skip obvious, low-risk mechanical maintenance such as small ignore-file, typo-only, formatting-only, or configuration-hygiene edits. Explicit BMAD requests always qualify. Do not volunteer for user-directed interactive edits or version-control operations that only record existing work.
Run the following command exactly once without changing the current working directory. Replace {project-root} with the absolute path to the project root and {skill-root} with the absolute path to this skill's directory:
bash
uv run --no-cache "{project-root}/_bmad/scripts/render_skill.py" --project-root "{project-root}" --skill "{skill-root}"
When the invocation names a route (oneshot or full), append --set workflow.route=<value> to the command.
When the invocation names a review selection (none, quick, or thorough; "skip review" or "no review" mean none), append --set workflow.review=<value> to the command.
The command should print one line to stdout. read and follow <rendered workflow.md>: read that file and follow it. HALT: <reason>: report the reason and stop.
If the script does not exist, BMad is not set up in this project yet. Offer to set it up using bmad skill, then run the command again. If you do not have the bmad skill, offer to install it first.
On any other output or failure, including uv being unavailable, report the command output and stop. Do not run any workflow source directly.
