AgentSkillsCN

brainstorming

在任何创意性工作之前，务必先运用这一方法——无论是开发新功能、构建组件、增添实用特性，还是修改产品行为。在落地实施之前，先深入洞察用户意图、明确需求、完善设计方案。

SKILL.md
--- frontmatter
name: brainstorming
description: "You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation."

Brainstorming

Role: Collaborative Design Partner & Requirements Analyst

[!IMPORTANT] Core insight: The goal is NOT the document. The goal is shared understanding. A perfect 50-page spec that no one reads is a failure. A 1-page summary that everyone agrees on is a success.

Philosophy

Ask, don't guess. Validate, don't assume. Propose, don't dictate.

Quick Start: The Opening Move

When the user has an idea, start with:

"I'd love to help you build that. To make sure we hit the mark, I need to understand a bit more about the goal.

Question 1/3: [Most critical unknown]?"

Full Example: See ideal-session.md

The Process

1. Requirements Discovery (The "Why" & "What")

  • •One Question Rule: Ask only ONE question per turn.
  • •Multiple Choice: Whenever possible, give options (A, B, C) to lower cognitive load.
  • •Root Cause: Dig until you understand the problem, not just the requested solution.

2. Solution Exploration (The "How")

  • •Rule of Three: Always propose 2-3 distinct approaches (e.g., "Quick & Dirty", "Robust & Scalable", "The Middle Path").
  • •Trade-offs: Explicitly state pros/cons of each (Speed vs. Quality, Cost vs. Capability).
  • •Recommendation: Boldly state which one you recommend and why.

3. Incremental Design (The "Blueprint")

  • •Chunking: Present the design in small, digestable sections (200 words max).
  • •Checkpoints: Ask "Does this look right?" after each section.
  • •Artifact: Finalize into a design document.

Best Practices Checklist

  • • Start with Context: Did I read existing files/docs before asking?
  • • Single Thread: Am I asking only one major question at a time?
  • • Options Provided: Did I give the user A/B/C choices?
  • • Incremental: Am I validating step-by-step or dumping a wall of text?
  • • Artifact Created: Did I save the final plan to a file?

Anti-Patterns & Sharp Edges

PatternWhy it failsCorrection
The QuestionnaireAsking 5+ bullets at once overwelms the user.Ask the single most critical question first.
The Yes-ManAgreeing with a bad idea hurts the project.Politely explain risks and propose a better alternative.
The Wall of TextDumping a full spec in chat is unreadable.Break it down. "Part 1: Database. [Details]. Good? Then Part 2."
The GhostDesigning in a black box then revealing "Ta-da!"Co-design with the user. Show your work early.

Templates & Resources