spec-ideatelisted

# spec-ideate Turn a rough product ask into a `requirements.md` under `specs/NNN_feature_slug/`. This is step 1 of the spec-driven workflow: `spec-ideate` → `spec-tasks` → `spec-build`. ## When to use Invoke when the user wants to start a new feature, capture requirements, or "ideate" on a product idea. The input is a product idea for planning purposes — not an implementation request. ## Procedure 1. **Grill first.** Apply the `grilling` skill to interrogate the idea: ask one question at a time, wait for each answer, and give a recommended answer per question. Look up _facts_ in the codebase yourself; only put genuine product _decisions_ to the user. Continue until you reach a shared understanding of the product ask. 2. **Compute the next number.** List `specs/`, find the highest existing `NNN_*` directory, add one, zero-pad to three digits. Numbers are never reused — even if a feature was abandoned, do not fill its slot. 3. **Derive the slug.** `NNN_feature_slug` — snake_case, ASCII only, drop punctuation. 4. **Write the file** at `specs/NNN_feature_slug/requirements.md` using the canonical structure below. 5. **Seed the index.** Append a row to the table in `specs/README.md` with `Status: Draft` and today's date. 6. **Format.** Run `deno fmt specs/NNN_feature_slug/requirements.md specs/README.md`. 7. **Report back** with the new path, and suggest running `spec-tasks` to break it into deliverable tasks. ## Canonical requirements.md structure Produce a file ma