ideate

# Ideate: grounded divergent generation behind a reject-by-default gate `ideate` turns a vague subject into a bounded set of candidate directions that survived critique, with the rejected candidates kept and explained rather than dropped. Flow: ground the subject in the real codebase, generate many candidates across parallel generators, critique all, then write the survivors plus the rejection rationale for the losers. It writes one surface by default: the operating repo's `docs/ideation/<slug>.md`, markdown; always the canonical surface. The opt-in `format:html` flag additionally renders a human-reading HTML view derived from that markdown (`references/html-rendering.md`); it never replaces the markdown and never changes the default output. Idea selection is reject-by-default. A candidate earns a place by surviving the critique, never by default. `Op:` of an ideate run is `extend`. A new ideation doc is a load-bearing capability added to the repo's decision record. ## Auto-invoke <auto_invoke> <trigger_phrases> - "let's brainstorm" - "what should we build" - "what should we build next" - "any ideas for" - "ideas for" </trigger_phrases> Fire automatically on a trigger phrase or on `/ideate`. The reject-by-default critique below still decides which candidates earn a place in the doc. Auto-firing is permission to evaluate behind that gate, not permission to fabricate ideas to look productive. If the subject is unidentifiable, ask one clarifying question (or hand off to `ask...