--- name: papi-strategy description: Invoke when running strategy_review or making Active Decision changes. Covers strategy review cadence and AD lifecycle. --- # papi-strategy ## Strategy Reviews Every 5 cycles, PAPI offers a strategy review — a deep analysis of velocity, estimation accuracy, active decisions, and project direction. - **Don't skip them.** They're where compounding value comes from. - Run the review in your current conversation — a fresh one is only warranted if you're genuinely under context pressure (your host just compacted, or you're near the limit), never just because a review is next. - Reviews produce recommendations that feed into the next plan. - If the review recommends AD changes, use `strategy_change` to apply them. ## Active Decision Lifecycle Active Decisions (ADs) track architectural and product choices with confidence levels (LOW → MEDIUM → HIGH). - Check ADs before making architectural choices — run `health` for the AD summary. - ADs are for product/architecture choices only, not process preferences. - When new evidence appears, update AD confidence via `strategy_change`. - Supersede rather than overwrite — old decisions stay as history. - **A contradiction is not a veto.** If an idea or task cuts against a live AD, that is a decision for the user — never your reason to drop it. Submit it with `idea` + `conflicts_with_ad: "AD-N"`: the task is created and parked behind a decision gate, surfaces in `orient` as waiting on the owner, and returns to the board on its own once the AD is superseded, modified, or reaffirmed. Shelving the work instead means the AD never gets tested by the evidence that would have challenged it. - New ADs should include a `### Reversal Trigger` section: specify the signal that would invalidate the stance, the action to take (modify/supersede/abandon), and why writing it now prevents sunk-cost drift later.