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/store-setup.md

View on GitHub
# Setting up the store

`{skill-root}/scripts/read_store.py` layers the project file `{project-root}/_bmad/custom/ticketing-store-config.toml` over the starter `{skill-root}/config/<store>-ticketing.toml`; the project file's keys win. No project file means the repo store.

Run this to connect, reconfigure, or switch a tracker.

{{ workflow.store_before }}

1. **Choose.** `uv run {skill-root}/scripts/read_store.py --starters` lists the shipped stores. The user may bring their own config file or url.
2. **Write the project file.** `[tickets]` with `store` and the starter's empty address fields, asked of the user. Copy nothing else from the starter; cut a whole-starter copy down to `store`, the address fields, and the team's changes. The user's own config goes in whole; a store with no starter is modelled on the nearest one. For the repo store, delete the project file.
3. **Connect.** Offer to run the store's `setup` verb. Tracker types or statuses that differ from the maps go under `[tickets.types]` or `[tickets.status]`. A state with no tracker status takes the previous state's status.
4. **Prove it.** Offer a test. With items, `query` a few back. Empty: create a ticket in `backlog/` titled "BMad setup test — safe to delete", query it back, move it to `in-progress`, assign it, then drop it. Give the user the `remote` url.

A house rule on a verb goes in `persistent_facts` in this skill's customization; set a whole verb under `[verbs]` in the project file only when the store's commands differ.

Then return to the user's task; when done, offer once a `bmad-customize` pass on this skill: its `customize.toml` holds the epic boundary rule, publication timing, own checks, templates, and before and after instructions.

{{ workflow.store_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