subagent-driven-development
Use when executing implementation plans with independent tasks in the current session
Skill by nocksock
Chalk Labs
Need help deploying subagent-driven-development?
Chalk Labs sets up agents like this inside real teams: connected to your tools, tested on your data, with a human in the loop where it matters.
Install
Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.
npx agentmarket install skill/nocksock-subagent-driven-development
Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.
Get the weekly diff
The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.
About
Use cases: agent-building
Reviews
Write a reviewNo reviews yet. Installed it? Reviews come from verified installers only. How reviews work
Permissions: not checked yet.
What's inside
- Skill name
subagent-driven-development- Description
- Use when executing implementation plans with independent tasks in the current session
- License
- MIT
- Instructions
- 312 lines in SKILL.md · view on GitHub
Before installing
- Instructions read files in your home folder (~/.ssh, ~/.aws…)
Files (4)
- SKILL.md
- code-quality-reviewer-prompt.md
- implementer-prompt.md
- spec-reviewer-prompt.md
SKILL.md (first lines)
# 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.
**Why subagents:** You delegate tasks to specialized agents with isolated context. By precisely crafting their instructions and context, you ensure they stay focused and succeed at their task. They should never inherit your session's context or history — you construct exactly what they need. This also preserves your own context for coordination work.
**Core principle:** Fresh subagent per task + two-stage review (spec then quality) = high quality, fast iteration
## When to Use
```dot
digraph when_to_use {
"Have implementation plan?" [shape=diamond];
"Tasks mostly independent?" [shape=diamond];
"Stay in this session?" [shape=diamond];
"subagent-driven-development" [shape=box];
"executing-plans" [shape=box];
"Manual execution or brainstorm first" [shape=box];
"Have implementation plan?" -> "Tasks mostly independent?" [label="yes"];
"Have implementation plan?" -> "Manual execution or brainstorm first" [label="no"];
"Tasks mostly independent?" -> "Stay in this session?" [label="yes"];
"Tasks mostly independent?" -> "Manual execution or brainstorm first" [label="no - tightly coupled"];
"Stay in this session?" -> "subagent-driven-development" [label="yes"];
"Stay in this session?" -> "executing-plans" [label="no - parallel session"];
}
```
**vs. Executing Plans (parallel session):**
- Same session (no context switch)
- Fresh subagent per task (no context pollution)
- Two-stage review after each task: spec compliance first, then code quality
- Faster iteration (no human-in-loop between tasks)
## Session Preferences (Check First)
**Before starting, check if session preferences were already set** (e.g., by deep-work-session).
### Commit Preference
**If already set:** Use that preference. Don't ask again.
**If not set, use the question tool to ask:**
> "Should subagents commit after each task?"
> Options: Yes, No
**If No (or previously set to No):**
- Pass `COMMIT_PREFERENCE: no` to all subagents
- Subagents MUST NOT commit
- This applies for the **entire session**, including any future skill invocations
- Only override if user **explicitly gives permission** later
**If Yes (or user doesn't specify):**
- Pass `COMMIT_PREFERENCE: yes` to all subagents
- Subagents commit after successful implementation (using superpowers:making-commits for format)
### Question Style
**If question style is set (e.g., `front-loaded` or `minimal`):**
- Pass `QUESTION_STYLE: [value]` to all subagents
- Subagents should only ask the controller questions if genuinely blocked
- Controller should only ask user questions if genuinely blocked
- Do NOT ask for permission between tasks - proceed autonomously
**If question style is `checkpoint` or `collaborative`:**
- Subagents may ask clarifying questions more freely
- Controller may check in with user between tasks if helpful
**If not set:** Default to proceeding without unnecessary check-ins (this skill is designed for autonomous execution)
## The Process
```dot
digraph process {
rankdir=TB;
subgraph cluster_per_task {
label="Per Task";
"Dispatch implementer subagent (./implementer-prompt.md)" [shape=box];
"Implementer subagent asks questions?" [shape=diamond];
"Answer questions, provide context" [shape=box];
"Implementer subagent implements, tests, (commits if allowed), self-reviews" [shape=box];
"Dispatch spec reviewer subagent (./spec-reviewer-prompt.md)" [shape=box];
"Spec reviewer subagent confirms code matches spec?" [shape=diamond];
"Implementer subagent fixes spec gaps" [shape=box];
"Dispatch code quality reviewer subagent (./code-quality-reviewer-prompt.md)" [shape=box];
"Code quality reviewer subagent approves?" [shape=diamond];
"Implementer subagent fixes quality issues" [shape=box];
"Mark task complete in TodoWrite" [shape=box];
}
"Read plan, extract all tasks with full text, note context, create TodoWrite" [shape=box];
"More tasks remain?" [shape=diamond];
"Dispatch final code reviewer subagent for entire implementation" [shape=box];
"Use superpowers:finishing-a-development-branch" [shape=box style=filled fillcolor=lightgreen];
"Read plan, extract all tasks with full text, note context, create TodoWrite" -> "Dispatch implementer subagent (./implementer-prompt.md)";
"Dispatch implementer subagent (./implementer-prompt.md)" -> "Implementer subagent asks questions?";
"Implementer subagent asks questions?" -> "Answer questions, provide context" [label="yes"];
"Answer questions, provide context" -> "Dispatch implementer subagent (./implementer-prompt.md)";
"Implementer subagent asks questions?" -> "Implementer subagent implements, tests, (commits if allowed), self-reviews" [label="no"];
"Implementer subagent implements, tests, (commits if allowed), self-reviews" -> "Dispatch spec reviewer subagent (./spec-reviewer-prompt.md)";
"Dispatch spec reviewer subagent (./spec-reviewer-prompt.md)" -> "Spec reviewer subagent confirms code matches spec?";
"Spec reviewer subagent confirms code matches spec?" -> "Implementer subagent fixes spec gaps" [label="no"];
"Implementer subagent fixes spec gaps" -> "Dispatch spec reviewer subagent (./spec-reviewer-prompt.md)" [label="re-review"];
"Spec reviewer subagent confirms code matches spec?" -> "Dispatch code quality reviewer subagent (./code-quality-reviewer-prompt.md)" [label="yes"];
"Dispatch code quality reviewer subagent (./code-quality-reviewer-prompt.md)" -> "Code quality reviewer subagent approves?";
"Code quality reviewer subagent approves?" -> "Implementer subagent fixes quality issues" [label="no"];
"Implementer subagent fixes quality issues" -> "Dispatch code quality reviewer subagent (./code-quality-reviewer-prompt.md)" [label="re-review"];
"Code quality reviewer subagent approves?" -> "Mark task complete in TodoWrite" [label="yes"];
"Mark task complete in TodoWrite" -> "More tasks remain?";
"More tasks remain?" -> "Dispatch implementer subagent (./implementer-prompt.md)" [label="yes"];
"More tasks remain?" -> "Dispatch final code reviewer subagent for entire implementation" [label="no"];
"Dispatch final code reviewer subagent for entire implementation" -> "Use superpowers:finishing-a-development-branch";
}
```
## Model SelectionFrom nocksock/superpowers, MIT.
More from nocksock/superpowers
- 0.432score
holistic-view
nocksock
Use this when given larger tasks, before starting the implementation, or during code reviews.
SkillDFreshness: D★ 1Claude Code +9 - 0.432score
jotai-atom-architecture
nocksock
Use when designing Jotai state architecture, setting up atom composition patterns, managing large objects, or debugging re-render issues - ensures proper atom…
SkillDFreshness: D★ 1Claude Code +9 - 0.432score
making-commits
nocksock
Use when ready to commit code changes.
SkillDFreshness: D★ 1Claude Code +9 - 0.432score
deep-work-session
nocksock
Use when user explicitly mentions 'deep work' or signals substantial work ('let's build/implement X').
SkillDFreshness: D★ 1Claude Code +9 - 0.432score
r3f-performance-optimization
nocksock
Use when optimizing React Three Fiber scenes, experiencing frame drops, high draw calls, or implementing 3D performance features - ensures systematic…
SkillDFreshness: D★ 1Claude Code +9 - 0.432score
session-handoff
nocksock
Use when approaching context limits (75-85%) to write comprehensive handoff documents for session continuity.
SkillDFreshness: D★ 1Claude Code +9 - 0.432score
component-authoring
nocksock
Use this when writing any kind of UI components in any language (heex, react, web components, and so on).
SkillDFreshness: D★ 1Claude Code +9 - 0.431score
code-cleanup
nocksock
Use when asked to clean up code, or after introducing a new larger feature.
SkillDFreshness: D★ 1Claude Code +9 - 0.423score
prioritise-todos
nocksock
Use this to rate and prioritise todos
SkillDFreshness: D★ 1Claude Code +9 - 0.423score
elixir-code
nocksock
ALWAYS use this skill, whenever you touch elixir code
SkillDFreshness: D★ 1Claude Code +9 - 0.423score
find-code-todos
nocksock
Use this to find todos in the source code
SkillDFreshness: D★ 1Claude Code +9 - 0.409score
brainstorming
nocksock
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior.
SkillDFreshness: D★ 1Claude Code +9
Signals
- Stars
- 1
- Forks
- 0
- Open issues
- 0
- Last commit (this folder)
- Mar 18, 2026 (7 months ago)
From GitHub (fetched Oct 24, 2026).
Details
- License
- MIT
- Repository
- github.com/nocksock/superpowers
- First seen
- Oct 24, 2026
- Last checked
- Oct 24, 2026
- Source
- GitHubgithub-graphql
More from nocksock
- 0.432score
making-commits
nocksock
Use when ready to commit code changes.
SkillDFreshness: D★ 1Claude Code +9 - 0.432score
jotai-atom-architecture
nocksock
Use when designing Jotai state architecture, setting up atom composition patterns, managing large objects, or debugging re-render issues - ensures proper atom…
SkillDFreshness: D★ 1Claude Code +9 - 0.432score
deep-work-session
nocksock
Use when user explicitly mentions 'deep work' or signals substantial work ('let's build/implement X').
SkillDFreshness: D★ 1Claude Code +9 - 0.432score
holistic-view
nocksock
Use this when given larger tasks, before starting the implementation, or during code reviews.
SkillDFreshness: D★ 1Claude Code +9 - 0.432score
component-authoring
nocksock
Use this when writing any kind of UI components in any language (heex, react, web components, and so on).
SkillDFreshness: D★ 1Claude Code +9 - 0.432score
r3f-performance-optimization
nocksock
Use when optimizing React Three Fiber scenes, experiencing frame drops, high draw calls, or implementing 3D performance features - ensures systematic…
SkillDFreshness: D★ 1Claude Code +9
Done for you
Rather not set it up yourself?
Chalk Labs scopes, builds and runs agents for your team: the task audit, the eval harness, the integrations and the weekly ops report. Fixed scope, priced before we start.
See how we build AI agents →Read the case studies
Chalk Labs is a two-founder AI and growth studio. We build AI agents, CRMs and MVPs for Web3 and AI companies, and have shipped 50+ product and token launches.
- launches shipped
- 50+
- launches shipped
- media placements
- 500+
- media placements
- founders on every account
- 2
- founders on every account
Press we've placed: Forbes · CoinDesk · Decrypt · Cointelegraph · The Block
Rahil Jain, Co-founder, Chalk Labs. Ex-Goldman Sachs engineer. You talk to the person who builds it.
Get subagent-driven-development running in your business
Tell us what you want to automate. A founder replies within one working day with a plan, not a pitch deck.
Cite this page
subagent-driven-development skill. Agent Mart. https://agentmart.dev/skills/nocksock-subagent-driven-development (last updated 2026-10-24)