Guide brainstorming sessions to produce design-ready concepts and formal design docs.
npx skills add https://github.com/rafifos/dotfiles --skill brainstorming-rafifos
Please help me install this Agent Skill. Skill: brainstorming Source: https://github.com/rafifos/dotfiles/tree/main/dot_agents/skills/brainstorming Command: npx skills add https://github.com/rafifos/dotfiles --skill brainstorming-rafifos
Brainstorming is a guided process that converts vague ideas into clear design directions by exploring context, requirements, and constraints before any implementation.
Start by sharing your project context and goals, and I will guide you through a structured brainstorming design session.
High-intent search queries and answers about installing and using this skill.
To turn vague ideas into design-ready requirements, you need a structured ideation process that identifies goals and constraints, asks one-question-at-a-time clarifications, and proposes approaches with trade-offs. This yields formal design documentation for stakeholder alignment.
The best way to run a design-thinking brainstorming session is enforcing a structured process: share project context, answer one-question-at-a-time clarifications, review 2-3 proposed design approaches, and select a recommended path to generate a formal specification document.
Yes, you can use this structured ideation process to align stakeholders before implementation. It converts raw ideas into clear design directions by exploring context and constraints, ultimately generating a detailed design spec for formal handoff.
Clarifying requirements one question at a time improves design discovery by isolating specific goals and constraints incrementally. This structured approach prevents overwhelming stakeholders and ensures raw ideas are accurately shaped into design-ready concepts with clear trade-offs.
To start a structured brainstorming design session, you simply need to provide your raw project context and goals. The process will then guide you through requirements discovery, propose multiple design approaches, and generate a formal design doc for handoff.
You should avoid using a guided brainstorming process for project planning when your requirements are already fully specified and design-ready. If no stakeholder alignment or context discovery is needed, the structured ideation and trade-off analysis steps are unnecessary.
ydnikolaevExtract project information through structured stakeholder interviews into a discovery brief.
flosrnGuide feature design from clarifying questions to an approved design document.
edwardmonteiroCreate dashboard briefs aligning analytics and design stakeholders on goals and data requirements.
jankneumannExplores ideas and project needs interactively without changing files.
