shipkit-orch-directionlisted

# shipkit-orch-direction - Direction Loop **Purpose**: Orchestrate the production and review of strategic artifacts until direction is coherent and stable. ## Standalone Invocation If invoked directly (no `orchestration.json` exists or `activeLoop` is not set by master): 1. Check that `.shipkit/` directory exists — if not, tell the user to run `/shipkit-why-project` first 2. Create `orchestration.json` yourself with `activeLoop: "direction"` 3. Proceed with normal dispatch order below ## Scope Strategic artifacts that define WHY, WHAT, and HOW at definition level: - `.shipkit/why.json` — Project vision and purpose - Stage assessment in why.json - `.shipkit/product-discovery.json` — Personas and user journeys - `.shipkit/product-definition.json` — Features, patterns, differentiators - `.shipkit/engineering-definition.json` — Mechanisms, components, stack - `.shipkit/architecture.json` — Architecture decisions (derived from engineering-definition) - `.shipkit/design-system/` — Design principles, tokens, aesthetic direction (UI projects only) - `.shipkit/goals/product.json` — Product success criteria - `.shipkit/goals/engineering.json` — Engineering success criteria ## Roster | Skill | What It Produces | |-------|-----------------| | `/shipkit-why-project` | why.json | | `/shipkit-stage` | goals/strategic.json | | `/shipkit-product-discovery` | product-discovery.json | | `/shipkit-product-definition` | product-definition.json | | `/shipkit-engineering-definition` | engine