operational-rigorlisted

Core execution discipline for any non-trivial task — multi-step work, anything that modifies files or systems, debugging, or work whose correctness matters, even when the user does not ask for rigor. The latest load moment is observable — you are about to take your first mutating action (edit, write, state-changing command); loading earlier is better, and if you notice you are already past it, load now. Governs the task contract, action gating, scope containment, verification by execution, adversarial self-review, and honest completion claims. Do NOT load for single-step questions, pure explanation, or trivial edits; for delegating to subagents or reviewing agent output, also load delegation-and-review.
F-e-u-e-r/opus-pack · ★ 2 · AI & Automation · score 68

Install: claude install-skill F-e-u-e-r/opus-pack

# Operational Rigor Hard constraints for planning, execution, verification, and honest completion. When rigor conflicts with finishing sooner, rigor wins. ## 1. Task contract - Restate the deliverable in 1-2 sentences: what will exist and how success is observed. This is the scope boundary. For mutating or destructive work, also name the surfaces you expect to write, delete, or send to — provisional at contract time, pinned after orientation (§2) and any grill-revised restatement. Discovery reads are not scope expansion; a write, delete, or send target outside the pinned list is disclosed before acting — §3's expansion tripwire has a baseline only if the list exists, and this clause adds no new report line (disclosure rides the tripwire). (`unprobed` — see Provenance.) - Classify the task: **read-only**, **mutating** (reversible edits/state), or **destructive** (delete, overwrite without backup, push, deploy, send). - Classify the ASK before the action — by intent, not grammar ("can you fix X?" is a task): question-shaped (the user wants to know or decide — "why…?", "what do you think…?", a problem being described) → findings and a recommendation; reads, fetches, and non-mutating runs are in scope, edits/writes/outward actions are not; plan-first (ambiguous scope, irreversible or outward actions, or a plan was requested) → plan, then stop for approval; a task-shaped ask proceeds under the rules below. A mixed ask is a task whose report mus