القائمة
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.
التثبيت باستخدام 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 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 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.
| name | verification-before-completion |
| description | 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. |
Evidence before claims.
Do not claim success without fresh verification that directly supports the claim.
Before saying work is done, fixed, clean, or ready:
bash -n path/to/script.sh succeeded.pytest tests/check_release_installability.py -q passed.get_errors still reports these files.Prefer the most behavior-scoped check available:
git diff is not a substitute for executable validation when executable validation exists.
Completion language is allowed only after the verification step has been run and its output actually supports the claim.