subagent-driven-development

Executes implementation plans by dispatching fresh subagents per task with two-stage review.

Updated Apr 18, 2026
One-click install
npx skills add https://github.com/azaanaliraza/operarius --skill subagent-driven-development-azaanaliraza
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: subagent-driven-development
Source: https://github.com/azaanaliraza/operarius/tree/main/src-tauri/bin/hermes/skills/software-development/subagent-driven-development
Command: npx skills add https://github.com/azaanaliraza/operarius --skill subagent-driven-development-azaanaliraza

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Executing a multi-task implementation plan in a single session leads to context pollution, inconsistent quality, and missed spec requirements. This Skill orchestrates plan execution by delegating each task to a fresh subagent and enforcing systematic review between tasks. ## Core Features & Use Cases - Per-Task Subagent Dispatch: Each plan task runs in a fresh delegate_task context with full task text and project context provided directly, avoiding accumulated state confusion. - Two-Stage Review Pipeline: Every task passes a spec compliance review first, then a code quality review, with fix-and-re-review loops until approved. - Final Integration Review: After all tasks complete, a reviewer checks cross-task consistency, runs the full test suite, and confirms merge readiness. - Use Case: Given a plan file like docs/plans/auth-feature.md with five tasks (User model, password hashing, login endpoint, JWT generation, registration endpoint), the Skill dispatches implementer and reviewer subagents per task, tracks progress in a todo list, and delivers tested, reviewed code. ## Quick Start Execute the implementation plan in docs/plans/feature-plan.md by dispatching a fresh subagent for each task with spec and quality reviews between tasks.

Frequently Asked Questions about subagent-driven-development

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I execute an implementation plan with subagents?▼

Read the plan file once, extract all tasks into a todo list, then dispatch a fresh implementer subagent per task with the full task text in context. Follow each implementation with a spec compliance review and a code quality review before marking the task complete.

What is the correct order for spec review and code quality review?▼

Spec compliance review always runs first, verifying the implementation matches the original task requirements with no scope creep. Code quality review runs only after spec compliance passes, checking conventions, error handling, test coverage, and security.

How big should each task be when delegating to subagents?▼

Each task should represent 2-5 minutes of focused work, such as creating a single model or adding one endpoint. Large tasks like 'implement authentication system' should be split into discrete units like password hashing, JWT generation, and login endpoint.

What happens when a reviewer subagent finds issues?▼

The implementer subagent (or a new fix subagent) addresses the issues, then the reviewer re-reviews the changes. This loop repeats until approval, and you never proceed to the next task with open critical or important issues.

When should I not use subagent-driven development?▼

Avoid it when tasks are tightly coupled and touch the same files, since parallel or sequential fresh-context subagents cannot coordinate shared state well. It also requires an existing implementation plan, so write the plan first using a planning skill.