init-milestone-base-workflowlisted

# init-milestone-base-workflow Bootstraps the milestone-driven workflow inside a project. It creates the `milestones/` directory and `milestones/README.md` (with the grep-able `Current milestone:` pointer line), and ensures `CLAUDE.md` contains the `## Milestone Workflow` guidance. Run this **once** per project, before any other workflow skill. This skill is additive and idempotent: it creates missing scaffolding and inserts missing sections into existing files, but never overwrites or rewrites content that is already there. It does not commit — staging is left to the user. ## Usage ``` /init-milestone-base-workflow ``` No arguments. ## Workflow ### 1. Detect existing state Probe the workspace root in parallel and record what already exists: - Does `milestones/` exist? - Does `milestones/README.md` exist? If so, does it contain a `Current milestone:` line? - Does `CLAUDE.md` exist? If so, read it and note whether it already contains a `## Milestone Workflow` section. Use these findings to decide which steps below are no-ops. If **all** of the following are already present — `milestones/`, `milestones/README.md`, and a `Current milestone:` line in `milestones/README.md` — the project is already initialized: report that and stop without changing anything. ### 2. Create the milestones/ directory If `milestones/` does not exist, create it. Create no `milestone_<N>_<slug>/` directory inside it — that is `/define-milestone-goal`'s job. ### 3. Create milestones/README.m