subagent-driven-development

Automate development by creating isolated subagents for each task with two-phase review.

Updated Jun 9, 2026

Search Tags:#code quality #subagent #development automation #specification compliance #two-phase review

Ready to run

npx skills add https://github.com/NQC233/sjtuMedMasterSpider --skill subagent-driven-development-nqc233

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: subagent-driven-development
Source: https://github.com/NQC233/sjtuMedMasterSpider/tree/main/.claude/subagent-driven-development
Command: npx skills add https://github.com/NQC233/sjtuMedMasterSpider --skill subagent-driven-development-nqc233

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates development workflows by dividing tasks into subagents, ensuring high-quality, quick iterations with minimal manual intervention.

Core Features & Use Cases

Subagent Automation: Distribute tasks to isolated subagents for execution, each with its own context.
Two-Phase Review: Ensures code meets specifications and adheres to quality standards.
Use Case: Use this Skill when executing plans for tasks with clear, independent specifications to streamline the development process.

Quick Start

Run the subagent-driven-development skill with the command: 'use subagent-driven-development'

Frequently Asked Questions about subagent-driven-development

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

FAQPage Schema

How do I automate development workflows to ensure code quality and specification compliance?▼

Development automation divides tasks into isolated subagents for execution, ensuring code meets specifications and quality standards. It uses a two-phase review to verify adherence without context leakage, minimizing manual intervention for high-quality iterations.

What is a two-phase review in subagent-driven development?▼

A two-phase review verifies that code generated by isolated subagents meets specifications and adheres to quality standards. It checks specification compliance and code quality sequentially, ensuring the automated development output aligns with the original plan.

How do I prevent context leakage when automating independent development tasks?▼

Prevent context leakage by distributing tasks to isolated subagents, each operating with its own independent context. This ensures specification compliance and code quality without cross-task interference during the automated development workflow.

When should I use subagent-driven development automation for my project?▼

Use subagent-driven development automation when executing plans for tasks with clear, independent specifications. It is ideal for scenarios requiring strict specification compliance, code quality, and quick iterations with minimal manual intervention.

Does subagent-driven development work for tasks with overlapping or unclear specifications?▼

Subagent-driven development is designed for tasks with clear, independent specifications. It may not be suitable for tasks with overlapping dependencies or unclear requirements, as isolated subagents require distinct contexts to ensure specification compliance.

How do I get started with subagent-driven development automation?▼

Start subagent-driven development automation by running the skill command, which creates subagents for each task. The subagents execute the development plan, undergo a two-phase review, and ensure specification compliance automatically.