| name | haiku-ideate |
| description | Surface adversarially-filtered improvement ideas from the codebase |
Ideate
Analyze the codebase and surface high-impact improvement ideas that survive adversarial scrutiny.
- Scope — If a focus area is given, analyze that. Otherwise analyze the full codebase (prioritize high-churn areas).
- Identify opportunities: Performance, Security, Maintainability, Test Coverage, DX.
- Adversarial filter — Argue against each idea on cost, prematurity, complexity, alternatives, risk.
- Present survivors with: one-line description, impact, effort (low/med/high), strongest argument against, verdict (do it / park it). Also list discards with reasons.
- Next steps: Elaborate (
/haiku:haiku-start), deep-dive (/haiku:haiku-ideate <sub-area>), or discard.
Be ruthless — five strong ideas beat twenty weak ones. Zero ideas is valid if nothing survives.