brainstorm

Generate and evaluate design options before implementation.

1|Updated Feb 15, 2026
One-click install
npx skills add https://github.com/n0rvyn/indie-toolkit --skill brainstorm-n0rvyn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brainstorm
Source: https://github.com/n0rvyn/indie-toolkit/tree/main/dev-workflow/skills/brainstorm
Command: npx skills add https://github.com/n0rvyn/indie-toolkit --skill brainstorm-n0rvyn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Facilitates early-stage design by generating and evaluating multiple design options before implementation, preventing premature coding and misaligned scope.

Core Features & Use Cases

  • Structured ideation: define context, extract constraints, and propose 2-3 design options with trade-offs.
  • One-question-at-a-time clarifications: elicit user requirements through a controlled interview loop.
  • Incremental design delivery: present options and progress through sections, awaiting user approval before moving forward.
  • Design artifacts: output a formal design document saved to docs/06-plans/ and, when needed, capture user journeys and UX assertions for user-visible features.

Quick Start

Provide a project brief and request 2–3 design options with trade-offs to start the brainstorming session.

Frequently Asked Questions about brainstorm

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

FAQPage Schema
How do I generate and evaluate multiple design options before implementation?

To generate design options before implementation, provide a project brief to initiate a structured ideation session. The tool extracts constraints and proposes 2-3 options with trade-offs, preventing premature coding and misaligned scope.

How do I scope early-stage product features without premature coding?

Scope early-stage product features by enforcing a design-before-implementation gate. The tool elicits requirements through a one-question-at-a-time interview loop, then delivers incremental design sections awaiting your approval before moving forward.

Can I capture user journeys and UX assertions for product design?

Yes, you can capture user journeys and UX assertions for user-visible features. When applicable, the design validation process includes these artifacts alongside the structured design document output.

What's the best way to document architecture decisions and design trade-offs?

Document architecture decisions by outputting a formal design document saved to the docs/06-plans directory. This document captures the evaluated design options, constraints, and trade-offs discussed during the ideation session.

Does this ideation process support incremental design delivery?

Yes, the ideation process supports incremental design delivery. It presents design options and progresses through sections one at a time, explicitly awaiting user approval before moving forward to the next part of the design.

When do I need a structured design document for feature scoping?

You need a structured design document for feature scoping when making early-stage architecture decisions across projects and teams. It formalizes context, constraints, and trade-offs to prevent misaligned scope before implementation begins.