Menu
Consult directly matching task playbooks before substantial design, debugging, implementation, review, or completion work without forcing full workflow execution.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Consult after receiving review feedback and before implementation when the feedback needs evidence-based evaluation.
Consult before delegating implementation when an approved plan benefits from worker context isolation and durable coordination.
Consult before attempting a fix when root cause or behavior is unclear, failures repeat, components interact, or guessing would be unsafe.
Consult before implementing an observable behavior change when a meaningful automated test seam exists; use proportional red-green evidence.
Consult before making a substantive completion claim; require current trustworthy evidence and semantic acceptance.
Consult when multi-round implementation, context compaction, or worker handoff requires a durable execution contract.
| name | using-superpowers |
| description | Consult directly matching task playbooks before substantial design, debugging, implementation, review, or completion work without forcing full workflow execution. |
Skills are task-specific playbooks. Explicit user invocation of a skill is binding.
Before substantial design, investigation, debugging, implementation, review, or completion work, inspect the available skills. If a skill directly matches the task type, load it before acting.
Loading a skill means consulting its guidance, not following every step verbatim. Apply the parts relevant to the task; exact step-by-step execution is not mandatory unless the skill explicitly marks a safety, permission, or verification gate as binding.
Start with at most one primary workflow skill. Load another only when the task enters a distinct phase or a separate risk boundary requires it.
Direct questions, narrow lookups, and bounded low-risk mechanical changes may proceed without loading a workflow skill.
These are task-type matches, not a fixed sequence.
Workers executing a bounded delegated task use the supplied task contract. They do not need to re-run this session-start selection step unless the task itself requires a safety, verification, or other specialized workflow.
If your harness appears here, read its reference file for tool translation only:
references/codex-tools.mdreferences/pi-tools.mdreferences/antigravity-tools.mdDirect user instructions, repository instructions, and project policy take precedence over this skill. Preserve user authority at approval, permission, and repository-operation boundaries.