ce-ideate

To generate grounded ideas anchored to your codebase context, provide a topic and the system will execute multi-frame ideation, tethering generated concepts to repository docs and workflows before applying adversarial critique to surface survivors.

Adversarial critique in codebase ideation is a rejection phase that filters generated concepts to surface only strong, well-supported survivors. You need it when divergent ideation produces too many untested ideas requiring strict validation.

You ideate across multiple perspectives without losing repository grounding by using a multi-frame exploration phase that generates roughly six ideas per frame, ensuring every divergent concept stays explicitly tethered to original codebase context.

Yes, codebase ideation works with Slack context and web research as optional, opt-in augmentations during the grounding phase to inform the generation of ideas with real-time external data and conversation history.

Yes, you can save ideation survivors directly to repository docs. In repo-mode, the system persists the five to seven surfaced survivors with warrants into your documentation, or saves them to Proof when operating elsewhere-mode.

The best way to critique generated concepts against rejection criteria is applying an adversarial review phase that filters multi-frame ideas, surfacing only five to seven well-supported survivors with explicit warrants attached.