Skip to content

m3taz-ahmed/aizee / skills/bmad-agent-po

bmad-agent-po

Verified

Sofia, 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'.

references/validate.md

View on GitHub
# Validating tickets

The checks are in `{{ rendered("references/validate-checks.md") }}`, one section per scope. Fresh-context subagents run them, given the file's path and their section names. They find missing prerequisites `tickets.py` cannot see.

{{ workflow.validate_before }}

- **Proposed child initiatives or epics, an epic breakdown, or a re-slice:** always, on the draft `tickets.toml` before approval. First run the Dependencies section yourself and fix the draft; give the agent its path. Show what the check changed and confirmed. Rerun when the user adds, removes, merges, or reorders items. At initiative slicing, check scope ownership; future epics need no stories or full detail.
- **A refined ticket:** before execution.
- **A container:** before closure, its implemented coverage and Done when.

How:

- Per epic: its container, its `tickets.toml`, every child ticket, done ones too, its Requirements, its `sources:` files, companions; sections Ticket, Set, Dependencies. The tree: the initiative, its `tickets.toml`, the epic files once written (on a parent, each child initiative's file), its `sources:` files; sections Tree, Dependencies. A single ticket: its epic file; section Ticket. Closure: section Closure.
- Name the `refined: true` tickets; point the agent at "Rules the template cannot carry" in `{{ rendered("references/ticket.md") }}`. Once `tickets.toml` exists, give the full `tickets.py status` command for the folder.
- Sort findings into fix (mechanical), suggest (with reason), or ask the user. Resolve gaps, missing prerequisites, and contradictions before proceeding; the user decides suggestions and scope changes.
- Do not re-raise suggestions declined in a `Decision:` line unless new evidence changes their basis.

{{ workflow.validate_after }}
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: 472kUpdated Claude CodeCodexVerifiedInstall
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: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
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 availableStars: 322kUpdated Claude CodeCodexVerifiedInstall