shipkit-orch-planninglisted

# shipkit-orch-planning - Planning Loop **Purpose**: Orchestrate the production and review of planning artifacts until product and engineering definitions are aligned and specs are complete. ## Standalone Invocation If invoked directly (no `orchestration.json` exists or `activeLoop` is not set by master): 1. Verify direction artifacts exist (`.shipkit/why.json`, `.shipkit/product-definition.json`, `.shipkit/engineering-definition.json`) — if missing, tell the user to run `/shipkit-orch-direction` first 2. Create `orchestration.json` yourself with `activeLoop: "planning"` 3. Proceed with normal dispatch order below ## Scope Planning artifacts that translate definitions into actionable plans: - `.shipkit/stack.json` — Tech stack context (prerequisite for specs/plans) - `.shipkit/codebase-index.json` — Codebase structure index (prerequisite for plans) - `.shipkit/spec-roadmap.json` — Spec priority order - `.shipkit/specs/*.json` — Feature specifications - `.shipkit/plans/*.json` — Implementation plans - `.shipkit/test-cases/` — Test specifications - `.shipkit/user-tasks.json` — Manual user tasks ## Roster | Skill | What It Produces | |-------|-----------------| | `/shipkit-project-context` | stack.json (also writes schema.json + env-requirements.md as bonus artifacts read by specs/plans) | | `/shipkit-codebase-index` | codebase-index.json | | `/shipkit-spec-roadmap` | spec-roadmap.json | | `/shipkit-spec` | specs/*.json | | `/shipkit-plan` | plans/*.json | | `/shipkit-tes