openspec-brainstorming

To brainstorm design requirements and save them to OpenSpec, this skill guides a structured questioning process and automatically writes the validated design artifacts to openspec/changes/<feature-name>/proposal.md. It detects existing OpenSpec configurations and routes the workflow accordingly.

The best way to elicit formal specs from collaborative brainstorming is through one-question-at-a-time refinement that extracts validated design sections into openspec/changes/<name>/specs. This ensures design artifacts remain aligned and traceable with project requirements.

An existing OpenSpec setup is not strictly required to function, as the workflow detects openspec/config.yaml and routes to the OpenSpec change workflow, otherwise falling back to standard brainstorming. However, an initialized OpenSpec directory is necessary to save proposal and spec artifacts.

Design proposals are structured and delivered in 200-300 word sections during the brainstorming process, allowing for incremental validations. This segmented presentation ensures collaborative requirement elicitation and design exploration remain focused before spec extraction.

Yes, you can generate change proposals and specs across multiple design topics simultaneously. The skill handles requirement elicitation, design exploration, and spec extraction across multiple topics, creating distinct change proposals within the openspec directory structure.