brainstorming

Refines ideas into validated designs through structured one-question-at-a-time dialogue.

92|12|Updated Dec 21, 2025
One-click install
npx skills add https://github.com/ARounder-183/HiFiShifter --skill brainstorming-arounder-183
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/ARounder-183/HiFiShifter/tree/main/.github/skills/brainstorming
Command: npx skills add https://github.com/ARounder-183/HiFiShifter --skill brainstorming-arounder-183

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Jumping straight into implementation without clarifying requirements leads to wasted effort and misaligned features. This Skill guides a collaborative dialogue that turns vague ideas into fully formed, validated designs before any code is written. ## Core Features & Use Cases - Incremental Requirement Discovery: Explores user intent by asking one question at a time, preferring multiple-choice formats to reduce friction. - Approach Comparison: Proposes 2-3 alternative approaches with trade-offs and a reasoned recommendation before settling on a direction. - Sectioned Design Validation: Presents the design in 200-300 word sections covering architecture, components, data flow, error handling, and testing, confirming each part before continuing. - Use Case: Before building a new feature, use this Skill to clarify purpose, constraints, and success criteria, then save the validated design to docs/plans/ as a dated markdown file committed to git. ## Quick Start Ask the AI to brainstorm and refine your feature idea into a validated design document before starting implementation.

Frequently Asked Questions about brainstorming

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I turn a feature idea into a design document?

Start a brainstorming session that explores your intent through one question at a time, compares 2-3 approaches with trade-offs, then presents the design in 200-300 word sections for validation. The final design is saved to docs/plans/ as a dated markdown file.

When should I brainstorm before writing code?

Brainstorm before any creative work such as creating features, building components, adding functionality, or modifying behavior. Clarifying purpose, constraints, and success criteria upfront prevents rework from misunderstood requirements.

What does the brainstorming design document include?

The design covers architecture, components, data flow, error handling, and testing. It is presented in sections of 200-300 words each, validated incrementally, then written to docs/plans/YYYY-MM-DD-topic-design.md and committed to git.

Can brainstorming skip straight to implementation?

No, the process requires exploring requirements and comparing approaches first. After the design is validated, it optionally hands off to implementation using git worktrees and a detailed implementation plan.

What are the limitations of a dialogue-based design process?

The process depends on user availability to answer questions and validate each section, so it is slower than autonomous generation. It is less suitable for trivial changes where design overhead exceeds the implementation effort.