Agent skill · writing content · 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. Use when the user says "create a skill", "scaffold a skill", "build a new planning skill", "add a skill to the orchestrator", "extend BMAD planning", "custom orchestration skill", "validate this skill", "check this skill for scope violations", "new skill for the planner", or "bmad-builder". Supports three intents: Create (new skill skeleton), Validate (check an existing SKILL.md), Scaffold (directory structure only). This skill plans and scaffolds only — it NEVER writes application code, runs tests, lints, or builds.
Why this skill is useful
Adds specific scripts and templates for creating and validating BMAD Planning & Orchestrator skills, which are not commonly found in public documentation.
What it needs
Requires bash installed locally. About 4k tokens when loaded. Last updated 2026-06-20. 471 stars on the source repository.
What this skill does
BMAD Builder 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. Scope (PLAN, never build) 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. Three intents Always clarify which intent applies before starting. Create — new planning skill from scratch 1. Gather requirements (use TodoWrite to track): Skill name (lowercase-hyphen, prefixed bmad-; e.g. bmad-example) What planning/orchestration problem it solves Trigger phrases users will say Allowed tools (subset of: Read, Write, Edit, Bash, Glob, Grep, WebSearch, WebFetch, TodoWrite) Which BMAD track(s) it applies to (Quick Flow / BMad Method / Enterprise) Upstream BMAD counterpart (e.g. bmad-risk-assessment) 2. Run the scaffold script to create the directory: This creates skills/<skill-name>/ with scripts/ and templates/ subdirectories and a starter SKILL.md. 3. Fill the SKILL.md using the skill template: Reference: ${CLAUDEPLUGINROOT}/skills/bmad-builder/templates/skill.template.md Keep body under 5K tokens; push long reference detail to a sibling REFERENCE.md in the new skill's own folder Use ${CLAUDEPLUGINROOT} for all paths to bundled scripts/templates Artifacts go to bmad-output/ (honor user-configured folder) End with the mandatory attribution footer (see template) 4. Validate the new skill: Fix all errors; review all warnings before declaring done. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aj-geddes/bmad-builder