brainstorm

Structured brainstorming surfaces intent and clarifies constraints to produce a validated design before coding, preventing wasted effort and misaligned requirements. It enforces a disciplined phase to generate concrete specs rather than fragile implementations.

Generate design specifications by starting an interactive brainstorming session that asks clarifying questions one at a time, builds a visual mindmap, and produces concrete artifacts including prd.md, task.json, and contract.md for downstream workflows.

The best way to choose an architecture is to evaluate generated design alternatives. This skill generates two to three viable approaches with specific trade-offs and recommends a path, ensuring the chosen architecture fits your clarified constraints.

Yes, you can prevent coding using safety gates. This skill enforces hard-gates that block any implementation skill from running until the brainstorming phase is complete and the generated design specification receives formal approval.

Yes, brainstorming works without external dependencies. It scans available project files, docs, and recent commits to build initial context, but the interactive clarification process can generate a design from a new feature idea alone.

The specification workflow outputs prd.md, task.json, and contract.md artifacts. These files include automated trace logging and are specifically formatted for consumption by downstream implementation workflows within superharness environments.