save-speclisted

# Scaffold Project SPEC.md (`/save-spec`) **Habits**: H8 (Find Your Voice — pick the deployment mode that fits your repo) + H2 (Begin with End in Mind — establish the save point on day 1) | **Anti-pattern**: Copying the SPEC.md template by hand every time you start a new operational repo, then forgetting to fill the timestamp. ## When to Use - The repo fits the **project-orientation hub mode** (operational / infra / integration / single-system) — not the per-feature `--persist <slug>` mode. - You want a one-page digest at the project root that points to project-specific detail files and acts as the read-first save point after `/clear` or `/compact`. - No `SPEC.md` exists yet at the project root. - See `guides/spec-digest-pattern.md` for the full pattern. This skill scaffolds the file; the discipline of maintaining it is yours. ## When to Skip - Repo uses the **feature-spec mode** (`docs/specs/<slug>/{prd,design,tasks,current-state}.md`). Use `/requirements --persist`, `/design --persist`, `/breakdown --persist` instead. - `SPEC.md` already exists at the project root — Phase 1 is generator-only; edit it manually or wait for Phase 2 `--update`. - One-off scripts / single-file repos where a digest adds no value. - **Memory-MCP already active** (`claude-mem`, `memforge`, or equivalent with SessionStart context injection) AND your existing `CLAUDE.md` is short enough to scan in <30 seconds (a ~150-line threshold is a reasonable rule of thumb). In that combination, §1 (archite