specifylisted

Capture feature intent and acceptance criteria before planning begins. Writes `docs/specs/<YY_MM_DD_HH>_<name>/spec.md` and stops — the user must approve the spec before the `plan` skill runs. ## Doc paths Default convention: specs live under `docs/specs/`. Check the project's `CLAUDE.md` for an overriding location (e.g. a "Docs Layout" section or explicit mention of spec paths) before falling back to the default. ## Spec Identifier Derivation 1. Use `Glob` with pattern `docs/specs/*/*.md` to list existing spec folders — do NOT use a trailing-slash pattern (`docs/specs/*/`) or a bare `docs/specs/*`, both silently return nothing on Windows; the nested `*/*.md` form matches files one level down and works 2. Generate the current local timestamp as `YY_MM_DD_HH` (for example, `26_07_18_14`) 3. Combine it with a short kebab-case feature name: `<YY_MM_DD_HH>_<name>` 4. Do not derive or assign a numeric index ## Orchestration Spawn an **architect sub-agent** (general-purpose) briefed with: - The user's feature description - Relevant project rules from `CLAUDE.md` and any project rules directory - The output path: `docs/specs/<YY_MM_DD_HH>_<name>/spec.md` - The spec format below The architect writes the spec file directly. You (orchestrator) then: 1. Present the spec contents to the user 2. Collect feedback and re-brief the architect if changes are needed (iterate until the user approves) 3. **Stop.** Do not run the `plan` skill or write any code. The user must explicitly requ