Shipkit Orch Direction

Roster

Done Condition

All direction artifacts exist AND .shipkit/reviews/direction-assessment.json has status: "pass".

Orchestration Tracking

After each skill dispatch and after each review cycle, update .shipkit/orchestration.json:

{
  "activeLoop": "direction",
  "status": "in_progress",
  "loops": {
    "direction": {
      "status": "in_progress",
      "currentSkill": "shipkit-why-project",
      "completedDispatches": [
        { "skill": "shipkit-why-project", "timestamp": "ISO" }
      ],
      "reviewCycles": 0
    }
  }
}

Set status to "pass" or "partial" when the loop finishes. Increment reviewCycles each time /shipkit-review-direction runs.

Dispatch Order

Completion Tracking (MANDATORY)

Before dispatching any skills, create tasks for every dispatch in the roster:

1. TaskCreate for each producer dispatch:
   • "Dispatch: /shipkit-why-project"
   • "Dispatch: /shipkit-stage"
   • "Dispatch: /shipkit-product-discovery"
   • "Dispatch: /shipkit-product-definition"
   • "Dispatch: /shipkit-engineering-definition"
   • "Dispatch: /shipkit-design-system" (skip if no UI — check stack.json for frontend framework)
   • "Dispatch: /shipkit-product-goals"
   • "Dispatch: /shipkit-engineering-goals"
2. TaskCreate: "Review: /shipkit-review-direction"
3. TaskCreate: "Re-dispatch for gaps (if needed)"
4. TaskCreate: "Re-review after fixes (if needed)"

Rules:

• TaskUpdate each task to completed only after the dispatched skill finishes AND you update orchestration.json
• Do NOT declare the loop done until: (a) the review task is marked completed, AND (b) direction-assessment.json reports status: "pass"
• If review returns gaps: update re-dispatch and re-review tasks to in_progress, dispatch fixes, then re-review
• Before declaring done, read orchestration.json and verify completedDispatches count >= 8 producers + 1 passing review

1. /shipkit-why-project — establishes foundation (vision lives inside why.json)
2. /shipkit-stage — sets stage, constraints, business gates
3. /shipkit-product-discovery — informs product definition
4. /shipkit-product-definition — informs engineering definition
5. /shipkit-engineering-definition — informs goals and design system
6. /shipkit-design-system — scaffolds design direction + tokens (UI projects only; skip for CLI/API)
7. /shipkit-product-goals — defines product success
8. /shipkit-engineering-goals — defines technical success
9. /shipkit-review-direction — assesses coherence
10. If gaps found → re-dispatch specific producers → re-review