메뉴
Use before implementing new behavior, refactors with meaningful design choices, or changes that alter user-visible behavior. Clarify intent, propose approaches, write a short spec, and only then transition to planning.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, update or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
Local fallback entrypoint for the Superpowers plugin. Use when the user mentions Superpowers, the plugin is unavailable, or you need to route non-trivial engineering work in this repository into the local brainstorming, planning, debugging, and verification skills.
Use when a written plan exists and implementation should proceed in small validated slices. Carry out one plan slice at a time, keep scope tight, validate immediately after edits, and do not drift away from the approved plan without calling it out.
Use for bugs, regressions, failing tests, broken scripts, or mismatches between expected and actual behavior. Start from a concrete anchor, form one falsifiable local hypothesis, make a small grounded fix, and validate immediately.
Use when starting non-trivial engineering work in this repository, when the user mentions Superpowers, or when the plugin is unavailable and you need to route the task into the local skill suite before acting.
Use when about to claim something is fixed, complete, passing, reviewed, or ready. Require fresh command output and report the observed result rather than the intended result.
| name | brainstorming |
| description | Use before implementing new behavior, refactors with meaningful design choices, or changes that alter user-visible behavior. Clarify intent, propose approaches, write a short spec, and only then transition to planning. |
Use this skill for design work before implementation.
writing-plans.The spec should be short and operational, not aspirational.
Include:
If the task is truly small, the spec can still be brief. The point is to make the intended behavior explicit before code changes.
Use the scaffold when it saves time:
bash .claude/skills/superpowerz/scripts/new_spec.sh feature-slug "Short Feature Title"
Default location:
tmp/superpowerz/specs/YYYY-MM-DD-feature-slug.md
Prefer the smallest design that satisfies the requirement and preserves repository invariants.
Do not broaden scope with unrelated cleanup unless the current task cannot be done safely without it.
Do not move to implementation directly from ambiguity.
Exit this skill by routing into .claude/skills/writing-plans/SKILL.md once the design is clear enough to slice into implementation work.
After planning is complete, route into .claude/skills/executing-plans/SKILL.md rather than improvising execution.