m3taz-ahmed/aizee / skills/bmad-agent-po
bmad-agent-po
VerifiedSofia, the Product Owner: turns any input (an idea, brief, PRD, transcript, notes) into a ticket's requirements, slices initiatives into epics and epics into stories, writes and refines tickets, runs the board, validates the tree, replans when a change lands, and sets up the ticket store. Use when the user asks for Sofia or the product owner, or says 'create a spec', 'distill this PRD', 'write the initiative from', 'slice this', 'split this epic', 'break this into stories', 'make a ticket', 'refine this ticket', 'what's ready', 'status of', 'publish', 'validate these tickets', 'this changed, what now', 'set up the ticket store'.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 1.7 KB |
| assets/bug-template.md | markdown | 2.3 KB |
| assets/spike-template.md | markdown | 1.8 KB |
| assets/ticket-template.md | markdown | 5.6 KB |
| assets/tickets-template.toml | config | 3.0 KB |
| bmod.toml | config | 113 B |
| config/github-ticketing.toml | config | 4.6 KB |
| config/jira-ticketing.toml | config | 4.8 KB |
| config/linear-ticketing.toml | config | 4.0 KB |
| config/notion-ticketing.toml | config | 4.0 KB |
| config/repo-ticketing.toml | config | 2.6 KB |
| config/trello-ticketing.toml | config | 3.7 KB |
| customize.toml | config | 7.8 KB |
| references/board.md | markdown | 7.0 KB |
| references/replan.md | markdown | 1.4 KB |
| references/slice.md | markdown | 8.9 KB |
| references/spec.md | markdown | 6.3 KB |
| references/store-setup.md | markdown | 1.7 KB |
| references/ticket.md | markdown | 5.2 KB |
| references/validate-checks.md | markdown | 4.4 KB |
| references/validate.md | markdown | 1.8 KB |
| scripts/read_store.py | script | 4.6 KB |
| scripts/tests/test_read_store.py | script | 5.4 KB |
| scripts/tests/test_tickets.py | script | 109.4 KB |
| scripts/tickets.py | script | 81.7 KB |
| workflow.md | markdown | 8.2 KB |
config/linear-ticketing.toml
View on GitHub# Store starter: Linear. `scripts/read_store.py` reads this file as the base layer; the project's
# _bmad/custom/ticketing-store-config.toml names the store, fills the empty fields below, and replaces
# any other key here, key by key.
# It updates with the skill and holds only what is specific to this store: the rules every store shares
# are in references/board.md. Comments and `description` are never loaded; `description` is for choosing a store.
#
# One tool: Linear's official MCP server. Initiatives hold projects, parent issues are epics, labels carry
# type, relations carry blocking. Linear ships no CLI; community CLIs are not used here.
description = "Linear through its MCP server: projects, parent issues, relations, labels. For product teams on Linear."
[tickets]
store = "linear"
key = "" # Linear team key, e.g. "SHOP"; Linear assigns the number
team = "" # the default team, key or name. A container's own `key` overrides it for everything under it
access = """
Use the Linear MCP (create_issue, update_issue, create_project, update_project, get_issue,
list_issues, list_issue_statuses, create_issue_label, create_comment) against `team`. Confirm from the tool schema whether parent
and blockedBy take identifiers (SHOP-12) or ids, and the exact tool names against the server's list at first use.
"""
fields = """
severity is Linear's priority, set on the issue: P0 = Urgent, P1 = High, P2 = Medium, P3 = Low.
risk is a label risk:<value>; `setup` creates the three. estimate is Linear's estimate field on a story; a label est:<value> on an epic. Empty field: no priority, no label.
"""
reference = """
Also pass the url in the issue's links so it shows in the sidebar.
"""
[verbs]
setup = """
Connect, unless the Linear tools already answer: add the MCP server https://mcp.linear.app/mcp to
the agent tool in use (in Claude Code, `claude mcp add --transport http linear-server https://mcp.linear.app/mcp`),
then sign in over OAuth. Do not use the deprecated /sse endpoint.
`create_issue_label` for every non-empty value in [tickets.types], `hitl`, and risk:low, risk:medium,
risk:high that the team lacks. States
cannot be created from the MCP: `list_issue_statuses`, compare with [tickets.status], and tell the
user what to add under Settings, Teams, Issue statuses, or which map entry to set in the project's
store config. Linear's defaults (Backlog, Todo, In Progress, Done, Canceled) need no setup; [tickets.status]
also expects an In Review state in the Started group.
"""
write = """
The team is the ticket's own `key`, else that of the nearest container above it, else `team` here.
tracker_id is the issue's identifier and remote its url.
`create_issue` creates, `update_issue` changes — title, description, state, assignee, parent,
blockedBy, labels, priority, project. The issue's state is [tickets.status].<state>. Labels carry type, hitl, and
risk:<value>; priority carries severity per `fields`. A standalone ticket: omit parent and project.
Epics are parent issues. Set [tickets.types].initiative to map onto a Linear Initiative only when the
server exposes initiative tools.
"""
query = """
One issue: `get_issue` with includeRelations — labels, priority, state, assignee, parent,
project, relations, description; after is the "blocked by" relations, and the description's
covers holds the source requirement ids. Many: `list_issues` by project, parent, label, state, or
query words.
"""
# BMad type -> this store's type.
[tickets.types]
initiative = "" # empty: the initiative stays local. Linear has no Epic object and Projects cannot nest; set to "initiative" only to map onto Linear Initiatives, which nest five deep and allow several parents, so the tree cannot round-trip.
epic = "epic" # label on a parent issue
story = "story"
spike = "spike"
bug = "bug"
# BMad state -> this store's status.
[tickets.status]
backlog = "Backlog" # or "Todo" — the team's choice
in-progress = "In Progress"
review = "In Review" # not a default Linear state; `setup` asks for it. With no review state, set it to the in-progress one
done = "Done"
dropped = "Canceled"
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Unverified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |