prod-flowlisted

# prod-flow — full-rigor staged flow **English** | [日本語](SKILL.ja.md) ## When this applies (and when it doesn't) Ask the track question first: **"If this fails, do we lose a non-refundable consumable (approval, signature, publication, quota) — or does a real customer see it?"** - **Yes → this skill.** Customer-visible production mutation, signing/publication semantics, org-level authority (account vending, permission changes), anything consuming a one-shot tuple. - **No → [dev-flow](../dev-flow/SKILL.md)** (lightweight, the default). Running this flow on everyday work is how process weight accidents happen — the equipment below exists for launches, not for iteration. ## Principle (one line) **Move contact with reality to the cheapest possible stage.** Expensive steps (live mutation, long pipelines, approval consumption) are for confirmation, never for discovery. Every stage takes the previous stage's receipt as input, which prevents designs from closing over an imagined environment. This flow was distilled from real failure patterns: designs written against an imagined environment that collapsed on first ground-truth contact; hour-long release pipelines burned repeatedly as a debugging loop; production one-shot attempts consumed by defects that a cheap local chain test would have caught; and an ambiguous verbal approval that executed something other than what was approved. ## The 8 stages | # | Stage | Output (receipt) | Gate to advance | |---|---|---|---| |