brainstorming

Turn nascent ideas into validated design specifications through guided iterative questioning.

Updated Aug 30, 2025
One-click install
npx skills add https://github.com/vonomarap/kanokna --skill brainstorming-vonomarap
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/vonomarap/kanokna/tree/main/.agents/skills/brainstorming
Command: npx skills add https://github.com/vonomarap/kanokna --skill brainstorming-vonomarap

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams and makers often jump to implementation without clarifying purpose, constraints, or success criteria, which leads to rework, misaligned expectations, and wasted effort. This Skill guides collaborative exploration to ensure ideas are well-formed, feasible, and ready for specification before development begins.

Core Features & Use Cases

  • Guided iterative questioning: ask one clarifying question at a time, preferring multiple-choice when possible to quickly converge on intent.
  • Explore 2-3 approaches with trade-offs and lead with a recommended option to speed decision-making.
  • Incremental design presentation: deliver design content in 200-300 word sections covering architecture, components, data flow, error handling, and testing, validating after each section.
  • Outputs and follow-through: author a dated design document at docs/plans/YYYY-MM-DD-<topic>-design.md and support transitioning to implementation planning and git workflows.

Quick Start

Begin by describing the feature idea, context, constraints, and success criteria, then request the first clarifying question.

Frequently Asked Questions about brainstorming

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

FAQPage Schema
How do I turn rough feature ideas into validated design specifications?

To turn rough ideas into validated design specifications, you can use a guided iterative workflow that applies one-question-at-a-time clarification to explore 2-3 approaches with trade-offs before finalizing requirements.

What is the best way to structure pre-implementation specifications for engineering planning?

The best way to structure pre-implementation specifications is by delivering incremental 200-300 word design sections covering architecture, data flow, and error handling, validating each section before moving forward.

How does guided iterative questioning work for product ideation and feature design?

Guided iterative questioning works for product ideation by asking one clarifying question at a time, preferring multiple-choice formats to quickly converge on intent and explore feasible approaches.

Can I generate a dated markdown design document ready for git commit from a brainstorming session?

Yes, you can generate a dated markdown design document ready for git commit automatically at docs/plans/YYYY-MM-DD-<topic>-design.md after completing the collaborative exploration and validation phases.

Does this approach work for UX flows and architecture sketches or just product requirements?

This approach works for UX flows and architecture sketches alongside product requirements, applying guided iterative questioning to ensure ideas are feasible and ready for specification across various engineering planning sessions.

When should I not use an iterative design specification workflow for ideation?

You should not use an iterative design specification workflow when immediate implementation is required without clarifying purpose, constraints, or success criteria, as the step-by-step validation process prioritizes thorough alignment over rapid execution.