Gestión de Proyectos
Next Milestone — Feature → Plan → Implement → Verify → Commit
Drive a feature request through the milestone discipline — read the project's milestones.md (or plan.md), decide the milestone size and number, write the plan paragraph in canonical sort position, ask the user to approve, dispatch an implementer sub-agent, dispatch a verifier sub-agent to check the result, and auto-commit on success. Use this skill whenever the user wants to add a new feature, fix, refactor, or behavior change to a project that uses milestones.md or plan.md with numbered milestones, including phrases like "let's add X", "new milestone for Y", "next milestone", "implement Z", "M9.x for ...", "/next-milestone", or any non-trivial feature request in a project where milestones.md exists. Prefer this skill over implementing features ad-hoc whenever the project has milestone-numbered history (M0, M1.5, M8.2, etc.) — the discipline keeps the plan and the code in lockstep, and the verifier sub-agent catches out-of-scope drift before it gets committed.