agentleFS
Sign inStart free
metaspartanmetaspartan/cybara/skills/subagent-driven-development/SKILL.md

subagent-driven-development

Skill38 starsChanged 5 months agoMITView on GitHub

Execute implementation plans with isolated subagents plus spec and quality review passes.

189 other projects use a version of this.

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

9 rules. 0 are common, 9 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 179 edited versions we read keep these.

  • 9

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this for larger implementation plans where independent work can be delegated and reviewed before integration.

    line 9
  2. Distinctive:

    Do not use it for small single-file fixes.

    line 20
  3. Distinctive:

    Read the plan once and extract every task with full context.

    line 24
  4. Distinctive:

    Create a todo list with all task IDs.

    line 25
  5. Distinctive:

    After implementation, spawn or reuse a reviewer for spec compliance.

    line 28
  6. Distinctive:

    After all tasks, run a final integration review across the full diff.

    line 31
  7. Distinctive:

    Run the affected test suite and full project checks required by the repo.

    line 32
  8. Distinctive:

    Never make subagents infer missing requirements from the full plan.

    line 58
  9. Distinctive:

    Keep worktree ownership explicit.

    line 60

“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

Use this for larger implementation plans where independent work can be delegated and reviewed before integration.

This adapts the Hermes/OpenClaw subagent workflow to Cybara's sessions_spawn, sessions_send, sessions_history, session_status, todo, and kanban_* tools.

When To Use

  • The plan has multiple mostly independent tasks.
  • Fresh context per task reduces confusion.
  • You need an implementer plus a spec reviewer and quality reviewer.
  • The user explicitly asks for subagents or parallel implementation.

Do not use it for small single-file fixes; direct implementation is faster and clearer.

Workflow

  1. Read the plan once and extract every task with full context.
  2. Create a todo list with all task IDs.
  3. For each task:
    • Spawn an implementer session with the exact task, relevant files, constraints, and verification command.
    • After implementation, spawn or reuse a reviewer for spec compliance.
    • Then run a quality/security/test review.
    • Fix gaps and re-review before marking complete.
  4. After all tasks, run a final integration review across the full diff.
  5. Run the affected test suite and full project checks required by the repo.

Implementer Prompt Shape

Include:

  • Task text copied from the plan.
  • Files likely involved.
  • Project constraints such as package manager, test command, platform, and style.
  • Definition of done.
  • A request to avoid unrelated refactors and avoid committing unless instructed.

Reviewer Prompt Shape

Spec reviewer:

  • "Compare implementation to this exact task spec."
  • "Output PASS or specific gaps with file paths."

Quality reviewer:

  • "Check correctness, security, performance, tests, and maintainability."
  • "Output Critical, Important, Minor, and Verdict."

Rules

  • Never make subagents infer missing requirements from the full plan; pass the relevant task context directly.
  • Review receipts count only after both spec and quality review are complete.
  • Keep worktree ownership explicit. Do not let parallel agents edit the same files without coordination.
  • Final integration review is mandatory for cross-task behavior.

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