Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add tranhieutt/software_development_department --skill subagent-driven-developmentgit clone --depth 1 https://github.com/tranhieutt/software_development_departmentWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/tranhieutt/software_development_department/subagent-driven-development)<a href="https://agentmods.dev/skills/tranhieutt/software_development_department/subagent-driven-development"><img src="https://agentmods.dev/badge/skills/tranhieutt/software_development_department/subagent-driven-development/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/tranhieutt/software_development_department/subagent-driven-development"><img src="https://agentmods.dev/badge/skills/tranhieutt/software_development_department/subagent-driven-development.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00055 | $0.02063 |
| Opus 5 | $0.00028 | $0.01032 |
| Sonnet 5 | $0.00011 | $0.00413 |
| Haiku 4.5 | $0.00006 | $0.00206 |
Grade A, and why
subagent-driven-development scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 302 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Subagent-Driven Development
Purpose
Execute an approved implementation plan by dispatching one fresh implementer subagent per task, then running two review gates before moving to the next task:
- Spec compliance review: did the task implement exactly the plan?
- Code quality review: is the implementation maintainable, tested, and safe?
The controller does not implement code directly. The controller curates context, dispatches focused subagents, verifies outputs, and blocks progression when a review gate fails.
Position in SDD
Use this workflow after:
spec-driven-development -> planning-and-task-breakdown -> user approval
Use it instead of:
test-driven-developmentinline when the plan has multiple tasks and review checkpoints would reduce riskorchestratewhen the work does not need multiple specialist domain wavesfork-joinwhen tasks are not safe to run in parallel or share files
Preconditions
All must be true:
- A concrete implementation plan exists.
- The user explicitly approved executing the plan.
- Tasks list exact files, acceptance criteria, and verification commands.
- The current branch/worktree is appropriate for implementation.
- Existing unrelated worktree changes are understood and will not be overwritten.
If any precondition is missing, stop and route back to
planning-and-task-breakdown, using-sdd, or the user.
Before the first implementation subagent, state:
Pre-code gate: Plan satisfied by user approval; execution mode: subagent-driven-development; Task 1 owner: fresh implementer subagent.
When Not to Use
- Single tiny task: use inline
test-driven-development. - Multiple independent branches: use
fork-join. - Cross-domain specialist sequencing: use
orchestrate. - Vague requirements: use
deep-intervieworspec-driven-development. - Missing tests or verification strategy: update the plan first.
Controller Workflow
1. Load the Plan Once
Read the approved plan once. Extract:
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 9d ago First seen · 302 lines · 55 tokens per session scan A da68bbac2782
subagent-driven-development is a skill published in the GitHub repository tranhieutt/software_development_department (72 stars, last pushed 4mo ago), licensed MIT. It adds 55 tokens to every session and 2,063 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
playwright-cli
Automates browser interactions for testing and validating your own web applications using playwright-cli. Use when you need terminal-first browser control for navigation, form filling, screenshots, tracing, bound browser sessions, debugging, or generating Playwright test code. Only use against applications you own or…
flutter-ui
Build Flutter UI from Figma MCP or image input. Scans src for design tokens (colors, sizes, text styles), existing components, and naming conventions before writing a single line of code. Never hard-codes values.
serena
Serena code intelligence — LSP-powered symbol navigation, diagnostics, and targeted code surgery. Activate before complex refactors, cross-file analysis, or when graph tools need symbol-level depth.
database-migrations
Database migration best practices for schema changes, data migrations, rollbacks, and zero-downtime deployments across PostgreSQL, MySQL, and common ORMs (Prisma, Drizzle, Kysely, Django, TypeORM, golang-migrate).
scan
Scan project once per session. Run first — all other skills depend on this.
tdd
Strict test-driven development for behavior changes. Requires verified RED before production code, minimal GREEN, and refactor only after passing tests.