superpowers-plus

Use when requesting-code-review is complete and all Critical/Important issues are resolved, before finishing-a-development-branch - dispatches an acceptance-tester subagent to verify every acceptance criterion

Use when a spec document has been approved during brainstorming and you need to produce testable acceptance criteria before writing the implementation plan - converts spec requirements into a structured acceptance criteria document

Use when a bug fix, architectural change, interface contract update, or recurring pitfall has been resolved and has clear reuse value — to record a durable lesson in project memory before the context is lost

Use when a repository or subsystem lacks usable canonical memory and needs an initial memory baseline

Use when a delivery cycle produced durable knowledge that should be preserved in canonical repository memory