subagent-driven-development

You can execute an implementation plan by dispatching a fresh subagent for each task, allowing independent tasks to run in parallel. This approach preserves context and avoids cross-task leakage during plan execution.

Inline lead review is the process where the lead performs spec compliance and quality verification after each subagent completes its task. This Julie-first orientation ensures changes are reviewed and verified before proceeding to the next task.

Yes, subagent-driven development supports multiple harnesses including Claude Code, Codex, Cursor, OpenCode, Copilot CLI, and Gemini CLI. The workflow dispatches per-task subagents and enforces model routing across these supported environments.

To prevent context leakage, dispatch a fresh subagent for each implementation task rather than reusing the same worker. This ensures isolated context per task, while the lead performs inline review to maintain spec compliance across the plan.

Yes, the workflow relies on provided templates such as implementer-prompt.md and fix-prompt.md. These templates guide the per-task subagents and enforce model routing and verification scopes defined in the implementation plan.

The best way to speed up delivery is dispatching independent tasks in parallel across multiple subagents. This parallel dispatch mechanism allows simultaneous execution while the lead conducts inline review after each task completes.