spec-createlisted

# Create a Spec The manual intake, for a change no tracker item covers: something settled in a conversation, a decision from a call, a defect found in passing. Ambiguous scope triggers a grill - a relentless, checkpointed interview. When a tracker item exists or could be made, `spec-pull` is the intake instead - it carries provenance and drift keys this path cannot, so say that out loud before proceeding. It produces `NNN-requirements.md` and hands to `spec-plan`, which writes the plan beside it - the same second half `spec-pull` hands to, so the chain reads identically whichever intake ran. This skill both **creates** a new spec and **updates** an existing one (re-scope when requirements change): in update-mode, re-read the current requirements, apply the delta, and keep a one-line history note. ## Resolve the docs structure (profile, then learn, then default) 1. Profile pins it: `specs_dir`, `features_dir`, `spec_grouping` (`flat` | `quarterly`) in `dev-project-profile.md`. 2. Else learn from the project: locate the existing spec/plan area and read the most recent shipped spec end-to-end - it is the structural template. 3. Greenfield default: `docs/specs/NNN-<slug>/` with `NNN-requirements.md` + `NNN-plan.md` - both files carry the folder's number (`spec-discipline`); `quarterly` grouping nests as `docs/specs/<yyyy>-Q<n>/NNN-<slug>/`. If the project has no docs substrate yet (no `model.md` / `features/` / `specs/`), run `spec-init` first to scaffold it - this skill wr