shipkit-engineering-goalslisted

# shipkit-engineering-goals — Technical Performance Criteria **Purpose**: Derive measurable technical performance criteria from the engineering blueprint. Each mechanism, component, and design decision implies criteria for "how do we know this performs?" — this skill makes those criteria explicit, measurable, and trackable. **What it does**: Reads the engineering blueprint + stage context, proposes technical criteria (confirms with user via `AskUserQuestion`), writes the engineering goal file, and adds engineering criteria to existing stage gates. Runs inline to avoid hallucinating SLA targets. **Output**: One JSON file: - `goals/engineering.json` — Technical-performance criteria (EM owns) > **Strategic goals** (stage, constraints, business metrics: S-*) are handled by `/shipkit-stage`, owned by the Visionary agent. Run that skill first — it creates the stage gates that engineering criteria are added to. > **Product goals** (user outcomes: P-*) are handled by `/shipkit-product-goals`, owned by the PM agent. --- ## Modes | Mode | Trigger | What It Does | |------|---------|-------------| | **Define** (default) | "engineering goals", "technical criteria", "SLAs" | Derive criteria from engineering blueprint, write engineering.json | | **Evaluate** | `--evaluate`, "check engineering metrics" | Compare actuals to targets, output technical gap report | --- ## When to Invoke **User triggers**: - "Define engineering goals", "Technical performance criteria" - "SLAs", "Respons