Guide structured ideation to convert raw ideas into design-ready specs.
npx skills add https://github.com/iEnergyy/opsflow --skill brainstorming-ienergyy
Please help me install this Agent Skill. Skill: brainstorming Source: https://github.com/iEnergyy/opsflow/tree/main/.agents/skills/brainstorming Command: npx skills add https://github.com/iEnergyy/opsflow --skill brainstorming-ienergyy
Brainstorming provides a structured, collaborative process to turn vague ideas into concrete designs and specs by guiding context gathering, questions, option exploration, and formal design documentation before implementation.
Clarify the project goal, then present 2-3 design approaches and draft a design doc after user approval.
High-intent search queries and answers about installing and using this skill.
Structured brainstorming converts vague ideas into design-ready specs by guiding context gathering, asking clarifying questions, and comparing approaches before drafting documentation. This enforces requirement discovery and alignment prior to implementation.
The best way to elicit requirements during product planning is through guided context exploration and sequential clarifying questions. This collaborative ideation process aligns team goals and extracts specific design requirements before any implementation begins.
To document design approaches during feature brainstorming, generate 2-3 options to evaluate trade-offs, then draft a participatory design doc. This structured process ensures options are vetted and recorded for user approval before implementation.
Yes, you can use structured ideation for design sprints to facilitate collaborative requirement discovery. The process enforces a multi-step workflow including context exploration, option presentation, and self-review to gate user approval before moving forward.
Yes, the brainstorming workflow requires user approval gating before finalizing the design doc. After presenting multiple approaches and evaluating trade-offs, the process pauses for explicit user sign-off to ensure the selected direction meets requirements.
You should avoid a multi-step ideation workflow if your project lacks vague ideas requiring structured discovery or if you already possess concrete design-ready specs. This process ensteps sequential questioning and approach comparison, which is redundant for fully defined requirements.
phyter1Convert raw ideation documents into structured product requirement specifications.
LucaDeLeoConvert brief engineering specs into executable development workflows.
zooid-aiDeploy and manage Zooid pub/sub servers with CLI and API tools.
telum-aiTransform unstructured ideas into structured project concepts with theme clustering.
