brainstorming

Clarifies requirements and writes validated design docs to docs/plans.

Updated Mar 22, 2026

Search Tags:#architecture #documentation #brainstorming #design specification #product planning #requirements discovery

Ready to run

npx skills add https://github.com/engineai-nz/engineai-skills --skill brainstorming-engineai-nz

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/engineai-nz/engineai-skills/tree/main/brainstorming
Command: npx skills add https://github.com/engineai-nz/engineai-skills --skill brainstorming-engineai-nz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you transform a rough idea into a clear, implementable design by first clarifying intent, requirements, constraints, and success criteria to avoid building the wrong thing.

Core Features & Use Cases

One-question-at-a-time requirement discovery to rapidly uncover purpose, constraints, and measurable success criteria.
Multi-approach design exploration by generating 2–3 options and recommending a preferred path with trade-offs.
Incremental design validation by presenting the design in 200–300 word sections and checking alignment after each section.
Documentation + handoff support by writing the validated design to docs/plans with a git commit, and then prompting for implementation planning when you’re ready.

Quick Start

Ask the skill: “Help me brainstorm and validate a design for building [feature/component] for my current project, starting with the most important questions.”

Frequently Asked Questions about brainstorming

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

FAQPage Schema

How do I turn ambiguous product ideas into validated design specifications?▼

To turn ambiguous ideas into validated design specifications, clarify user intent, requirements, constraints, and success criteria through one-question-at-a-time discovery, then generate multi-approach design options with trade-offs before writing a final plan.

What is the best way to document feature design plans for an active codebase?▼

The best way to document feature design plans for an active codebase is by incrementally validating design sections and writing the finalized, dated plan file to a docs/plans directory with a git commit to ensure careful alignment.

How does incremental design validation work during requirements discovery?▼

Incremental design validation during requirements discovery works by presenting the design in 200–300 word sections and checking alignment after each section to ensure the translation of ambiguous ideas into a clear, implementable design.

Can I explore multiple design approaches before writing a final plan file?▼

You can explore multiple design approaches by generating 2–3 options and recommending a preferred path with trade-offs before finalizing the design documentation and writing a dated plan file.

Does requirements discovery support implementation handoff for component planning?▼

Requirements discovery supports implementation handoff for component planning by writing validated design documentation to docs/plans with a git commit and then prompting for implementation planning when ready to proceed.