dx-swe-subagent-dev

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

3|5|Updated Jan 21, 2025
One-click install
npx skills add https://github.com/DEEPX-AI/dx_stream --skill dx-swe-subagent-dev-deepx-ai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dx-swe-subagent-dev
Source: https://github.com/DEEPX-AI/dx_stream/tree/main/.deepx/skills/dx-swe-subagent-dev
Command: npx skills add https://github.com/DEEPX-AI/dx_stream --skill dx-swe-subagent-dev-deepx-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Executing a multi-task implementation plan in a single AI session often leads to context pollution, skipped reviews, and inconsistent quality. This Skill orchestrates plan execution by dispatching a fresh subagent for each task and enforcing a two-stage review (spec compliance, then code quality) after every task. ## Core Features & Use Cases - Subagent-per-task execution: Each task runs in an isolated subagent context with curated instructions, preventing context pollution and keeping the controller focused on coordination. - Two-stage review gates: A spec compliance reviewer verifies the code matches requirements exactly, then a code quality reviewer checks maintainability, with fix-and-re-review loops until approval. - Status handling and escalation: Implementer subagents report DONE, DONE_WITH_CONCERNS, NEEDS_CONTEXT, or BLOCKED, and the controller responds with re-dispatch, model upgrades, task splitting, or human escalation. - Use Case: Given a written implementation plan with five independent tasks, use this Skill to execute each task via implementer subagents, run spec and quality reviews after each, and finish with a final whole-implementation code review. ## Quick Start Use the dx-swe-subagent-dev skill to execute the implementation plan at docs/plans/feature-plan.md task by task with subagent reviews.

Frequently Asked Questions about dx-swe-subagent-dev

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

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

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

What is the difference between subagent-driven development and executing plans in a parallel session?▼

Subagent-driven development stays in the same session with no context switch, using fresh subagents per task and automatic review checkpoints for faster iteration. Executing plans in a parallel session involves a handoff and human-in-the-loop between tasks.

When should I not use subagent-driven development?▼

Avoid it when there is no implementation plan yet, when tasks are tightly coupled and cannot run independently, or when you need a parallel session instead of same-session execution. In those cases, brainstorm or write a plan first, or use an executing-plans workflow.

How do I handle a blocked or failing implementer subagent?▼

Check the reported status: for NEEDS_CONTEXT provide the missing information and re-dispatch; for BLOCKED, add context, switch to a more capable model, split the task into smaller pieces, or escalate to the human if the plan itself is wrong. Never force the same model to retry unchanged.

Why must spec compliance review come before code quality review?▼

Spec compliance confirms the implementer built exactly what was requested, nothing missing and nothing extra. Reviewing code quality before correctness wastes effort polishing code that may need rework to meet the specification.