bmad-builder

Name: bmad-builder
Author: aj-geddes

467stars73forks

How to install bmad-builder?

aj-geddes/claude-code-bmad-skills/bmad-builder

$npx -y skills add aj-geddes/claude-code-bmad-skills --skill bmad-builder

Installs into the current project.

Summary

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 chec

Files · 1

View on GitHub

SKILL.md

1	# BMAD Builder
2
3	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.
4
5	## Scope (PLAN, never build)
6
7	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.
8
9	## Three intents
10
11	Always clarify which intent applies before starting.
12
13	### Create — new planning skill from scratch
14
15	1. Gather requirements (use TodoWrite to track):
16	- Skill name (lowercase-hyphen, prefixed `bmad-`; e.g. `bmad-example`)
17	- What planning/orchestration problem it solves
18	- Trigger phrases users will say
19	- Allowed tools (subset of: Read, Write, Edit, Bash, Glob, Grep, WebSearch, WebFetch, TodoWrite)
20	- Which BMAD track(s) it applies to (Quick Flow / BMad Method / Enterprise)
21	- Upstream BMAD counterpart (e.g. `bmad-risk-assessment`)
22
23	2. Run the scaffold script to create the directory:
24	```bash
25	bash ${CLAUDE_PLUGIN_ROOT}/skills/bmad-builder/scripts/scaffold-skill.sh <skill-name>
26	```
27	This creates `skills/<skill-name>/` with `scripts/` and `templates/` subdirectories and a starter SKILL.md.
28
29	3. Fill the SKILL.md using the skill template:
30	- Reference: `${CLAUDE_PLUGIN_ROOT}/skills/bmad-builder/templates/skill.template.md`
31	- Keep body under 5K tokens; push long reference detail to a sibling `REFERENCE.md` in the new skill's own folder
32	- Use `${CLAUDE_PLUGIN_ROOT}` for all paths to bundled scripts/templates
33	- Artifacts go to `bmad-output/` (honor user-configured folder)
34	- End with the mandatory attribution footer (see template)
35
36	4. Validate the new skill:
37	```bash
38	bash ${CLAUDE_PLUGIN_ROOT}/skills/bmad-builder/scripts/validate-skill.sh \
39	${CLAUDE_PLUGIN_ROOT}/skills/<skill-name>/SKILL.md
40	```
41	Fix all errors; review all warnings before declaring done.
42
43	### Validate — check an existing SKILL.md
44
45	Run the validator directly against any SKILL.md path:
46	```bash
47	bash ${CLAUDE_PLUGIN_ROOT}/skills/bmad-builder/scripts/validate-skill.sh <path-to-SKILL.md>
48	```
49
50	The validator checks:
51	- `name` field present and lowercase-hyphen
52	- `description` field present with trigger phrases
53	- `allowed-tools` field present (warns if missing)
54	- No dev/lint/build/coverage scope violations in `allowed-tools` or body
55	- File size within the ~5K token target (~20KB)
56	- Attribution footer present
57
58	### Scaffold — directory structure only
59
60	Use when you want an empty directory skeleton without generating content:
61	```bash
62	bash ${CLAUDE_PLUGIN_ROOT}/skills/bmad-builder/scripts/scaffold-skill.sh <skill-name>
63	```
64	Then fill SKILL.md manually using the template as a guide.
65
66	## Scope law for new skills
67
68	Every skill created by this builder MUST comply with the Scope Law:
69
70	- The plugin PLANS and ORCHESTRATES. It NEVER writes application code, runs tests, lints, checks coverage, builds, or reviews implemented code.
71	- The last artifact any skill may produce is a ready-for-dev story file or a handoff manifest. Implementation is handed to EXTERNAL dev tools/plugins.
72	- Acceptance Criteria, Testing STRATEGY, and Dev Notes are planning — allowed. Executing tests or writing implementation code is out of scope.
73
74	The `validate-skill.sh` script enforces this automatically by flagging forbidden terms.
75
76	## BMAD fidelity reminders
77
78	When designing skills, track the BMAD Method conventions:
79
80	\| Convention \| Rule \|
81	\|------------\|------\|
82	\| Scale Tracks \| Quick Flow / BMad Method / Enterprise — user confirms interactively \|
83	\| Story size \| ~2-8h, one dev-day max; split if larger \|
84	\| Delivery tracking \| Stories remaining / completion rate — NO Fibonacci points, velocity, o

