subagent-driven-developmentlisted

# Subagent-driven development Use subagents when the task benefits from independent investigation, implementation, or review and the current provider supports them. Give each subagent a narrow objective, relevant context, boundaries, and expected output. Do not spawn agents for trivial work. Prefer fresh-context reviewers for meaningful changes. The parent agent remains responsible for integration, verification, and the final answer.