brainstorming

To turn raw ideas into approved design concepts, you need a structured process that explores context, asks clarifying questions, and proposes multiple design options with trade-offs before writing a design document for approval.

Documenting UX changes and architecture decisions with unclear requirements requires a stepwise approach: explore existing context, resolve uncertainties through questions, propose design approaches, and write validated documentation to a design markdown file.

Yes, generating multiple design approaches with trade-offs for early-stage feature planning involves exploring project context, asking clarifying questions one at a time, and presenting 2-3 options with a clear recommendation for approval.

Yes, this brainstorming workflow outputs a standard design document written to docs/plans/YYYY-MM-DD-<topic>-design.md, which is then handed off to a planning skill for implementation.

You need a stepwise design process with context exploration for feature planning when raw ideas require validation, requirements are unclear, or when you need to reduce rework and miscommunication before implementation begins.

To reduce rework and miscommunication when converting ideas into design concepts, enforce a process that grounds designs in existing context, confirms approval section by section, and produces clear design documentation before handoff.