Dev Plan
Runs a development objective as a phased plan: each phase goes to a fresh haiku, sonnet or opus subagent, or inline, is gated by the tests of the code it touches and reviewed by the main conversation, with iterations only as correction rounds. The full suite runs once at the end, or is left to the repository's CI when it runs it. The plan is plain markdown plus git, no engine to install. Stack-agnostic. For multi-step work: a module, an integration, a migration, a refactor. Triggers: "/dev-plan", "build a plan for", "resume the plan", "monta un plan por fases", "retoma el plan", "en qué fase vamos", "cierra el plan". Not for scheduling, effort estimation or Gantt charts.