skills.rest
Emmanuel-R8
Emmanuel-R8COMMUNITY
Explore all skills by this author →
WebsiteGitHub

brainstorming

Refines feature ideas into validated design documents through structured dialogue.

1|Updated Feb 18, 2026
Search Tags:#git#design#architecture#documentation#brainstorming#requirements#feature planning
One-click install
npx skills add https://github.com/Emmanuel-R8/aikos --skill brainstorming-emmanuel-r8
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/Emmanuel-R8/aikos/tree/main/.cursor/skills/brainstorming
Command: npx skills add https://github.com/Emmanuel-R8/aikos --skill brainstorming-emmanuel-r8

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Jumping straight into coding a new feature often leads to misunderstood requirements, over-engineered solutions, and wasted rework. This Skill guides a structured brainstorming process that turns a rough idea into a validated design before any implementation begins. ## Core Features & Use Cases - Guided Requirement Discovery: Explores user intent, constraints, and success criteria by asking one focused question at a time, preferring multiple-choice formats. - Approach Comparison: Proposes 2-3 alternative approaches with trade-offs and a clear recommendation before settling on a direction. - Incremental Design Validation: Presents the design in 200-300 word sections covering architecture, components, data flow, error handling, and testing, confirming each section before continuing. - Use Case: Before building a new authentication feature, use this Skill to clarify requirements, compare session-based versus token-based approaches, and produce a committed design document at docs/plans/YYYY-MM-DD-auth-design.md. ## 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 feature idea into a design document?▼

Start by reviewing the current project state, then answer clarifying questions one at a time about purpose, constraints, and success criteria. The design is presented in 200-300 word sections for validation, then written to docs/plans/ with a dated filename and committed to git.

How to compare different implementation approaches before coding?▼

The process proposes 2-3 alternative approaches with explicit trade-offs, leading with a recommended option and its reasoning. You discuss the options conversationally before settling on a direction, avoiding premature commitment to a single solution.

When should I use brainstorming before writing code?▼

Use it before any creative work: creating features, building components, adding functionality, or modifying behavior. It is designed for the pre-implementation phase where requirements and design are still uncertain.

What happens after the design is validated?▼

The validated design is written to docs/plans/YYYY-MM-DD-<topic>-design.md and committed to git. If you continue, the workflow moves to creating an isolated git worktree and writing a detailed implementation plan.

Does this brainstorming process work for small changes?▼

It applies YAGNI principles to strip unnecessary features, so small changes move through quickly. However, for trivial fixes with no design ambiguity, the full question-and-answer flow may add little value.

Related Skills

Explore More Software Engineering Skills→
ContentsUSContentsUS

ccc

Create a GitHub issue with git context and session history.

Official
Basic
ed3daied3dai
5

starting-an-implementation-plan

Create an implementation plan from a design plan with branch setup and handoff.

Official
Advanced
javierhbrjavierhbr

docs-style

Apply documentation style principles for voice, structure, and LLM-friendly patterns.

Community
Basic
c-sonnierc-sonnier
2

convergence-design

Coordinate collaborative design sessions and produce a formal design document.

Community
Advanced