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 |
references/validate-checks.md
View on GitHub# Validation checks
`validate.md` assigns sections to agents.
## Ticket
- References open; no unfilled placeholders; assumptions marked.
- Nothing contradicts its epic file, its companions, the architecture, or a recorded decision.
- Each entry has a description, `unknown` when one is known, and a `verify` a non-builder can run; only bugs, `refine = true` entries, and leaves with no entry need full criteria before execution.
- A ticket needing full criteria and covering an id in a `Source conflict:` line with no later `Decision:` has `refined: false`.
{% if workflow.checks.ticket %}
{{ workflow.checks.ticket }}
{% endif %}
## Set
Every entry in the epic's `tickets.toml`, draft or committed, pulled or not.
- Tickets cover every Requirements line not deferred with the user; each `covers` id exists there; tickets sharing an id say which part each delivers.
- UX, architecture, constraint and integration work is covered without ids; results satisfy Done when; citing an id alone is not coverage.
- Every `after`, cross-epic too, is a real prerequisite, not restated order; once `tickets.toml` exists, `tickets.py status` on the epic shows no cycle, `drift`, `unpinned_after`, `undeclared_after`, or `order_conflict`; the epic's Notes hold a dated `Decision:` line naming the tracer bullet, and the sequencing decisions.
- A builder could write each story's acceptance criteria from the epic, entry, and references; if not, fix the epic, not the one-sentence `description` and `verify`.
- Tracer bullet, as rendered in `slice.md`: {{ workflow.tickets_tracer_bullet }}
- Refactor sweep, as rendered in `slice.md`: {{ workflow.tickets_refactor_sweep }}
{% if workflow.checks.set %}
{{ workflow.checks.set }}
{% endif %}
## Tree
The initiative, its `tickets.toml`, draft or committed, and the epic files once written; for a parent initiative, the child initiatives in place of epics.
- Every initiative requirement has an accountable epic or agreed deferral; shared ones say which part each epic delivers; no unexplained overlap.
- Each epic's `covers` cites parent ids; each Requirements line names in parentheses its parent id, or its source section if the parent lacks it; a child's `covers` resolves through the Requirements line to a parent id.
- Every source id on a Requirements line exists in a `sources:` file, every parent id in the parent's Requirements; every adopted design or architecture document is in `companions:`.
- Every unit the source touches is an epic, out of scope, or a touch point (consumed or configured only, named in the initiative's Boundaries with its owner).
- Each decision several epics adopt has one home: an architecture spine section, or an opening-epic entry (first `[[epic]]`) the others wait on.
- Every written epic file has Outcome, Done when (including production delivery), Boundaries, its `covers`, and references; one with `refined: false` needs no Requirements or breakdown yet; the initiative's `tickets.toml` lists every epic in build order, each `after` naming what it needs, and `tickets.py status` on the initiative shows no cycle or `order_conflict`; it opens with a platform-baseline epic, or its first epic's first stories, or a `Decision:` line saying why not.
- A parent initiative's `tickets.toml` lists every child in build order, each `after` naming what it needs; every child's `sources:` lists the parent's file; `tickets.py status` on the parent shows no `order_conflict`.
- The initiative's `tickets.toml` lists child initiatives, epics, or entries, one kind only; with epics, no leaf sits in the initiative's `tickets/` folder.
{% if workflow.checks.tree %}
{{ workflow.checks.tree }}
{% endif %}
## Dependencies
An item is a set entry, a tree epic, or a parent's child initiative.
- Needs: what each item needs to start and to run its check is built by it or its `after`.
- Collisions: items with no dependency path share no code, config, schema, or setup; else add an `after` or merge them.
- Shared setup: the earliest item needing it owns it; others list it in `after`.
- Handoffs: when one item relies on another's output, both descriptions say so.
{% if workflow.checks.dependencies %}
{{ workflow.checks.dependencies }}
{% endif %}
## Closure
- Verify the container's Done when, requirements, constraints and companions against implementation evidence, not child status; explain dropped work and confirm remaining scope with the user.
{% if workflow.checks.closure %}
{{ workflow.checks.closure }}
{% endif %}
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 |