managing-specslisted

# Managing the Spec Manifest The spec manifest (`specs/manifest.json`) tracks every specification in the project. Never edit it by hand — always use the manifest-ops script. ## Running the Script ```bash node --experimental-strip-types --disable-warning=ExperimentalWarning .claude/scripts/spec-manifest-ops.ts <command> [args] [options] ``` ## Canonical Statuses Only four statuses are valid: | Status | Meaning | | ------------- | ------------------------------- | | `ideation` | Spec has `01-ideation.md` | | `specified` | Spec has `02-specification.md` | | `implemented` | Spec has `04-implementation.md` | | `superseded` | Replaced by a newer spec | Non-canonical aliases are normalized automatically: `draft` -> `ideation`, `specification` -> `specified`, `completed` -> `implemented`. ## Status Progression Statuses move forward only: **ideation -> specified -> implemented -> superseded**. The script rejects regressions unless `--force` is passed. ## When to Update Status - After writing `01-ideation.md` -> set to `ideation` - After writing `02-specification.md` -> set to `specified` - After all implementation tasks complete -> set to `implemented` - When replaced by a newer spec -> set to `superseded` ## Commands ### Update status ```bash node --experimental-strip-types --disable-warning=ExperimentalWarning \ .claude/scripts/spec-manifest-ops.ts update-status <slug> <status> ``` ### Add a new spec ```bash node -