milestone-driven

Reconnaissance worker for `/milestone-breakdown`. Given a milestone description and a repo root, scouts the codebase for everything the orchestrator needs to decompose the milestone into tasks: relevant files, code conventions, test posture, data models / schemas, framework usage, and risks. Returns a structured report. Does NOT propose tasks — synthesis is the orchestrator's job. Read-only.

Implementation-cycle worker. Runs `task-implementation` followed by `commit` on a single PLAN.md task and exits with a parser-friendly report block. Used by `/implementation-cycle` to keep the orchestrator session lean — the full implementation transcript (file reads, test runs, iteration on errors) lives in this subagent and is discarded on return.

Drive PLAN.md to completion by running task-implementation + commit in a fresh subagent per task, sequentially.

Break down the next open milestone from ROADMAP.md into small, actionable, independently testable tasks in PLAN.md. Trigger whenever the user says "break down", "plan tasks", "create tasks", "task breakdown", "decompose milestone", "phase 2", "let's break this down", references PLAN.md in a planning context, or asks to prepare for implementation. Also trigger when the user has just finished strategic planning and wants to move to the next phase. This skill reads the codebase and docs to produce implementation-aware tasks with architectural hints, test cases, and file associations.

Close out a completed milestone by documenting results, noting discrepancies, adding manual testing/demo steps, and preparing PLAN.md for the next cycle. Trigger whenever the user says "close milestone", "milestone done", "wrap up", "close it out", "phase 4", "finish the milestone", "we're done", or when all tasks in PLAN.md are marked complete and the user wants to finalize. Also trigger when the user asks to document what was built, write demo steps, or prepare for the next planning cycle.

Facilitate project inception for new software projects by discovering the project's vision, goals, and planned feature set through Socratic dialogue, then producing a concise README.md and a CLAUDE.md with project-specific instructions for AI-assisted development. This skill precedes the four-phase milestone-driven workflow — use it once at the very beginning to establish the project's identity before strategic planning begins.

Facilitate strategic planning for AI-native software projects by adding new milestones to ROADMAP.md through Socratic dialogue. Trigger whenever the user mentions adding a milestone, starting a new feature, planning a new capability, discussing project direction, or says things like "let's plan", "new milestone", "next feature", "I want to build", "add to the roadmap", or references ROADMAP.md. Also trigger when the user starts describing a high-level goal or user-facing feature they want to pursue next. This skill is the entry point of a four-phase milestone-driven workflow — use it for the strategic/planning phase, not for breaking down tasks or implementing code.