Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →aj-geddes/bmad-builder
Meta-skill for scaffolding and validating custom PLANNING/ORCHESTRATION skills within the BMAD Planning & Orchestrator plugin. Produces the full skill directory: SKILL.md, scripts, and templates — all pre-targeted at this plugin's path conventions. Includes a scope-violation checker so newly created skills never drift into dev/lint/build/coverage territory.
Passed 17 of 20 test cases with the skill, and 3 of 20 without it.
and 21 more in the full report
16 fixed3 passed either way3 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 16 test cases the skill fixed. Same model, same prompt, with and without the skill.
When writing shell commands and referencing templates inside SKILL.md files, what environment variable prefix must be used instead of hardcoding absolute home paths like ~/.claude?
| Checked | Without skill | With skill |
|---|---|---|
| ${CLAUDE_PLUGIN_ROOT} | Missed | Passed |
The instructions your model reads when the skill loads.
Function: Scaffold and validate custom planning/orchestration skills for the BMAD Planning & Orchestrator plugin. Produces compliant SKILL.md files, shell scripts, and templates — pre-wired to this plugin's path conventions — and runs scope-violation checks to keep new skills inside the PLAN/ORCHESTRATE boundary.
This skill produces planning artifacts and skill skeleton files. It does NOT write application code, run tests, lint, check coverage, or execute builds. If a skill being designed is tempted to "implement", "fix the code", "run the suite", or "review the diff" — that is a scope violation. Plan and hand off instead.
Always clarify which intent applies before starting.
Gather requirements (use TodoWrite to track):
bmad-; e.g. bmad-example)bmad-risk-assessment)Run the scaffold script to create the directory:
bash ${CLAUDE_PLUGIN_ROOT}/skills/bmad-builder/scripts/scaffold-skill.sh <skill-name>
This creates skills/<skill-name>/ with scripts/ and templates/ subdirectories and a starter SKILL.md.
Fill the SKILL.md using the skill template:
${CLAUDE_PLUGIN_ROOT}/skills/bmad-builder/templates/skill.template.mdREFERENCE.md in the new skill's own folder${CLAUDE_PLUGIN_ROOT} for all paths to bundled scripts/templatesbmad-output/ (honor user-configured folder)Validate the new skill:
bash ${CLAUDE_PLUGIN_ROOT}/skills/bmad-builder/scripts/validate-skill.sh \
${CLAUDE_PLUGIN_ROOT}/skills/<skill-name>/SKILL.md
test cases passed, vs 3 / 20 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.