Ideation

/xavier ideate uses the same panel architecture as code review, but for brainstorming and strategy instead of code analysis.

How it works

Xavier dynamically selects relevant personas based on the task context and spawns them in parallel. Each persona approaches the problem from a different angle — technical feasibility, user experience, operational concerns, or whatever lenses fit the discussion.

Unlike /xavier review which uses fixed reviewer personas (correctness, security, performance), ideation selects from a broader pool based on what you're exploring.

When to use it

• Exploring a new feature direction — get multiple perspectives before committing
• Evaluating trade-offs — surface concerns you might not have considered
• Architecture decisions — stress-test an approach from different angles
• Problem framing — make sure you're solving the right problem

How it differs from review

Relationship to PRDs

Ideation is a good precursor to /xavier prd. Use it to explore the problem space, then feed the insights into a structured PRD interview. The vault connects them — ideation notes become context for future PRD sessions.