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/replan.md

View on GitHub
# Replanning

Leave the remaining tickets true and nothing already built rewritten. No proposal file.

{{ workflow.replan_before }}

1. **Name the change** briefly: what changed, its source and evidence. Read the ticket, its `.memlog.md`, breakdown, finished children, and any architecture or design it touches; ask only what the tree cannot tell you. Say whether what is required changed or only how it is delivered, and propose a way forward (adjust remaining entries, roll back built work, or cut scope) with the reason; the user decides. An in-progress ticket: ask whether its build stops; never edit its plan.
2. **What is required.** When the change alters what the ticket requires, run `spec.md` on it with the change as input: lines re-render with ids kept, naming entries whose `covers` cite a changed id. Otherwise say so and skip.
3. **Re-slice** each affected epic per Re-slicing in `slice.md`; an obsolete or new epic changes the initiative's breakdown per Initiative into epics there.
4. **Drop** what no longer belongs per Close, drop, move in `board.md`, and clear what waited on it.
5. **Record the reason** as a dated `Decision:` line in the Notes of each container touched, in step 1's words. If the architecture spine or design is invalidated, note it in the container's Notes and offer `bmad-architecture` or `bmad-ux`; never edit the companion.

Then report what changed, was dropped, and is ready.

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