brainstorm

Guides collaborative requirements discovery and PRD creation before AI coding implementation.

Updated Mar 24, 2026
One-click install
npx skills add https://github.com/yizhitangtongxue/opencode-switch --skill brainstorm-yizhitangtongxue
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: brainstorm
Source: https://github.com/yizhitangtongxue/opencode-switch/tree/main/.agents/skills/brainstorm
Command: npx skills add https://github.com/yizhitangtongxue/opencode-switch --skill brainstorm-yizhitangtongxue

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Jumping straight into coding with unclear requirements leads to rework, scope creep, and misaligned implementations. This Skill structures the pre-implementation phase by guiding AI through requirements discovery, research, and PRD documentation before any code is written. ## Core Features & Use Cases - Task-First Capture: Immediately creates a task directory and seeds a PRD so ideas are recorded from the first message. - Action-Before-Asking: Inspects the repo, docs, and configs to derive answers automatically, asking only blocking or preference questions one at a time. - Research-First Technical Choices: Compares 2-4 similar tools or patterns and proposes concrete approaches with trade-offs before asking for a decision. - Diverge-Converge Workflow: Expands thinking across future evolution, related scenarios, and edge cases, then locks an MVP with explicit out-of-scope items. - Use Case: When a user says "add a plugin switching command to my CLI tool", the Skill creates a task, inspects the repo, researches CLI conventions, presents 2-3 approaches, and converges on a confirmed PRD with acceptance criteria before implementation begins. ## Quick Start Ask the AI to brainstorm requirements for your next feature idea before writing any code, and it will create a task, research options, and produce a confirmed PRD.

Frequently Asked Questions about brainstorm

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

FAQPage Schema
How do I gather requirements before starting an AI coding task?▼

Start by creating a task and seeding a PRD with everything already known, then inspect the repository and docs to derive answers automatically. Ask only blocking or preference questions, one per message, and update the PRD after each answer until requirements converge.

What is a PRD and how do I write one for a coding task?▼

A PRD (Product Requirements Document) captures the goal, requirements, acceptance criteria, definition of done, out-of-scope items, and technical notes for a task. This Skill seeds the PRD immediately and evolves it through Q&A until a final confirmation is approved.

How should AI choose between multiple implementation approaches?▼

Use a research-first approach: identify 2-4 comparable tools or patterns, summarize their conventions, map them to repo constraints, then present 2-3 concrete approaches with pros and cons. Ask the user a single preference question and record the outcome as an ADR-lite decision.

When should brainstorming be skipped for a coding task?▼

Skip brainstorming for trivial changes like single-line fixes or typos, and implement directly. For simple tasks with a clear goal and 1-2 files, ask one confirmation question then proceed; full brainstorming is reserved for complex, ambiguous, or architectural work.

What questions should be avoided during requirements discovery?▼

Avoid meta questions like "should I search?" or asking users to paste code that exists in the repo. Also avoid asking users to pick an approach before presenting concrete options, and never ask multiple questions in a single message.