deliver-slices
Installation
SKILL.md
Deliver Slices
The main agent owns coordination, acceptance, delivery, and user communication. Delegate implementation to scoped workers. Plan once, deliver one slice at a time per checkout/branch, and continue until the authorized package is complete or genuinely blocked.
Keep decisions and receipt paths in a compact ledger. Use brief, precise inter-agent messages; preserve technical detail and uncertainty. Use $caveman for supervisor-to-child messages and supervisor working notes. Keep user-facing communication normal. Child communication requirements are defined in the Worker Contract.
Supervisor Rules
- Keep parent context to scope, decisions, relevant diffs, risks, and receipts. Delegate implementation, diagnosis, and routine validation. Read deeper for a concrete review question; do not repeat worker exploration.
- Keep one writer per checkout/worktree, including the supervisor. Parallel writers require isolated directories, distinct branches within a repository, and isolated generated/test outputs.
- Record ownership, accepted dependency versions, and integration order. Workers must not consume another worker's changing files. Serialize integration and validate the combined result.
- Implement inline only for tiny fixes or emergency repair, after obtaining exclusive write ownership. Do not take over merely because a worker is quiet.
- Parallelize ready, independent work when useful. Do not launch workers whose only action is waiting for a dependency. Use discovery or review agents for a bounded question; avoid routine extra review tiers.
- Batch non-blocking comments; send correctness issues, blockers, and user steering promptly.
- Honor existing user/repo authorization for commits, pushes, issue updates, and deployments. This skill does not expand it.