Records one open question's embedded recommendation as its answer in the current milestone's requirements.md, leaving the edit uncommitted for the orchestrator to commit. Invoke with the target question's Short Title as the prompt. Dispatched per-question by the answer-all-open-questions-with-recommendation sweep; not…
Read-only recommendation subagent for a single open question — the non-interactive twin of discuss-open-question. Given one question's Short Title plus context, it grounds in the live project read-only, produces the alternatives + a single recommendation, and returns them as the block's XML sub-elements (one per…
Authors one fully-specified task from a high-level brief and inserts it into the current milestone's TASKSTODO.md at a caller-specified position. Invoked by derive-tasks (bulk); not called directly by the user.
Autonomously sweep the current milestone's requirements for open and deferred questions that already carry an embedded recommendation and record each one's recommendation as its answer — by dispatching the file-editing answer-open-question-with-recommendation agent once per question, strictly sequentially, and…
Record a chosen from an open question's embedded analysis as its answer in the current milestone's requirements.md inline in this conversation, then commit that answer on its own. Use when the recommend sweep has annotated a question with alternatives and you want to accept a specific alternative — named by its id…
Record one open question's embedded recommendation as its answer in the current milestone's requirements.md inline in this conversation, then commit that answer on its own. Use when the recommend sweep has annotated a question with a recommendation and you want to accept and record that recommendation as the decision…
Answer a named open question in the current milestone requirements document, recording the decision and its downstream implications and committing the manual-answer edit.
Use when the user is asking a question about the current milestone rather than trying to change it. Triggers: status checks ("what's done vs still pending?", "what's left and why?"), dependency/ordering questions ("what's blocking task X — is it waiting on something earlier?", "why is it ordered this way?"), recall of…
Distill reusable answering principles from a just-finished milestone's recorded decisions into the project-wide principle store. This is the optional finish-time follow-up that /finish-current-milestone recommends — run it right after finishing a milestone to harvest everything that milestone's manual answers taught.…
Complete a single named task from the current milestone's TASKSTODO.md inline in this conversation, then move it to TASKSDONE.md. Use for one ad-hoc task you want to stay available to discuss and tweak afterwards.
Convert the current milestone's requirements.md into a complete, dependency-ordered TASKSTODO.md. Decomposes the milestone into high-level task briefs, proves every requirement is covered, then delegates the detailed authoring of each task to the submit-task agent.
Clarify a rough or ambiguous issue surfaced mid-flight into one or more clear tasks, then hand off to /submit-task. Use this whenever the user reports a problem, gap, or "we should also..." idea mid-flight but the description is too vague to act on, or whenever they want to talk through an issue before adding it to…
Start a structured conversation about a named open question in the current milestone requirements — surfaces alternatives, trade-offs, and a recommendation to help the user reach a decision.
Mark the current milestone as done — records accomplishments in milestones/README.md, clears the current-milestone pointer to "none" in milestones/README.md, and updates CLAUDE.md only for lasting changes to the project's environment context.
Activate an already-defined milestone — scans milestones/ for a defined-but-not-yet-active directory and updates milestones/README.md to point to it as the current milestone. Requires finish-current-milestone to have been run first (current pointer must be "none").
One-time bootstrap for the milestone workflow in a project — creates the milestones/ directory and milestones/README.md with the Current Milestone pointer, and ensures CLAUDE.md carries the Milestone Workflow guidance. Safe to run on an existing project; never overwrites existing files.
Revise the ## Goal of the current milestone's requirements.md when a discussion reveals the goal itself — not just an open question — needs to change. Use when the user wants to reshape, broaden, narrow, or correct the objective of an already-defined milestone (e.g. "the goal should also cover X", "drop Y from the…
Non-interactively sweep the current milestone's requirements for open and deferred questions and annotate each one with an embedded recommendation — alternatives plus a single recommended option — produced by dispatching one read-only recommend-open-question subagent per question. Use this to batch the per-question…
Run a review pass over the current milestone's requirements.md to drive its open-questions loop forward — reconcile the existing question set against what's already been decided (prune blocks an existing decision now covers, dedup repeats), surface genuinely new gaps the latest decisions exposed, and report whether…
Analyze the project's existing state and fill the "Relevant starting state" section of a milestone's requirements.md with context that supports future decisions.