skill CX Codex

bmad · akillness — Claude Code skill: BMAD phases and the next artifact

Q: How do I install bmad in Claude?

Run `npx skills add akillness/jeo-skills --skill bmad -a claude-code`. The skill file then lives at `~/.claude/skills/bmad/SKILL.md`.

Q: How is bmad different from bmad-idea and plannotator?

bmad is the shared front door. `bmad-idea` handles early concept framing, `plannotator` covers artifact approval and review, and `task-planning` does backlog slicing.

Reads your current project state and names the next BMAD artifact or gate. Useful when you are stuck after idea notes, a PRD or an architecture draft.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓

npx skills add akillness/jeo-skills --skill bmad -a claude-code

Open on GitHub

What bmad does

The skill acts as a front door into a BMAD/BMM workflow. It first classifies what you already have: idea notes, a product brief, a PRD, a tech spec, an architecture draft, review feedback, an active repo or milestone pressure. Then it picks a project level from 0 to 4 and infers the likely current phase.

What you get back is one next step, not a stack of parallel documents. If an artifact exists but was never reviewed, the skill often points at the review gate instead of another draft. For level 0–1 work it does not push heavy planning or architecture. Specialist jobs are routed outward on purpose: bmad-idea for early concept framing, plannotator for approval, task-planning for backlog slicing, and oh-my-claudecode, oh-my-codex or oh-my-agent for runtime setup.

Under the hood are references/intake-packets-and-route-outs.md, references/core-routing.md, references/status-and-review.md and references/runtime-and-module-boundaries.md. The skill is allowed Read, Write, Bash, Grep and Glob, so it inspects repo state itself. When a project already exists, it prefers a brownfield-resume packet over pretending you are starting fresh — worth checking, because that is where a working repo can get misread as a clean slate.

What it helps with

figure out which BMAD phase follows idea notes
choose between a PRD and a tech spec during planning
decide whether a review gate is needed before moving on
turn an approved architecture into a sprint plan
pick the next step inside an existing repository

Example prompts for the agent

I have idea notes and a draft PRD — what comes next in BMAD?
The project is already in a repo with some features built. What is the next artifact?
Architecture is done but not approved. What now?

How to install bmad

1Skills CLI (Vercel)

npx skills add akillness/jeo-skills --skill bmad -a claude-code

2Manually: put the files in place

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

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

1Skills CLI (Vercel)

npx skills add akillness/jeo-skills --skill bmad -a codex

2Manually: put the files in place

.agents/skills/bmad/SKILL.md

For all projects use ~/.agents/skills/

1Skills CLI (Vercel)

npx skills add akillness/jeo-skills --skill bmad -a cursor

2Manually: put the files in place

.cursor/skills/bmad/SKILL.md

Cursor also reads .agents/skills/ and .claude/skills/

1GitHub CLI

gh skill install akillness/jeo-skills bmad

2Manually: put the files in place

.github/skills/bmad/SKILL.md

1Skills CLI (Vercel)

npx skills add akillness/jeo-skills --skill bmad -a gemini-cli

2Platform CLI

gemini skills install https://github.com/akillness/jeo-skills --path .agent-skills/bmad

Manually: put the files in place

.devin/skills/bmad/SKILL.md

The legacy .windsurf/skills/ path still works

Skills CLI (Vercel)

npx skills add akillness/jeo-skills --skill bmad -a opencode

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

Questions about bmad

How do I install bmad in Claude?

Run npx skills add akillness/jeo-skills --skill bmad -a claude-code. The skill file then lives at ~/.claude/skills/bmad/SKILL.md.

What does bmad do?

It classifies your current packet, picks a project level and the likely BMAD phase, then recommends a single next artifact or gate. Specialist work is handed off to other skills.

How is bmad different from bmad-idea and plannotator?

bmad is the shared front door. bmad-idea handles early concept framing, plannotator covers artifact approval and review, and task-planning does backlog slicing.

bmad by other authors comes first.

bmad bmad-code-org Coordinates BMad Method modules, recommends the next skill, and tracks project initiatives. Useful when setting up or repairing your workflow. CX Codex +1 13,300installs bmad-architecture bmad-code-org Writes a short architecture document that pins down only the invariants keeping independently built parts of a system from diverging. CX Codex +1 12,000installs bmad-brainstorming bmad-code-org The skill runs a brainstorming session: the agent asks one question at a time, rotates creative techniques and logs ideas to a memlog. Useful when you want more options than you'd get alone. CX Codex +1 12,000installs speckit-plan github-spec-kit Executes implementation planning workflows inside spec-kit projects to produce research notes and interface contracts. CX Codex +1 2,500installs goal-plan ruvnet A skill that builds step-by-step plans for complex tasks, tracks what conditions must be met before each step, estimates costs, and switches to an alternative path if something fails. CX Codex +1 770installs bmad-marketing-growth-module reason-machines A BMAD Framework module with 14 agents and 6 workflows that covers SaaS marketing from strategy down to per-platform posts. CX Codex +1 908installs think tw93 Turns a rough idea into a plan with a recommendation, success criteria, and checks. Use it to weigh architecture choices or prepare a handoff before coding. CX Codex +1 15,000installs

From the same set22

plannotator The skill opens a browser approval loop: a human reads a plan, diff or spec and leaves notes before any code gets written. CX Codex +1 379installs marketing-automation The skill turns a vague marketing request into one operating mode, one discipline and one operator packet with an owner and proof. CX Codex +1 377installs monitoring-observability Turns service, data-pipeline, or live-ops context into a monitoring brief with a primary mode, useful signals, and a small first implementation slice. CX Codex +1 369installs authentication-setup Walks you through choosing an auth lane for a web app or API and drawing the line between what the provider owns and what stays in your app. CX Codex +1 368installs state-management A skill that classifies React state into packets and picks the narrowest owner, so you stop arguing about libraries before you know what the state is. CX Codex +1 365installs sprint-retrospective Runs a sprint or milestone retrospective and turns it into a few owned actions instead of another template ritual. CX Codex +1 364installs debugging A skill that walks the agent through a reproduce → isolate → verify loop for concrete bugs, regressions and flaky failures. Useful once you already have a failing test or request. CX Codex +1 361installs system-environment-setup A skill that makes a repo runnable on any machine: pinned runtimes, local services, containers, bootstrap scripts and setup diagnosis. CX Codex +1 351installs