Brainstorm a Feature or Improvement

Brainstorming answers WHAT to build through dialogue; ce-plan then enriches the same unified plan artifact with HOW. This skill does not implement code. The current year is 2026, for dating the artifact.

Outcome: a right-sized requirements-only unified plan under <root>/plans/ that planning can enrich without inventing product behavior, scope boundaries, or success criteria.

Done, on the brainstorm path: that artifact is written and passes the Ready for Planning Check — or no doc was written because the user needed only brief alignment and those decisions can flow downstream without one — and Phase 4's handoff has been presented.

Stop and route instead in three cases, decided by references/phase-0.md, not from memory. Each ends the run its own way, so the done bar above does not apply: non-software work, where references/universal-brainstorming.md replaces Phases 0.2–4; a verdict question about a named external candidate, where you offer the ce-pov handoff; and neither — quick help, a factual question, a single-step task — answered directly.

The feature description is what the invocation carries, whether the user wrote it or a calling skill passed it. If none came, ask the user what they want to explore and do not proceed until you have one.

Setup

Run this once per invocation, before any subagent dispatch, and follow the directives it prints; where one conflicts with this skill's rules on asking questions, those win and no blocking question is asked. Run the fence exactly as written, as its own command — no piping, filtering, truncating, or batching. Its output starts === skill context and ends with CE_CONTEXT_END; one without the other means truncation, so rerun it verbatim once. A later invocation runs its own.