project-foundationlisted

# project-foundation Drive the front-half foundation flow — charter through Definition of Ready — across ten phases, producing a docs-managed Markdown tree the `create-milestones` skill can pick up. Requires [`docs-cli`](https://github.com/ArtRichards/docs-cli) **v1.2.0 (M7+)** for the `Lifecycle:` controlled-vocab field and expanded role vocab, and **v1.3.0 (M8+)** for `docs new --body-from -|<path>` (single-call atomic authoring) and the tree-wide `[exclude]` section in `.docs.toml`. Ask the user to upgrade if the host's `docs` binary is older. ## When this applies The user wants to start a new project (or a sub-project) and needs the foundation work done before any implementation begins: problem, scope, architecture choice, milestone plan, environment, data, test strategy, documentation plan, risks, Definition of Ready gate. Do **not** apply when: - The project already has a docs tree with foundation artifacts — use `create-milestones` to begin or resume milestone work. - The user wants a one-off doc (a single charter, a single ADR) — author it with `docs new` directly. - The user has an existing Markdown directory they want to adopt rather than start from scratch — point them at `docs migrate` first; this wizard runs after the tree is in convention. ## Substance lives in references/ This SKILL.md is intentionally short. The full procedure lives in: - [`references/foundation-playbook.md`](references/foundation-playbook.md) — step-by-step procedure with a