brainstorming

Convert vague requests into concrete directions with locked decisions.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Refine fuzzy requests into concrete directions through ideation, decision locking, and spec-driven development, enabling smoother handoffs to planning.

Core Features & Use Cases

  • Ideation and domain classification to surface options and decisions
  • Mode-based outputs: quick (lock direction only), spec (full brainstorm with FR/NFR/AC/Scenarios), deep-explore (Socratic dialogue with optional CONTEXT.md)
  • Stable decision IDs (D1, D2, ...) for downstream planning
  • Output-ready direction, constraints, and scope boundary for planning

Quick Start

Provide a rough idea or goal and receive a concrete direction with locked decisions ready for planning.

Frequently Asked Questions about brainstorming

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

FAQPage Schema
How do I turn vague feature ideas into concrete requirements and decisions?

To turn vague ideas into concrete requirements, use a brainstorming process that applies ideation and domain classification to explore options. This refines fuzzy requests into a clear direction with locked decisions and an optional spec with FR, NFR, AC, and scenarios for planning.

What is the best way to lock decisions before starting software planning?

The best way to lock decisions before planning is to generate stable decision IDs like D1 and D2 during ideation. This establishes locked decisions and scope boundaries, ensuring downstream planning begins with a concrete direction and clear constraints.

How do I write a full spec with FR, NFR, AC, and scenarios from a rough goal?

To write a full spec from a rough goal, use a spec-based brainstorming mode that outputs functional requirements, non-functional requirements, acceptance criteria, and scenarios. This converts ambiguous requests into an output-ready direction and an optional spec for implementation.

Can I use Socratic dialogue to explore ambiguous requirements and surface options?

Yes, you can use a deep-explore mode that applies Socratic dialogue to ambiguous requirements. This explores options and decisions interactively, optionally generating a CONTEXT.md file to capture the refined direction and constraints before implementation.

When do I need to run ideation and domain classification for product management?

You need ideation and domain classification when you have ambiguous features or requirements requiring exploration and option comparison. It produces a recommended direction and locked decisions, enabling smoother handoffs to planning before implementation begins.