brainstorming

Refines feature ideas into structured design documents through guided dialogue.

Updated Oct 2, 2025
One-click install
npx skills add https://github.com/YuriiYInno/Innogram --skill brainstorming-yuriiyinno
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/YuriiYInno/Innogram/tree/main/.codex/skills/brainstorming
Command: npx skills add https://github.com/YuriiYInno/Innogram --skill brainstorming-yuriiyinno

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a vague feature idea into an actionable design is hard when requirements, constraints, and architecture decisions are unclear. This Skill guides a structured conversation that explores user intent, compares approaches, and produces a written design document before any code is written. ## Core Features & Use Cases - Guided Requirement Exploration: Asks one question at a time (preferring multiple choice) to clarify purpose, constraints, and success criteria. - Approach Comparison: Proposes 2-3 alternative approaches with trade-offs and a reasoned recommendation, including library-vs-custom-build decisions. - Incremental Design Validation: Presents the design in 200-300 word sections covering architecture, data model, API design, error handling, and testing, confirming each section before continuing. - Persistent Design Output: Writes the final design to tasks/TASK-{N}/brainstorming-design.md using a task counter, so context survives conversation resets. - Use Case: Before building a notifications feature, use this Skill to clarify requirements, decide between WebSockets and polling, choose a queue library, and save the agreed design for the planning phase. ## 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 before coding?▼

Start a brainstorming session that asks clarifying questions one at a time, explores 2-3 approaches with trade-offs, and presents the design in small validated sections. The final design is written to tasks/TASK-{N}/brainstorming-design.md for later implementation.

Should I use a library or build a custom solution for my feature?▼

The skill defaults to recommending established libraries for logging, validation, auth, and similar concerns. Custom implementations require explicit justification such as licensing or bundle size, and the rationale is documented in the design.

What does the brainstorming design document contain?▼

The design document follows a fixed template: problem statement, proposed solution, architecture, data model, API design, error handling, testing strategy, security considerations, and open questions. It is saved as brainstorming-design.md inside the task directory.

When should I not use a brainstorming phase?▼

Skip it for trivial changes like typo fixes, config tweaks, or well-specified bug fixes where requirements are already unambiguous. It is intended for creative work such as new features, components, or behavior modifications.

How does task numbering work for design documents?▼

If a task number comes from a prior requirements-analyst step it is reused. Otherwise the skill reads or creates tasks/.task-counter, or scans existing TASK-* directories and uses the highest number plus one.