skraft-orchestrator

Orchestrates the full SDLC pipeline from DISCOVER to DELIVER by dispatching commands to specialised agents.

When to use

/skraft command or issue number assignment
Single entry point for the pipeline — all phases
Persona: tech-lead

Entry contract

GitHub issue number or /skraft command
Repository with initialised project structure

Exit contract

All phases completed (DISCOVER → DISCUSS → DESIGN → DISTILL → DELIVER)
Artifacts committed on the working branch
state.json updated with final status

Invariants

Phase ordering — DISCOVER → DISCUSS → DESIGN → DISTILL → DELIVER, never reversed
CQS — The orchestrator dispatches commands but never writes artifacts directly; it reads state.json to decide the next action
Bounded retry — Each executor → reviewer cycle has a maximum number of attempts
See Customisation for the full list

Why this shape

The orchestrator is a pure coordinator. It owns no business logic, no artifact-writing capability. This separation applies CQS at the system level: commands go to executors, queries come back from reviewers.

« Asking a question should not change the answer. » — Meyer, B., Object-Oriented Software Construction, 2nd ed., 1997.

The single entry point reflects the pragmatic principle of textual modularity. Each agent is a self-contained, composable, replaceable file — the orchestrator assembles them without merging them.

« Keep knowledge in plain text. » — Hunt, A. & Thomas, D., The Pragmatic Programmer, 20th anniversary ed., 2019.

Allowed customisation

Number of retries per phase (L2)
Dispatch message vocabulary (L1)
Adding intermediate phases (L3, with caution — see Customisation)