brainstorming

Guide teams through clarifying questions and design options before implementation.

30|2|Updated Mar 3, 2022
One-click install
npx skills add https://github.com/lie5860/ak-guess --skill brainstorming-lie5860
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/lie5860/ak-guess/tree/main/.agents/skills/brainstorming
Command: npx skills add https://github.com/lie5860/ak-guess --skill brainstorming-lie5860

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

在开始实现前,系统地发现并澄清目标、约束和成功标准,从而避免走偏或返工。

Core Features & Use Cases

  • 探索项目上下文:分析文件、文档与最近提交,理解背景。
  • 提出澄清问题与 2-3 种方案:逐条提问,给出权衡和推荐。
  • 展示设计并获取批准:以分节的设计输出,便于迭代。
  • 生成设计文档并自检:将规格写入文档并进行一致性与范围校验。

Quick Start

Describe the project context, then begin by asking clarifying questions and proposing two design options for approval.

Frequently Asked Questions about brainstorming

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

FAQPage Schema
How do I clarify design requirements and explore user intent before coding?

To explore project context before implementation, analyze existing files, documentation, and recent commits. This context gathering ensures proposed design options align with actual constraints and success criteria, preventing costly rework later in the development cycle.

What is the best way to present design proposals for team approval?

To generate a design document after brainstorming, write the finalized specifications into a structured doc and perform automated consistency and scope checks. This self-validation ensures the approved design is coherent and ready for implementation planning.

Can I use this brainstorming approach for diverse project contexts?

You should use this design brainstorming process when you need to systematically discover goals, constraints, and success criteria before implementation. It enforces process guardrails to prevent premature coding and culminates in a formal, self-checked design document.

Why does starting implementation without a design specification lead to rework?

Limitations of brainstorming without process guardrails include premature coding and uncontrolled scope creep. Without a formal design document and approval step, teams risk building solutions that fail to meet actual user intent or project constraints.