ideating-featureslisted

# Ideating Features ## Overview This is the shared-skill replacement for the legacy Claude Code `/ideate` workflow. Use it to: - turn a brief into a structured ideation document - preserve and upgrade existing rough notes or partial design docs - explore implementation options before specification work - resolve key product and technical decisions before writing a spec ## Read First Before acting, read: - `AGENTS.md` - `.claude/skills/orchestrating-parallel-work/SKILL.md` only if the user explicitly asks for parallel agent work If the work is already tied to the spec system, also inspect: - `specs/manifest.json` - any existing `specs/<slug>/` materials referenced by the user ## Core Workflow 1. **Check for existing source material** - If the user gave a file path, rough notes, partial spec, or detailed design, read it first. - Preserve detail; do not paraphrase away concrete constraints, numbers, or examples. 2. **Classify maturity** - rough notes -> normal ideation - partial spec -> fast-track toward specification work - detailed spec -> adapt rather than re-ideate 3. **Create or identify the feature slug** - keep names URL-safe and consistent with `specs/` 4. **Capture intent and assumptions** - restate the brief - list explicit assumptions - define scope boundaries 5. **Do discovery** - inspect the relevant codebase areas - research only when needed - use parallel agent work only when the user explicitly asks for it 6. **Resol