Delegated Delivery
Use a layered execution model:
- main PM owns scope, sequencing, and final acceptance
- sub-PM owns one ticket end to end
- implementation worker makes the scoped change
- reviewer looks for real risk
- bounded maintainability pass checks for high-value simplification before closeout
- main PM accepts or sends the ticket back
references/SOP.md is the canonical operating model. Read it when you are actually running a ticket through this workflow.
Use this workflow only when the user clearly wants delegated or agent-based delivery, a worker/reviewer loop, independent review, or ticket ownership. Do not infer delegation from a generic request to finish or close out work.
Dispatch prompts should be free-form, not forced into templates. Preserve the ticket contract in whatever shape fits the work: problem, invariants, scope, non-goals, source-of-truth order, acceptance criteria, validation, and escalation triggers.
Workflow
- Decide whether the ticket is ready to delegate.
- Assign one sub-PM as the ticket owner.
- Have the sub-PM read the directly relevant current truth and restate the ticket.
- Default to one worker and one reviewer unless the ticket shape clearly warrants otherwise.
- Give the worker the ticket packet and let them take the first pass.
- Give the reviewer the ticket contract, handoff, and changed files or diff.
- Have the sub-PM triage review findings and loop fixes as needed.
- Run a bounded maintainability pass and accept only simplifications that clearly reduce complexity or risk.
- Have the sub-PM run final validation and prepare the outcome packet.
- Have the main PM accept or send the ticket back.
When spawning subagents, pass ticket-local context plus the directly relevant sources of truth. Do not preload unrelated tickets or broad program context.