milestone-driven

Plugin milestone-driven from marketplace mtrense-skills in mtrense/skills. Commands read from the repo's manifest — today.

Skills (7)

• implementation-cycle-workflow

  Workflow-backed twin of /implementation-cycle. Drives PLAN.md to completion by invoking the `implementation-cycle` Workflow script (one task-worker + doc-updater subagent per task, sequential) instead of running the loop in the main session. Exists so the two orchestration styles can be tested side

• implementation-cycle

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

• milestone-breakdown

  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

• milestone-closing

  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

• project-inception

  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

• strategic-planning

  Facilitate strategic planning for AI-native software projects by adding new milestones to ROADMAP.md through Socratic dialogue. The strategic/planning entry point of the four-phase milestone-driven workflow — not for breaking down tasks or implementing code.

• task-implementation

  Implement the next unfinished task from PLAN.md using strict test-driven development. Writes tests first, then writes just enough code to make them pass, and prepares the result for human review and commit. Operates at the individual task level — one task per invocation. Trigger whenever the user sa

Subagents (4)

• decision-lookup

  Read-only query worker for a project's Architecture Decision Records (in the project's architecture home — `architecture/` by default, overridable via the `.workflow-overrides/architecture-path` file). Given a topic or an action the caller is about to take, reads the crisp per-topic summaries and th

• doc-updater

  Implementation-cycle documentation worker. Runs after `task-worker` has landed a task commit. Inspects that single commit's diff and, only if the change is user- or developer-visible, updates reference docs and examples to match, then `commit`s them as a separate `docs(...)` commit. Defaults to a no

• milestone-scout

  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

• task-worker

  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)

Similar plugins