Menu
Use at session start or before deciding how SpecPowers should shape a task. Routes work into the small core workflow set.
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
Use before saying work is complete, fixed, passing, approved, ready, or safe to hand off.
Define behavior and architecture before edits when a change is user-visible, risky, or not yet bounded.
Compact engineering rules for implementation and review when the repository has no stronger local guidance.
Implement an accepted or clear change with minimal diff, direct verification, and no compatibility wrappers unless required by the contract.
Read-only investigation for unclear requests, bug reports, failures, architecture questions, or project health checks.
Install, repair, package, or verify the SpecPowers plugin and its generated payloads.
| name | using-specpowers |
| description | Use at session start or before deciding how SpecPowers should shape a task. Routes work into the small core workflow set. |
SpecPowers is a lightweight operating model for coding agents. Its job is to choose the right work mode, keep the interface small, and prevent unsupported claims. It is not a ceremony generator.
Route the task first. Do not load multiple workflow skills unless the selected mode reaches a point that needs them.
Choose exactly one primary mode:
| Mode | Use When | Skill |
|---|---|---|
| Direct answer | The user asks for explanation, judgment, or advice and no repository action is needed. | none |
| Read-only investigation | The user reports a bug, asks what is wrong, or scope is unclear. | investigate |
| Define a change | User-visible behavior, public contract, or architecture must be decided before edits. | define-change |
| Execute a change | Scope and expected behavior are clear enough to edit. | execute-change |
| Review a change | The user asks for review, merge readiness, or a second opinion on a diff. | review-change |
| Operate plugin | The user asks to install, repair, package, or verify the SpecPowers plugin itself. | operate-plugin |
claim-gate is not a primary mode. Use it before claiming work is complete,
fixed, passing, approved, merge-ready, or safely handed off.
engineering-rules is not a primary mode. Use it while writing or reviewing
code when the repository does not provide stronger local rules.
Use artifact scale only inside define-change or execute-change:
| Scale | When | Required Artifact |
|---|---|---|
| S | Small, local, low-risk work. | Inline contract and verification notes. |
| M | Normal feature or bug fix with visible behavior. | Short change note with scenarios and affected files. |
| L | Cross-module, high-risk, or ambiguous work. | File-backed change brief with scenarios, design choices, and tasks. |
Before any completion claim:
claim-gate.