prospectlisted

# /prospect — Plan pre-mortem with risk enforcement Run a structured pre-mortem on a plan or approach that has been *created but not yet executed*. Forward-looking counterpart to `/retrospect`. Produces a 10-section markdown report with per-step verdicts, risk status, action recommendations, and process pre-mortem when the plan-formation itself was thin. Writes findings to `knowledge/logs/prospect/` and runs aria's standard intake. The discipline this enforces: before the first edit lands, every planned step gets named, its evidence base examined, its smallest viable version identified, and its action gated on the strength of the underlying hypothesis. Mirrors `/retrospect`'s shape so the same review muscle works in both directions. ## When to use - After a multi-step plan is articulated (in chat, in TodoWrite, in a `.md` plan file) but no code has been written yet - After `/brainstorming` concludes with an action plan - After `/distill` produces a task spec that's about to be executed - After a Linear ticket's Technical Intake is drafted and the implementer is about to begin - Before kicking off a long autonomous run (e.g., `combined go`) on a non-trivial plan - As a soft-suggested response to "let me implement…", "I'll just code it…", "ok ship it" when no validation exists yet If code has already been written/committed (even in-session), use `/retrospect` instead — that pivots from forward-looking to backward-looking validation. ## Step 0: Inputs & Mode Detection Par