agentleFS
Sign inStart free
mick-gskmick-gsk/drift/.github/skills/subagent-driven-development/SKILL.md

subagent-driven-development

Skill14 starsChanged 7 months agoMITView on GitHub

Use when executing implementation plans with independent tasks in the current session. Dispatches fresh subagent per task with two-stage review (spec compliance, then code quality).

189 other projects use a version of this, 72 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use chinese-code-review, chinese-commit-conventions and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • Leodorareluctant259Skill

    chinese-code-review

    中文代码审查规范——在保持专业严谨的同时，用符合国内团队文化的方式给出有效反馈

    Also in 8 projects that use this

  • Leodorareluctant259Skill

    chinese-commit-conventions

    中文 Git 提交规范 — 适配国内团队的 commit message 规范和 changelog 自动化

    Also in 8 projects that use this

  • obraSkill

    diagnosing-superpowers

    Use when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.

    Also in 19 projects that use this

  • Tommy-ywSkill

    webhook-subscriptions

    Create and manage webhook subscriptions for event-driven agent activation, or for direct push notifications (zero LLM cost). Use when the user wants external services to trigger agent runs OR push notifications to chats.

    Also in 5 projects that use this

  • math-incSkill

    minecraft-modpack-server

    Set up a modded Minecraft server from a CurseForge/Modrinth server pack zip. Covers NeoForge/Forge install, Java version, JVM tuning, firewall, LAN config, backups, and launch scripts.

    Also in 5 projects that use this

  • math-incSkill

    pokemon-player

    Play Pokemon games autonomously via headless emulation. Starts a game server, reads structured game state from RAM, makes strategic decisions, and sends button inputs — all from the terminal.

    Also in 5 projects that use this

  • +3 more from Leodorareluctant259
  • +2 more from math-inc

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 3 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 179 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If spec issues found: implementer fixes → re-review

    line 30
  2. Distinctive:

    If quality issues found: implementer fixes → re-review

    line 32
  3. Distinctive:

    After all tasks: dispatch final code reviewer for entire implementation

    line 34
  4. Very specific:

    DONE_WITH_CONCERNS: Read concerns before proceeding.

    line 46

“Common” is measured: kept by at least 6 in 10 of the 179 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Subagent-Driven Development

Execute plan by dispatching fresh subagent per task, with two-stage review after each: spec compliance review first, then code quality review.

Core principle: Fresh subagent per task + two-stage review (spec then quality) = high quality, fast iteration

When to Use

  • You have an implementation plan (from writing-plans skill)
  • Tasks are mostly independent
  • You want to stay in this session

vs. Executing Plans: Same session, fresh context per task, faster iteration with no human-in-loop between tasks.

The Process

  1. Read plan once — extract all tasks with full text and context
  2. Create TodoWrite with all tasks
  3. Per task:
    • Dispatch implementer subagent with full task text + scene-setting context
    • Answer any questions before letting them proceed
    • Implementer implements, tests, commits, self-reviews
    • Dispatch spec compliance reviewer subagent
    • If spec issues found: implementer fixes → re-review
    • Dispatch code quality reviewer subagent
    • If quality issues found: implementer fixes → re-review
    • Mark task complete
  4. After all tasks: dispatch final code reviewer for entire implementation
  5. Use superpowers:finishing-a-development-branch

Model Selection

  • Mechanical tasks (isolated functions, clear specs, 1-2 files): cheap/fast model
  • Integration tasks (multi-file, pattern matching, debugging): standard model
  • Architecture/design/review: most capable model

Handling Implementer Status

  • DONE: Proceed to spec compliance review
  • DONE_WITH_CONCERNS: Read concerns before proceeding. Address correctness/scope concerns first.
  • NEEDS_CONTEXT: Provide missing context and re-dispatch
  • BLOCKED: Assess blocker — more context, more capable model, smaller task, or escalate to human

Never ignore an escalation or force the same model to retry without changes.

Prompt Templates

  • ./implementer-prompt.md — Dispatch implementer subagent
  • ./spec-reviewer-prompt.md — Dispatch spec compliance reviewer subagent
  • ./code-quality-reviewer-prompt.md — Dispatch code quality reviewer subagent

Red Flags

Never:

  • Skip reviews (spec compliance OR code quality)
  • Proceed with unfixed issues
  • Dispatch multiple implementation subagents in parallel (conflicts)
  • Make subagent read plan file (provide full text instead)
  • Skip scene-setting context
  • Accept "close enough" on spec compliance
  • Start code quality review before spec compliance is ✅
  • Move to next task while either review has open issues

Integration

Required workflow skills:

  • superpowers:writing-plans — Creates the plan this skill executes
  • superpowers:test-driven-development — Subagents follow TDD for each task
  • superpowers:finishing-a-development-branch — Complete development after all tasks

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free