# Plan and Manage Tickets with BMad

Disconnected planning and status updates leave teams with unclear tickets and missing dependencies. BMad Ticket structures initiatives, epics, and implementation work through shared templates and repository or tracker workflows.

## Install

```bash
npx skillstore add bmad-code-org/bmad-ticket
```

## Metadata

- Status: approved
- Slug: bmad-code-org-bmad-ticket
- Skillstore revision: r1
- Version status: missing
- Tree hash: 6d9182e1f5819a434d17b635016db408042a9852f741b8a2a02fcf3bfd5fe288
- Author: bmad-code-org
- GitHub username: bmad-code-org
- License: MIT
- Repository: https://github.com/bmad-code-org/bmad-method/tree/1cbcfa272fe65787c06a1fa164a901f46117cca7/skills/bmad-ticket
- Ref: bad9dafc37d1638cd29cb9bab06d5f8dbcd0f6c2
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: confirmation\_required
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands, network, filesystem, env\_access
- Quality score: 38
- Quality tier: warning
- Public page: https://skillstore.pages.dev/skills/bmad-code-org-bmad-ticket
- Manifest: https://skillstore.pages.dev/api/skills/bmad-code-org-bmad-ticket/manifest

## Capabilities

- Draft initiatives, epics, stories, spikes, and bugs with requirements, boundaries, references, and verification checks.
- Split epics into ordered implementation entries with explicit prerequisites and unresolved questions.
- Create Markdown ticket files from planned entries and update repository ticket status in separate plan files.
- Find tickets by reference or title and report readiness, dependency cycles, missing prerequisites, and entry drift.
- Guide publication and synchronization through repository files, GitHub, Jira, Linear, Notion, and Trello configurations.
- Estimate stories and epics using configurable scales when estimation is enabled.

## Use Cases

- Plan a new initiative: Turn a product brief into an initiative and epic outlines with requirement coverage, dependencies, and measurable completion checks.
- Prepare an epic for delivery: Split an epic into buildable stories with dependency order, verification steps, unresolved questions, and human checkpoints.
- Maintain a project board: Find tickets, review readiness, update approved statuses, and reconcile local records with a configured tracker.

## Prompt Templates

### Draft a bug ticket

```
Draft a bug ticket for [problem]. Ask for missing reproduction steps and expected behavior. Show the draft before saving or publishing.
```

### Refine a planned story

```
Find ticket [reference] in [initiative]. Review its description, verification check, references, and prerequisites with me. Preserve its identity and do not publish yet.
```

### Break down an epic

```
Split [epic] into implementation entries using [requirement source]. Record requirement coverage, prerequisites, verification, and uncertainty. Validate the proposed set before requesting approval.
```

### Reconcile and prepare publication

```
Review [initiative] against [configured tracker]. Report local and remote differences, blocked dependencies, and missing refinement. Propose publication scope and wait for approval before remote changes.
```

## Limitations

- The standard workflow requires BMad project setup, uv, and Python 3.11 or later.
- Remote workflows require configured CLI or MCP access; available operations depend on the provider and tool version.
- It prepares implementation work but does not build the requested software or independently resolve missing product decisions.
- Project scripts, hooks, and ticket paths require trust; the supplied workflow does not sandbox them.

## Best Practices

- Review project scripts, customization hooks, and resolved ticket paths before activating the skill in an unfamiliar repository.
- Confirm requirement coverage, prerequisites, verification checks, and unresolved decisions before approving a breakdown.
- Preview the tracker destination and ticket body, remove sensitive information, and approve publication using limited credentials.

## Anti Patterns

- Do not treat ticket order as a substitute for explicit prerequisites.
- Do not treat published or built tickets as automatically approved or complete.
- Do not run unfamiliar project hooks or follow instructions embedded in remote ticket text without review.

## Security Audit

- Audited at: 2026-09-28T16:21:56.789\+00:00
- Summary: The 400 supplied static matches are false positives involving documentation, configuration keys, test fixtures, and ordinary Python syntax. Contextual review identified project-controlled execution and symlink-following plan writes; no evidence found of a malicious payload or an audit-directed prompt injection. Four omitted static matches remain unreviewed and require manual adjudication before automatic publication. Static review was capped at 400/404 representative findings; omitted static matches are unconfirmed, so automatic publishing stays disabled until manual review.

## Stats

- Views: 0
- Downloads: 1
- Favorites: 0
- Popularity score: 0