菜单
Defines where to save work-in-progress artifacts (design, plan, research, temporary files) so output paths stay consistent. Use when saving a design, plan, research note, or temp script, or when running /deep-read, /write-plan, or superpowers (brainstorming/writing-plans).
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use for GitHub operations: creating issues, posting issue comments, creating draft PRs, and adding PR review comments.
Facilitate structured divergent idea generation using the SCAMPER technique (Bob Eberle). An orchestrator elicits a concrete target, applies seven transformation lenses (Substitute, Combine, Adapt, Modify, Put to another use, Eliminate, Reverse) in parallel via focused subagents, then converges into evaluated, prioritized ideas. Use when the user asks for a SCAMPER analysis, systematic ideation, or improvement ideas for an existing product, service, process, or idea.
Facilitate structured multi-perspective analysis using Edward de Bono's Six Thinking Hats. A Blue Hat orchestrator applies one hat at a time in sequence over a single shared record, using five focused hat subagents. Use when the user asks for a Six Hats or 6 hat analysis, a multi-perspective breakdown of a decision, idea, or problem, or systematic structured thinking on a topic.
Author markmap-format Markdown. Use when writing a mindmap (マインドマップ / markmap) in Markdown.
Sample skill for verifying plugin wiring. Trigger when the user asks to run the sample greeting or test the sample plugin.
Use when resolving or addressing PR review comments.
| name | save-conventions |
| description | Defines where to save work-in-progress artifacts (design, plan, research, temporary files) so output paths stay consistent. Use when saving a design, plan, research note, or temp script, or when running /deep-read, /write-plan, or superpowers (brainstorming/writing-plans). |
Save work-in-progress artifacts to consistent locations. Without these rules, output paths drift across the existing folder structure each time.
| Directory | Purpose |
|---|---|
docs/adr/ | Architecture Decision Records |
docs/design/ | System-wide specs and design docs (not per-feature implementation design) |
docs/reports/ | Research notes, plans, and other work-in-progress artifacts |
docs/tmp/ | Disposable scripts and scratch output |
| Tool | Output path |
|---|---|
| superpowers (design) | docs/superpowers/specs/YYYY-MM-DD-{topic}-design.md |
| superpowers (plan) | docs/superpowers/plans/YYYY-MM-DD-{topic}.md |
/deep-read | docs/reports/YYYY-MM-DD-{topic}-research-{small-topic}.md |
/write-plan | docs/reports/YYYY-MM-DD-{topic}-plan.md |
YYYY-MM-DD is today's date; {topic} is the work subject in kebab-case.
Always include both so parallel work stays distinguishable.docs/reports/. Follow
superpowers' own default directories (docs/superpowers/specs/,
docs/superpowers/plans/). State this explicitly because, without it,
superpowers picks a different location each time.