Claude Skill MartBrowse skillsQuick linesLearn by videoTerminal guideWhat is a Skill?
← Back to list

BMad Ticket Manager

A BMad-native skill that slices initiatives into epics and stories, writes/refines tickets, and runs the whole board.

Dev & CodingAdvanced★ 428⑂ 46AI score 9/10Last updated: Sep 28, 2026

What it does

  • Hierarchical breakdown: turns an idea, brief, or PRD into an initiative ticket, slices it into epics, and cuts epics into stories, spikes, or bugs sized for a single agent session.
  • Ticket authoring & refinement: starts from a per-type template, then works with you on description, Verify: check, requirement references, build order, prerequisites (after), and open uncertainty.
  • Board operations: publish, start, move, assign, block, close, drop, "what's ready/next", and status for a single ticket or an entire tree.
  • Validation & estimation: configurable checks at ticket/set/tree/closure scope, point or t-shirt estimation, actuals, and scale calibration.
  • Store integration: git-backed tree by default, with an optional external tracker as a remote synced through explicit status maps.

Who it's for

  • Teams and solo devs already on (or adopting) BMAD-METHOD
  • Anyone who wants work chopped into agent-buildable slices with explicit sequencing
  • People who want specs, tickets, and build status to live in one consistent tree

Examples

  1. "Create a new initiative from this PRD and split it into epics" → creates the initiative envelope, then proposes epic boundaries tied to stable requirement ids.
  2. "Incept this epic" → records ordered story entries with prerequisites in the epic's tickets.toml.
  3. "What's ready?" / "Status of story 1.2" → a board grouped by state, or a resolved single-ticket report with file and plan paths.

Note: it will not run without BMad artifacts in the project (_bmad/scripts/resolve_config.py, ticketing-store-config.toml, uv).

· · · Install guide · · ·

Try it now, no install

Paste this into Claude to use the skill without installing anything.

Read the instructions in this file and follow them to help me:
https://raw.githubusercontent.com/aiskillstore/marketplace/HEAD/pending/bmad-code-org/bmad-ticket/SKILL.md

What I want: (describe your task here)

If Claude can't open the link, open it yourself and paste the contents instead.

↓ If it works for you, download the ZIP below and install it. Then it runs on its own — no pasting each time.

Install in the Claude app (no terminal)
  1. Download the ZIP with the button below.
  2. In Claude, open Settings → Capabilities and turn on 'Code execution and file creation'. (one time)
  3. Go to Customize → Skills → + → 'Upload a skill' and upload the ZIP.
↓ Download ZIP
Install in Claude Code

Let Claude do it — paste this into Claude Code

Install the skill I found on Claude Skill Mart.
Copy the pending/bmad-code-org/bmad-ticket folder from the GitHub repo aiskillstore/marketplace into my ~/.claude/skills/bmad-ticket/.
When it's done, tell me in one line what this skill can do.

Install with a command instead

git clone https://github.com/aiskillstore/marketplace.git /tmp/marketplace && mkdir -p ~/.claude/skills && cp -r /tmp/marketplace/pending/bmad-code-org/bmad-ticket ~/.claude/skills/

⚠ This is a third-party skill. Check the source repository before installing.

  1. Prerequisites: confirm the uv runtime with uv --version (install from https://docs.astral.sh/uv if missing).
  2. Install BMad first: in your project folder run npx skills add bmad-code-org/BMAD-METHOD --skill bmad, then ask the bmad skill in Claude Code to run setup so the _bmad folder is created.
  3. Install this skill: run npx skills add bmad-code-org/BMAD-METHOD --skill bmad-ticket, or pull it from the marketplace repo in one line:
    git clone https://github.com/aiskillstore/marketplace.git /tmp/marketplace && mkdir -p ~/.claude/skills && cp -r /tmp/marketplace/pending/bmad-code-org/bmad-ticket ~/.claude/skills/
    
  4. Verify: ls ~/.claude/skills/bmad-ticket should show SKILL.md, references/, and scripts/.
  5. Restart Claude Code, then try "Create a new initiative" or "Break this epic into stories" to confirm the trigger fires.
  6. Configure the store: if no store config exists, follow the skill's references/store-setup.md walkthrough to wire up the git tree or an external tracker.