shipkit-orch-shippinglisted

# shipkit-orch-shipping - Shipping Loop **Purpose**: Orchestrate implementation via an Agent Team, then verify quality and gate release. ## Standalone Invocation If invoked directly (no `orchestration.json` exists or `activeLoop` is not set by master): 1. Verify planning artifacts exist (`.shipkit/plans/` with at least one plan, `.shipkit/test-cases/`) — if missing, tell the user to run `/shipkit-orch-planning` first 2. Create `orchestration.json` yourself with `activeLoop: "shipping"` 3. Proceed with normal dispatch order below ## Scope Execution that delivers working software: - Code changes — Implementation by Agent Team - `.shipkit/verification-report.json` — Quality verification - `.shipkit/preflight.json` — Release gate ## Roster | Step | Method | What It Produces | |------|--------|-----------------| | `/shipkit-work-memory` | Skill dispatch | progress.json (checkpoint) | | Implement | Direct team (Agent tool) | code changes | | `/shipkit-review-shipping` | Skill dispatch → reviewer-shipping | verification-report.json | | `/shipkit-preflight` | Skill dispatch → reviewer-shipping | preflight.json | ## Done Condition `.shipkit/verification-report.json` has `status: "pass"` AND preflight passes. ## Orchestration Tracking After each major step and after each review cycle, update `.shipkit/orchestration.json` (read existing content first, merge your loop state): ```json { "loops": { "shipping": { "status": "in_progress", "currentSkill": "shipki