ideatelisted

# Ideate Turn raw ideas into sharp, SpecScore-compatible Idea artifacts through structured divergent and convergent thinking. ## Hard Gate <HARD-GATE> Do NOT invoke `specstudio:specify`, `specstudio:plan`, `specstudio:implement`, `writing-plans`, or any implementation skill until: 1. An Idea artifact has been written to `spec/ideas/<slug>.md`. 2. `specscore spec lint` passes. 3. The user has explicitly approved the Recommended Direction. Ideas that can't be lint-clean aren't ready to be specified. </HARD-GATE> ## When to Use - Raw, vague, or unvalidated concept. - User unsure whether an idea is worth building. - Multiple possible directions with no clear winner. - **Skip** when: the user already has an approved Idea or a clear, high-conviction feature to specify — go straight to `specstudio:specify`. ## Philosophy See [philosophy.md](../shared/philosophy.md). Key tenets here: *simplicity is the ultimate sophistication*, *say no to 1,000 things*, *challenge every assumption*, *unsaved ideation is waste*, *prefer stable CLI contracts over ad-hoc file writes when both are possible*. ## Path Conventions Artifacts land at `spec/ideas/<slug>.md`. See [path-conventions.md](../shared/path-conventions.md). Never use `docs/ideas/`. If `spec/ideas/` does not exist when the skill is invoked, **bootstrap it** before writing the first artifact: create the directory and a lint-clean `spec/ideas/README.md` index (`type: index`, empty Contents table, `Outstanding Questions: N