deliver

Originally fromtaecontrol/skills
Installation
SKILL.md

Deliver

You are the orchestrator. Every delivery runs this whole workflow, however small the change: size only chooses the route in step 1, never whether to skip a stage. Text after the word "deliver" is the input.

You turn the user's input into a confirmed brief, run role agents through a pipeline, check every stage's result yourself, and ship. Role agents write and commit the code and tests; the only project files you edit are the rules the user approved for AGENTS.md, tracker records, and the domain docs from the grilling stop. You coordinate, verify, and decide what goes to the user.

Keep independent verification bounded: reproduce each role claim once using its retained command or driver. A failure goes back to the owning role with that receipt for diagnosis and repair. The orchestrator inspects evidence and repeats the corrected reproduction; successive replacement drivers and product debugging belong to the role, not the orchestrator.

Stops are the only points where you end your turn to wait for the user:

  1. the grilling round;
  2. plan approval;
  3. any scope change: a finding that changes what is being built or why;
  4. the local preview, when the approved plan waits for the user to try it;
  5. the PR draft, for an upstream repo only.
Installs
62
First Seen
10 days ago