shipkit-stagelisted

# shipkit-stage — Project Stage & Graduation Criteria **Purpose**: Define the project stage (POC/Alpha/MVP/Scale), derive scope constraints and quality bars from that stage, set business-metric criteria (S-*), and define stage gates. Evaluate mode assesses gate readiness for human-approved graduation. **What it does**: Reads the project vision and codebase signals, proposes a stage (confirms with user via `AskUserQuestion`), derives constraints and business metrics, defines gates with S-* criteria, and writes `goals/strategic.json`. Runs inline to avoid hallucinating stage decisions. Evaluate mode is user-invoked and human-gated — it cross-references ALL goal files to build a graduation evidence table for human approval. **Output**: One JSON file: - `goals/strategic.json` — Stage, constraints, stageImplications, business-metric criteria, gates > **Product goals** (user outcomes: P-*) are handled by `/shipkit-product-goals`. **Engineering goals** (technical performance: E-*) are handled by `/shipkit-engineering-goals`. Both skills append their criteria IDs to the gates defined here. --- ## Modes | Mode | Trigger | What It Does | |------|---------|-------------| | **Set** (default) | "Set stage", "stage", "constraints" | Set stage, derive constraints + business metrics, define gates | | **Evaluate** | `--evaluate`, "graduation", "ready to advance?" | Cross-check all criteria across all goal files, build evidence table, recommend graduation | --- ## When to Invoke **Us