subagent-driven-development
Subagent-Driven Development
Use this skill after the plan is written and approved. Keep the controller session as the manager: detect the harness, extract tasks, route models, decide what to delegate, keep context narrow, review the work, verify outcomes, and close agents that are no longer needed.
Use When
- The plan already exists and is approved.
- Most tasks are bounded and can be owned by one worker at a time.
- The controller can keep integration, review, and final verification centralized.
Workflow
- Confirm the plan is approved and the workspace is safe to edit.
- Capture a routing profile before dispatching work:
- harness name or family
- whether fresh workers can be spawned
- how fresh workers are spawned, such as host subagents, task tools, external CLIs, or inline fallback
- whether model or reasoning can be set per worker
- whether browser sessions can be isolated
More from mylesmcook/mcook-skills
adversarial-review
Use this skill when you need a serious code review, diff review, or implementation-plan review from independent reviewers. In Codex hosts, prefer a fresh Codex subagent for the Codex reviewer; otherwise use the Codex, Claude Code, and Gemini reviewer paths when available. Return a PASS, CONTESTED, or REJECT verdict.
13brainerd
>
10git-it-out
Use this skill when the user explicitly wants final end-of-session closeout and no more branch or PR limbo: proper verification, proper commits, main/mainline landing, push, repo-native merge/release/deploy/publish steps, tracker updates, Entire/checkpoint handling when configured, and a concise handoff. Reach for it on prompts like 'git it out', 'get it out', 'ship this', 'I'm done', 'I'm going to bed', 'take this off my plate', 'finish the session', or 'get this into production'. Do not use it for greenfield implementation, open-ended debugging, broad refactors, or inventing a release process from scratch.
8simple-code
Reduce incidental complexity in code and design. Use when shaping APIs, module boundaries, refactors, tests, naming, and architecture tradeoffs with a bias toward concrete, local, reversible solutions.
7laws-of-taste
>-
6simplify
Refine recently changed code for clarity, consistency, and maintainability without changing behavior. Use when the user explicitly asks to simplify, clean up, or lightly refactor touched code, reduce local complexity, remove redundancy, improve naming or structure, or make recent edits easier to read while preserving outputs, interfaces, tests, security, and accessibility.
6