specify-milestone-starting-statelisted

# specify-milestone-starting-state Reads the milestone goal, explores the project's existing state, and writes a concise summary into the `## Relevant starting state` section of `requirements.md`. The output is reference material — not decisions — to ground the `## Decisions` conversation that follows. ## Usage ``` /specify-milestone-starting-state <milestone_id> ``` - `<milestone_id>`: the milestone directory name under `milestones/`, e.g. `milestone_12_user-guide`. **Example:** ``` /specify-milestone-starting-state milestone_12_user-guide ``` ## Workflow ### 1. Locate the milestone Resolve `milestones/<milestone_id>/requirements.md`. If the file does not exist, stop and report that the milestone was not found — suggest running `/define-milestone-goal` first. ### 2. Read the goal Read `requirements.md` in full. Extract the `## Goal` section. This is the lens for everything that follows — only surface starting state that is directly relevant to achieving or building on that goal. ### 3. Load the environment and explore the project Read `CLAUDE.md` at the workspace root for the project's environment. If it carries no description of the project's domain context or working conventions, suggest the user run `/init` to enrich it first — richer project context yields a sharper starting-state summary — then proceed with whatever the project reveals. Extract from `CLAUDE.md`: - The project's domain context — what the project is and how its material is organized; use this