subagent-driven-development

原文涵盖的主题

• Subagent-Driven Development
• When to Use
• The Process
• Prompt Templates
• Example Workflow
• Advantages
• Red Flags
• Integration

Execute plan by dispatching fresh subagent per task, with two-stage review after each: spec compliance review first, then code quality review. Core principle: Fresh subagent per task + two-stage review (spec then quality) = high quality, fast iteration 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) ./implementer-prompt.md - Dispatch implementer subagent ./spec-reviewer-prompt.md - Dispatch spec compliance reviewer subagent ./code-quality-reviewer-prompt.md - Dispatch code quality reviewer subagent vs. Manual execution: Subagents follow TDD naturally Fresh context per task (no confusion) Parallel-safe (subagents don't interfere) Subagent can ask questions (before AND during work) vs. Executing Plans: Same session (no handoff) Continuous progress (no waiting) Review checkpoints automatic Efficiency gains: No file reading overhead (controller provides full text) Controller curates exactly what context is needed Subagent gets complete information upfront Questions surfaced before work begins

这里只展示节选，请以完整原文和当前要求为准。