subagent-driven-development

Topics in the source

• Subagent-Driven Development

Choose delegation by total effort: briefing, implementation, rediscovery, integration, and rework. The parent may implement or fix code directly. Do not require a particular implementation model or forbid the parent model from writing code. Select available models for task difficulty and use the runtime's actual tool contract. Delegate only work with clear ownership, interfaces, acceptance criteria, and useful independence. Parallel tasks must not edit the same files or depend on unfinished shared state. Give each worker concise requirements, relevant source paths, the workspace, constraints, and expected verification; do not ask it to transcribe a complete implementation from a plan. Use implementer-prompt.md as an optional brief template. The controller integrates results, resolves dependencies, and can handle a small fix itself. Workers report evidence and uncertainties; they do not launch extra reviewers. Maintain a concise progress record only when it aids resumption, using existing runtime records where available. Run appropriate tests while implementing. After integration, use the project's independent quality-check and its review budget. There is no mandatory task-by-task r

This is an excerpt. Refer to the complete source and its current requirements.