← ClaudeAtlas

supervised-devlisted

Use to run a ticket end-to-end through the supervised delivery pipeline: tester writes failing tests, implementer fixes production code, reviewer inspects the diff, simplifier finds over-built surface, supervisor gives a single combined verdict. Invoked by the supervisor when the user provides a ticket.
alyahmedaly/supervised-dev · ★ 0 · Code & Development · score 72
Install: claude install-skill alyahmedaly/supervised-dev
# Supervised Delivery Run one ticket through the full pipeline. Serial execution, one worktree. No parallel writers. ## When this pipeline is the wrong tool Four subagents cost four system prompts, four tool schemas, four handoffs, and four reviews before any code changes. That fixed prefix only repays itself on work with real correctness risk and enough substance to amortise it. Downshift to the first row that covers the work: | Work | Run it as | | --------------------------------------------------- | -------------------------------------------- | | One-line fix, typo, mechanical rename, comment | Yourself, plus the one relevant check | | Bounded change, one or two files, obvious oracle | Yourself, plus one reviewer pass on the diff | | Copy-and-wrap or move-and-rewire: oracle is diff vs source plus existing suite | Light loop — see "Light loop" below | | Real feature or refactor, non-obvious failure modes | Full pipeline below | | Repo-wide sweep of N near-identical units | Full pipeline, batched — see Phase 3 | The rows have moved down over time. Current models finish multi-file features end to end without leaving stubs when handed the complete specification up front, so work that once needed the pipeline to avoid half-done output now sits a row lower — the pipeline buys independent judgement on a diff, not completion. Escalatin