pm

Project-management discipline that sits ABOVE OpenSpec and Superpowers. Use whenever work spans more than one epic, when a review or build reveals something broken/orphaned/unwired that forces a detour, when deciding what to work on next, or when resuming after a context compaction. Keeps a single lane-agnostic index of epics, an explicit detour stack, and epic links so nothing is lost across pivots. Triggers: "what were we working on", "what's next", "this is broken, fix it first", "park this", "resume", "where did we leave off".

Route what the work taught you instead of leaving it in the transcript — a practice you invented becomes a candidate improvement with its evidence attached, and a workaround you invented for your tooling's friction becomes a filed bug. Use whenever you adopt a new practice, gate, discipline or checklist, whenever you route around friction in a tool rather than reporting it, whenever you hand-edit a file a tool owns because no verb exists for it, and at the end of any epic or release. Triggers "should this be in the product", "dogfood", "we should do this every time", "I had to work around", "there's no verb for this", "let me just edit that file by hand".

Keep a repository's hard-won PROCESS knowledge where it fires on the situation instead of on recall — consult a lesson before a risky operation, capture one the moment it is earned, and let the PreToolUse advisor surface a known lesson before the mistake. Use when about to run parallel agents in one checkout, commit while something else may be staging, hand-edit a file a tool also generates, measure a suite while agents write, invoke a slash command for the tool you are developing, or decide what to fix from a review — and the moment you undo work, kill and restart, hit the same problem twice, or say "that was my error". Triggers "lessons learned", "have we hit this before", "what went wrong last time", "post-mortem", "we should write this down", "that cost us", "I did that wrong".