brainstorming

Transforms vague ideas into validated design specifications through structured multi-phase dialogue.

Updated Apr 11, 2026
One-click install
npx skills add https://github.com/Coral5644/NekansModPack --skill brainstorming-coral5644
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/Coral5644/NekansModPack/tree/main/.cursor/skills/brainstorming
Command: npx skills add https://github.com/Coral5644/NekansModPack --skill brainstorming-coral5644

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Starting implementation on a vague idea leads to scope creep, missed requirements, and rework. This Skill guides a structured brainstorming workflow that turns fuzzy concepts into confirmed design documents before any code is written. ## Core Features & Use Cases - Phased Requirement Discovery: Progresses through intent exploration, scope boundary definition (in-scope vs out-of-scope), feature point breakdown, and risk assessment with explicit user confirmation at each stage. - Technical Feasibility Verification: Requires Spike validation with minimal test code for unused APIs or uncertain engine behaviors, recording conclusions in a technical constraints table. - Design Presentation & Documentation: Presents the design in 200-300 word sections for incremental confirmation, then commits the approved design to Docs/plans/<business-name>/ and hands off to implementation planning skills. - Use Case: Before adding a blueprint rotation feature to a NetEase MC mod, use this Skill to confirm scope, evaluate engine API risks, compare 2-3 implementation approaches, and produce a committed design document. ## Quick Start Ask the AI to brainstorm and design the new feature you have in mind before writing any code.

Frequently Asked Questions about brainstorming

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

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

Use a phased brainstorming workflow: first explore user intent with batched questions, then define in-scope and out-of-scope boundaries, break down feature points, assess risks, and present the design in small sections for confirmation. The confirmed design is written to a plans directory and committed to git.

What should a software design brainstorming process include?▼

It should cover requirement understanding, explicit scope boundaries, core and optional feature points, risk and compatibility assessment, technical feasibility verification for uncertain APIs, and comparison of 2-3 implementation approaches with a clear recommendation.

When is a spike test needed before finalizing a design?▼

A spike is needed when the design uses APIs never used in the project, relies on undocumented engine behavior, or touches platform-specific limitations. Write a minimal test under 30 lines, verify in the target environment, and record the conclusion in the design's technical constraints section.

How do I prevent scope creep during feature planning?▼

Explicitly list what is in scope and out of scope after understanding requirements, and get user confirmation before continuing. Apply the YAGNI principle to remove non-essential features from every proposed design.

What are the limitations of a conversation-based design workflow?▼

It depends on user availability for confirmation at each phase and cannot verify engine or API behavior without actual in-environment testing. Assumptions from prior sessions must be revalidated rather than inherited directly.