ce:brainstorm

仓库创建 2026年6月29日最近提交 22 天前SkillHot 收录 22 天前

▸ 精选理由

将脑暴结果结构化为可复用的需求文档，便于交接与实施。

这个 Skill 做什么

通过协作对话产出面向实现的需求文档和设计要点。

用对话式协作把想法推进成可落地的需求文档和设计要点，先讨论范围和方案再出轻量级 PRD。当你有模糊需求、想头脑风暴功能选项或不确定实现路径时用，能把讨论结果结构化为开发可用的需求。重点是先搞清要做什么和为什么，再交接给实现环节，避免边做边改。

▸ 展开 SKILL.md 英文原文

Explore requirements and approaches through collaborative dialogue before writing a right-sized requirements document and planning implementation. Use for feature ideas, problem framing, when the user says 'let's brainstorm', or when they want to think through options before deciding what to build. Also use when a user describes a vague or ambitious feature request, asks 'what should we build', 'help me think through X', presents a problem with multiple valid solutions, or seems unsure about scope or direction — even if they don't explicitly ask to brainstorm.

开发编程需求分析方案设计文档化通用

Stars

Forks

仓库内 Skill

7 日增星

安装 / 使用

给你的 Agent 一句话（通用）

帮我安装这个 skill：https://raw.githubusercontent.com/MaximoCorrea1/ultra-powers/main/flows/ultra-powers/skills/ce-brainstorm/SKILL.md

或 curl 直取 SKILL.md

curl -fsSL "https://raw.githubusercontent.com/MaximoCorrea1/ultra-powers/main/flows/ultra-powers/skills/ce-brainstorm/SKILL.md"

SKILL.MD 节选查看完整文件 ↗

# Brainstorm a Feature or Improvement

**Note: The current year is 2026.** Use this when dating requirements documents.

Brainstorming helps answer **WHAT** to build through collaborative dialogue. It precedes `/ce:plan`, which answers **HOW** to build it.

The durable output of this workflow is a **requirements document**. In other workflows this might be called a lightweight PRD or feature brief. In compound engineering, keep the workflow name `brainstorm`, but make the written artifact strong enough that planning does not need to invent product behavior, scope boundaries, or success criteria.

This skill does not implement code. It explores, clarifies, and documents decisions for later pl

via SKILL·HOT · 数据来自 GitHub 公开信息 · 原文版权归作者所有