Agent skill · operations · aj-geddes
bmad-init
Initialize a BMAD planning workspace: pick a scale-adaptive TRACK (Quick Flow / BMad Method / Enterprise) interactively, then scaffold the output folder, a config file, an empty decision-log.md, and a project-context.md "constitution". Use when the user says "initialize BMAD", "set up BMAD", "start a new BMAD project", "scaffold the planning workspace", "bmad init", "create the bmad config", or is beginning planning and has no bmad-output/ folder yet. Also use when the user asks "which track should I use?" or "what scale is my project?". This is the FIRST skill to run before any other planning workflow (brief, PRD, architecture, stories).
Why this skill is useful
Adds a script for initializing a BMAD planning workspace with specific configurations and decision logs that the AI wouldn't reliably generate on its own.
What it needs
Requires bash installed locally. About 3k tokens when loaded. Last updated 2026-06-20. 471 stars on the source repository.
What this skill does
BMAD Init — Workspace Scaffolder Set up the planning workspace and choose the TRACK that scales the rest of the BMAD planning workflows. This is a planning skill: it creates folders and seed documents only. It never writes application code, runs tests, or builds anything. What it produces Under the configured output folder (default bmad-output/): config.yaml is the single source of truth other skills read to find the output folder and the chosen track. The three TRACKS (never numbered Levels) Track Story count Planning artifacts ------- ------------- -------------------- Quick Flow 1–15 stories tech-spec only BMad Method 10–50+ stories PRD + Architecture (+ optional UX) Enterprise 30+ stories PRD + Architecture + Security + DevOps planning The track is a planning-need decision, not a points/velocity decision. Story count is a rough signal only; let scope, cross-team coordination, and risk drive the call. A heuristic may suggest a default — the user always confirms. Workflow 1. Check for an existing workspace. Glob for bmad-output/config.yaml (or a custom output folder if the user names one). If it exists, read it and ask whether to keep, re-run idempotently (safe — existing files are preserved), or change the track. Do not clobber a populated decision-log.md or project-context.md. 2. Gather rough scope signals in conversation (don't interrogate): One-line project description. Roughly how many distinct pieces of work / stories? (ranges are fine) Multiple teams or just one builder? Hard compliance / security / infra requirements? 3. Suggest a track. Run the helper to print the three tracks and a suggested default, then state your recommendation and ask the user to confirm or override: Heuristic the helper applies (you may reason past it): compliance/infra = yes, or 30+ stories → Enterprise 10+ stories, or PRD/architecture clearly needed → BMad Method otherwise → Quick Flow 4. Scaffold. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aj-geddes/bmad-init