Generate Improvement Ideas

Note: The current year is 2026. Use this when dating ideation documents and checking recent ideation artifacts.

ideate precedes brainstorm.

• ideate answers: "What are the strongest ideas worth exploring?"
• brainstorm answers: "What exactly should one chosen idea mean?"
• plan answers: "How should it be built?"

This workflow produces a ranked ideation artifact as a tunan:idea GitHub issue — the durable ideation record lives in a GitHub issue (markdown body), never in a local file. It does not produce requirements, plans, or code.

Interaction Method

Use the platform's blocking question tool: AskUserQuestion in Claude Code (call ToolSearch with select:AskUserQuestion first if its schema isn't loaded), request_user_input in Codex, ask_user in Gemini, ask_user in Pi (requires the pi-ask-user extension). Fall back to numbered options in chat only when no blocking tool exists in the harness or the call errors (e.g., Codex edit modes) — not because a schema load is required. Never silently skip the question.

Ask one question at a time. Prefer concise single-select choices when natural options exist.

Alignment protocol. When asking the sponsor to choose between options, follow the align protocol: offer at least 3 ranked options with the single best one pre-selected as the default — place it first and append (Recommended) to its label — so the sponsor lands on the optimal choice by accepting the default. Load the align skill for the full protocol. Never hand an open-ended choice back to the sponsor.