Skip to main content
skill CX Codex

bmad-init — Claude Code skill: what it does, how to install

bmad-init — a skill for Claude Code sets up a BMAD planning workspace. Runs when starting a project to pick an adaptive track and scaffold planning files.

MIT 100 installs ★ 493 updated 2026-06-20

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add aj-geddes/claude-code-bmad-skills --skill bmad-init -a claude-code
Open on GitHub

What bmad-init does

Scaffolds the bmad-output/ directory with seed files: config.yaml, decision-log.md, project-context.md, and an empty stories/ directory. It handles planning structure only and never writes application code, tests, or build scripts.

The tool evaluates scope signals through select-track.sh based on story count and compliance needs. It suggests one of three tracks: Quick Flow for 1–15 stories, BMad Method for 10–50+ stories, or Enterprise for 30+ stories requiring security and DevOps artifacts. The initialization script init-project.sh runs idempotently, leaving populated context documents intact during updates. Running it requires an environment with Bash support.

What it helps with

  • scaffold planning directories and seed files for BMAD
  • determine the planning track based on project scale
  • set up initial project context and non-goals
  • validate existing bmad-output workspace files

Example prompts for the agent

  • Initialize BMAD workspace for this repository
  • Which BMAD track should I use for a 20-story project?
  • Validate the existing bmad-output workspace

How to install bmad-init

1Skills CLI (Vercel)

npx skills add aj-geddes/claude-code-bmad-skills --skill bmad-init -a claude-code

2Manually: put the files in place

~/.claude/skills/bmad-init/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/bmad-init/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about bmad-init

How to install bmad-init in Claude Code?

Run npx skills add aj-geddes/claude-code-bmad-skills --skill bmad-init -a claude-code. Alternatively, copy the file to ~/.claude/skills/bmad-init/SKILL.md.

What does bmad-init do?

It initializes the bmad-output/ workspace, writes config.yaml, seeds decision-log.md, and guides initial setup of project-context.md. It also selects the planning workflow track before story generation.

What is required to run bmad-init?

The skill requires Bash execution along with file inspection and editing tools like Read, Write, Edit, Glob, Grep, and TodoWrite.

Source text

SKILL.md · MIT
---
name: bmad-init
description: |
  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).
allowed-tools: Read, Write, Edit, Bash, Glob, Grep, TodoWrite
---

# 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/`):

```
bmad-output/
├── config.yaml          # project name, track, output paths, languages
├── decision-log.md      # empty threaded decision log (grows across workflows)
├── project-context.md   # the project "constitution" loaded by every later skill
└── stories/             # empty; future story files land here
```

`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**:

   ```bash
   bash "${CLAUDE_PLUGIN_ROOT}/skills/bmad-init/scripts/select-track.sh" --stories <N> --teams <one|many> --compliance <yes|no>
   ```

   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.** Once the user confirms name + track, run:

   ```bash
   bash "${CLAUDE_PLUGIN_ROOT}/skills/bmad-init/scripts/init-project.sh" \
     --name "<project name>" \
     --track <quick-flow|bmad-method|enterprise> \
     --output "bmad-output"
   ```

   The script is **idempotent**: it creates missing folders and seeds any missing
   template files, but never overwrites `decision-log.md` or `project-context.md`
   if they already contain content. It always (re)writes `config.yaml`.

5. **Open the constitution.** Walk the user through filling the first sections of
   `project-context.md` (project goal, primary users, constraints, non-goals). This
   is the document every downstream skill loads, so a few good sentences here pay off.
   Record the track choice and rationale as the first entry in `decision-log.md`.

6. **Hand off.** Recommend the next planning step based on track:
   - Quick Flow → tech-spec, then sprint-planning / story creation.
   - BMad Method → product brief → PRD → architecture.
   - Enterprise → product brief → PRD → architecture (+ security & DevOps planning).

## Three intents

- **Create** — fresh workspace (the common case).
- **Update** — change the track or rename the project: edit `config.yaml` and append
  the change to `decision-log.md` with a date and reason. Do not wipe other files.
- **Validate** — confirm the workspace is well-formed:
  ```bash
  bash "${CLAUDE_PLUGIN_ROOT}/skills/bmad-init/scripts/init-project.sh" --validate --output "bmad-output"
  ```

## Guardrails

- No numbered Levels anywhere — only the three named tracks.
- No story points, velocity, burndown. Delivery is **count-based** (stories
  remaining / completion rate). Story sizing target: small enough for one agent
  session (~2–8h); split anything larger.
- This skill stops at scaffolding. It hands off to other planning skills; it never
  implements, tests, lints, or builds.

See `REFERENCE.md` for the full config schema, track decision detail, and the
project-context section guide.

> ---
> Part of the **BMAD Planning & Orchestrator** plugin — a Claude Code harness for the **BMAD Method** by the **BMAD Code Organization** (https://github.com/bmad-code-org/BMAD-METHOD). Implements the spirit of `bmad-init`. All methodology credit belongs to the BMAD Code Organization.

© aj-geddes · MIT · aj-geddes/claude-code-bmad-skills

Similar skills

All skills for Agent setup: memory, context, orchestration →

From the same set11

The whole set →
bmad-brainstorm bmad-brainstorm runs structured ideation sessions using SCAMPER, SWOT, and 5 Whys. Delivers an organized markdown report ready for project planning. CX Codex +1 130installs bmad-tech-spec bmad-tech-spec generates a focused tech spec for small-scope work instead of a full PRD and architecture pair. Use it when requirements are clear, scope fits 1-15 stories, and you need one planning artifact before writing stories. CX Codex +1 114installs bmad-spec The bmad-spec Claude Code skill turns rough notes, a PRD, or a transcript into a compact SPEC.md with five sections. It activates when a project needs a clear problem statement and scope. CX Codex +1 108installs bmad-readiness-check The bmad-readiness-check Claude Code skill checks whether planning documents agree before implementation starts. Ask for it to validate requirements, architecture, and epics for build readiness. CX Codex +1 107installs bmad-document-project The bmad-document-project Claude Code skill scans an existing codebase in read-only mode to generate project-documentation.md. It maps runtime dependencies and entry points before downstream planning. CX Codex +1 104installs bmad-sprint-planning The bmad-sprint-planning Claude Code skill sorts stories by dependency and prepares a development handoff plan. Ask it to arrange stories, map parallel waves, or create sprint-status.yaml. CX Codex +1 104installs bmad-investigate The bmad-investigate Claude Code skill investigates bugs and turns findings into a case file. Invoke it to trace a reported failure, update an open investigation, or check a draft before handoff. CX Codex +1 102installs bmad-builder bmad-builder — a skill for Claude Code scaffolds and validates custom planning skills in the BMAD plugin. Generates folder trees and keeps instructions strictly inside planning boundaries. CX Codex +1 102installs

Project sponsors

Companies that keep this analytics open