brainstorming

Transform informal ideas into validated design specifications with dated design documents.

Updated Apr 17, 2026
One-click install
npx skills add https://github.com/Chris-Maskey/opencode-config --skill brainstorming-chris-maskey
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/Chris-Maskey/opencode-config/tree/main/skills/brainstorming
Command: npx skills add https://github.com/Chris-Maskey/opencode-config --skill brainstorming-chris-maskey

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents premature implementation by forcing structured exploration of user intent, constraints, and success criteria so that work starts from a validated design rather than assumptions.

Core Features & Use Cases

  • Context exploration: Directs the agent to review project files, docs, and recent commits to ground the conversation in the current codebase.
  • Guided clarification: Asks one clarifying question at a time to surface constraints, priorities, and acceptance criteria.
  • Approach comparison & gated approval: Proposes 2-3 approaches with trade-offs, presents a recommended design, obtains user approval, writes a dated design doc to docs/plans, and then transitions to implementation planning.
  • Use Case: When adding a new component or feature, use this Skill to define scope, pick an approach, and produce a short approved design before any code is written.

Quick Start

Use the brainstorming skill to explore the new login flow idea by asking one clarifying question about user goals and constraints.

Frequently Asked Questions about brainstorming

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

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

To turn informal ideas into validated design specifications, use a guided brainstorming process that explores project context, asks clarifying questions, proposes 2-3 approaches with trade-offs, and requires user approval before writing a dated design document.

What is the best way to prevent premature implementation when adding a new feature?

The best way to prevent premature implementation is to enforce a gated design exploration process that defines scope, identifies constraints, and produces an approved design document before any code is written.

How do I create a design document for a new component or behavior change?

To create a design document, the agent reviews project files and recent commits, asks clarifying questions one at a time, compares approaches, and writes the final approved design to the docs/plans directory.

Does the brainstorming process require user approval before writing the design doc?

Yes, the brainstorming process requires gated user approval. It presents a recommended design from 2-3 proposed approaches, obtains explicit user approval, and then writes the dated design document.

Can I transition directly from design validation to implementation planning?

Yes, you can transition directly from design validation to implementation planning. After writing the approved design document to docs/plans, the process invokes the writing-plans skill to handle the transition to implementation.