brainstorming

分类: 内容与多媒体 | 上传者: Plumess | 下载: 0 | 版本: v1.0（最新）

Use when the user explicitly requests brainstorming, design exploration, or structured ideation — e.g. /brainstorm, 'let's brainstorm', 'help me design'. NOT auto-triggered in general conversation.

更新日志: Source: GitHub https://github.com/Plumess/plume-skills

目录结构

当前层级: skills/brainstorming-universal/

📄 SKILL.md 1.4 KB

SKILL.md

---
name: brainstorming
description: "Use when the user explicitly requests brainstorming, design exploration, or structured ideation — e.g. /brainstorm, 'let's brainstorm', 'help me design'. NOT auto-triggered in general conversation."
---

<PLUME-OVERRIDE>
The following directives take priority over the vendor skill. Anything not mentioned here follows the vendor skill as-is.

- **Activation**: This is the universal (non-project) version. Only activate when the user explicitly asks.
- **Locale**: Read `$PLUME_ROOT/config.yml` → `locale.language`. Write spec documents in this language. Timestamps use `locale.timezone`.
- **Output path**: `$PLUME_ROOT/data/<slug>/specs/YYYY-MM-DD-<topic>-design.md`
  - `<slug>` = current working directory with leading `/` removed, `/` replaced by `-`
  - `PLUME_ROOT` from `[PLUME_ROOT: ...]` in session context
  - Create `specs/` directory if it doesn't exist
  - Do NOT write to `docs/superpowers/` or `docs/plume/`
- **Gate**: After spec review is complete: STOP and wait for explicit user approval.
</PLUME-OVERRIDE>

Now read and follow the vendor skill's complete content:

1. Use the Read tool to read: `PLUME_ROOT/vendor/superpowers/brainstorming/SKILL.md` (replace PLUME_ROOT with the path from `[PLUME_ROOT: ...]` in your session context)
2. Follow all instructions in that file
3. Where the vendor skill conflicts with `<PLUME-OVERRIDE>` above, the override wins
4. Everything else: follow the vendor skill exactly

登录后下载/点赞/收藏 ❤ 2 | ★ 0

brainstorming

目录结构

SKILL.md

举报内容

提示