People who liked this also viewed

6 picks

Type

bmad-builder

467stars73forks

View on GitHub

How to install bmad-builder?

aj-geddes/claude-code-bmad-skills/bmad-builder

$npx -y skills add aj-geddes/claude-code-bmad-skills --skill bmad-builder

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# BMAD Builder
2
3	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.
4
5	## Scope (PLAN, never build)
6
7	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.
8
9	## Three intents
10
11	Always clarify which intent applies before starting.
12
13	### Create — new planning skill from scratch
14
15	1. Gather requirements (use TodoWrite to track):
16	- Skill name (lowercase-hyphen, prefixed `bmad-`; e.g. `bmad-example`)
17	- What planning/orchestration problem it solves
18	- Trigger phrases users will say
19	- Allowed tools (subset of: Read, Write, Edit, Bash, Glob, Grep, WebSearch, WebFetch, TodoWrite)
20	- Which BMAD track(s) it applies to (Quick Flow / BMad Method / Enterprise)
21	- Upstream BMAD counterpart (e.g. `bmad-risk-assessment`)
22
23	2. Run the scaffold script to create the directory:
24	```bash
25	bash ${CLAUDE_PLUGIN_ROOT}/skills/bmad-builder/scripts/scaffold-skill.sh <skill-name>
26	```
27	This creates `skills/<skill-name>/` with `scripts/` and `templates/` subdirectories and a starter SKILL.md.
28
29	3. Fill the SKILL.md using the skill template:
30	- Reference: `${CLAUDE_PLUGIN_ROOT}/skills/bmad-builder/templates/skill.template.md`
31	- Keep body under 5K tokens; push long reference detail to a sibling `REFERENCE.md` in the new skill's own folder
32	- Use `${CLAUDE_PLUGIN_ROOT}` for all paths to bundled scripts/templates
33	- Artifacts go to `bmad-output/` (honor user-configured folder)
34	- End with the mandatory attribution footer (see template)
35
36	4. Validate the new skill:
37	```bash
38	bash ${CLAUDE_PLUGIN_ROOT}/skills/bmad-builder/scripts/validate-skill.sh \
39	${CLAUDE_PLUGIN_ROOT}/skills/<skill-name>/SKILL.md
40	```
41	Fix all errors; review all warnings before declaring done.
42
43	### Validate — check an existing SKILL.md
44
45	Run the validator directly against any SKILL.md path:
46	```bash
47	bash ${CLAUDE_PLUGIN_ROOT}/skills/bmad-builder/scripts/validate-skill.sh <path-to-SKILL.md>
48	```
49
50	The validator checks:
51	- `name` field present and lowercase-hyphen
52	- `description` field present with trigger phrases
53	- `allowed-tools` field present (warns if missing)
54	- No dev/lint/build/coverage scope violations in `allowed-tools` or body
55	- File size within the ~5K token target (~20KB)
56	- Attribution footer present
57
58	### Scaffold — directory structure only
59
60	Use when you want an empty directory skeleton without generating content:
61	```bash
62	bash ${CLAUDE_PLUGIN_ROOT}/skills/bmad-builder/scripts/scaffold-skill.sh <skill-name>
63	```
64	Then fill SKILL.md manually using the template as a guide.
65
66	## Scope law for new skills
67
68	Every skill created by this builder MUST comply with the Scope Law:
69
70	- The plugin PLANS and ORCHESTRATES. It NEVER writes application code, runs tests, lints, checks coverage, builds, or reviews implemented code.
71	- The last artifact any skill may produce is a ready-for-dev story file or a handoff manifest. Implementation is handed to EXTERNAL dev tools/plugins.
72	- Acceptance Criteria, Testing STRATEGY, and Dev Notes are planning — allowed. Executing tests or writing implementation code is out of scope.
73
74	The `validate-skill.sh` script enforces this automatically by flagging forbidden terms.
75
76	## BMAD fidelity reminders
77
78	When designing skills, track the BMAD Method conventions:
79
80	\| Convention \| Rule \|
81	\|------------\|------\|
82	\| Scale Tracks \| Quick Flow / BMad Method / Enterprise — user confirms interactively \|
83	\| Story size \| ~2-8h, one dev-day max; split if larger \|
84	\| Delivery tracking \| Stories remaining / completion rate — NO Fibonacci points, velocity, o

People who liked this also viewed

6 picks

Type