subagent-driven-development

Automating implementation plan execution involves breaking the plan into discrete tasks and dispatching independent subagents to handle each one. This Skill manages the workflow from task implementation to final code review automatically.

Two-stage code review in subagent-driven development ensures spec compliance and code quality through automated checks. Dedicated spec reviewers and code quality reviewers evaluate the implementation before moving to the next task.

Yes, you can use subagents to manage task decomposition within a single session. This approach preserves context and enables iterative refinement through automated subagent interactions throughout the development cycle.

Yes, a detailed implementation plan is required before starting automated development. The Skill executes tasks based on the provided plan document, such as a markdown file located in your project's docs directory.

The best way to ensure spec compliance during automated code implementation is to dispatch specialized subagents for two-stage reviews. This process checks both specification adherence and code quality before progressing.

Context preservation matters in subagent-driven development because it maintains session continuity across multiple task executions. This ensures iterative refinement and efficient development cycles without losing prior implementation state.