consult-gateslisted

# Consult Gates -- Stage Gate Table Break work into stages; each stage answers one primary question; gates have entry and exit. ## Inputs | Input | Required | Notes | |---|---|---| | Phasing hints from `consult-arc` | yes | Sequence + option (MVP/Pilot/Full) if chosen | | `timeln-plan` artifact or stage list | optional | Import stage names / bets as raw material only -- rewrite for **client** phases | ## Workflow 1. Name **3-5 phases** max (merge weak phases). Order is linear unless source needs parallel -- if parallel, split rows and note dependency. 2. For each phase write: - **Primary question** -- exactly one yes/no or decidable question. - **Entry criteria** -- what must be true to start. - **Exit / outcome** -- what exists when the gate opens. - **Gate owner** -- role who says the gate passed; `unknown -- confirm` if missing. 3. Add **between-stage notes** only where ordering is controversial (one line: what must not happen out of order). ## Output -- exactly this shape ``` ## Gates -- <client or "TBD"> -- <YYYY-MM-DD> **Selected option:** MVP | Pilot | Full | mixed -- <note> | Phase | Primary question | Entry | Exit / outcome | Gate owner | |---|---|---|---|---| | 1 ... | | | | | | 2 ... | | | | | **Sequencing locks** - ... ``` ## Rules - Primary question is not a task list -- it is what the phase **decides**. - If input from `timeln-plan` conflicts with `consult-arc`, prefer `consult-arc` for naming; pull content from plan only when clearly the