hashgraph-online/awesome-codex-plugins / plugins/boshu2/agentops/skills/rpi
rpi
UnverifiedDrive one accepted change through implementation and checks to done, with one fresh review only where a mistake is costly. Use when: asked to run or orchestrate work through RPI.
RPI
Own the authorized outcome through finish. RPI (research, plan, implement) is one native pass, not fixed phases: use the native coding agent and shell. BD or the caller's tracker owns work and handoffs; Git owns content and delivery. AgentOps supplies a small charter and one fresh judgment where a mistake is costly, not a scheduler.
Operating charter
- Use the existing accepted outcome, scope and real bounds. A clear change needs no Plan, Recall or Learn worksheet. Resolve uncertainty only when it could change the implementation or acceptance decision.
- Take the smallest acceptance-advancing action. Plan runs only when intent is missing, an uncertainty is consequential or evidence disproves the approach. Once an implementer can act and a validator can judge, implement; do not keep improving the plan. Approach revisions preserve acceptance and authorized scope. Acceptance changes need caller authority.
- Implement and repair ordinary known defects directly. A known test failure needs a fix and a discriminating check, not another planning phase, council or helper.
- Use focused checks during edits and complete required integration checks before finishing. Reuse a check result only while its inputs are unchanged; rerun affected checks after changes. Reserve capacity for integration and repair. Keep a subject unchanged while it is being judged.
- Spend validation where a mistake is costly. For an ordinary change the checks and CI are the gate: finish. Obtain Validate from one fresh author-distinct context only when the caller asks, when a mistake cannot be cheaply undone after it lands (a published release or instructions users will follow, a security boundary, destroying data or tracker state, deleting a check that protects the product), or when no deterministic check covers the changed behavior. Use the author's model family unless the caller selects additional legs; explicitly required reviewers remain required.
- One round. Give the validator the accepted criteria, the exact subject and
one question written before it starts, never the author's confidence or
desired verdict; it does not re-run the checks. Repair what fails the
accepted behavior or would mislead a user, break install or the CLI, or
remove protection for the product; treat the rest as optional notes. Confirm
each repair with a check and finish. A repair does not start another
review, and
NOT_PROVENis reported with its gaps, not chased. Keep review cost a fraction of the cost of the work; when it approaches that cost, stop and report what is unchecked. - Stop at completed acceptance, cancellation, refusal, a spent real bound, a
pending caller decision or an unresolved causal stall after the help below.
A choice the accepted outcome depends on that lies outside existing
authority (changed acceptance, wider scope, an irreversible step it does not
cover) is the caller's decision, not a stall, so no helper applies. Finish
the independent authorized work, then stop and return the choice instead of
waiting on it, handed over in full: what raised it, what you found, the
options with their tradeoffs and your recommendation. A count or a link is
not a handover, and the result is never
donewhile a choice is open. Adjacent improvements are not permission to expand the goal. Report them briefly only when useful; do not turn them into another work batch.
Delegation and handoffs
When delegation is authorized and useful, select the runtime's task-only
dispatch option for independent work: a short prompt in a full-history fork
still carries the full history, and prompt wording proves neither isolation nor
a smaller inherited context. Supply accepted intent and scope, the exact
subject, relevant evidence, remaining bounds, the result's consumer and check
ownership; resume an author for direct repair when useful. At completion,
verify the expected subject and required results; a quiet or partial status is
not success. Integrate as Implement's
delegated work describes, carrying each worker's not_as_briefed and gaps lines into
the closeout below.
Causal stall and bounds
Name a stall by what you observed, never by a count:
- Unknown cause: a check fails and neither its output nor the diff points to a change or assumption you can name.
- Recurrence: a check that passed after a repair fails again for the same cause.
- No progress: the failing check's output and the diff are unchanged since the previous attempt, or a delegated worker's last observed activity has not changed since you last looked.
- Wrong objective: a caller correction, or a check of the accepted example, shows the work aims at something acceptance does not ask for.
Any of the four admits at most one bounded fresh helper for that incident within authority and bounds; if it stays unresolved, the stalled Result names its observed fact. Give it the failed assumption, evidence and one discriminating question. Resume only with a different testable approach; an unhelpful answer ends the attempt. Do not chain helpers or rename the incident. Known failures get direct repair. Cancellation, refusal and spent hard time/cost/quota skip help.
Respect actual caller/native limits, including explicit repair-round bounds. Retries, compaction, helpers and new subjects never renew them; retry count alone is not a spent budget, and prompt text proves no native enforcement. If interruption threatens evidence, preserve accepted intent, exact subject, check results, unresolved cause, bounds and helper use in the native handoff. Outer-goal guidance remains optional.
Evidence and boundaries
When a validator is used, bind accepted intent, complete changed paths, the
exact subject and its check results using
Validate's Subject rules, including its status
listing and file hashes for uncommitted work.
Where the repository records AgentOps evidence bindings, run the orphaned-evidence
scan Implement step 6 details; without ao,
list the scan under Not checked. Requested proof goes to protected storage outside
Git that the caller selects; preserve legacy .agents/ evidence. Validate's
decision order sets a requested binding verdict, which the author cannot issue.
Memory, specialists and runtime adapters are on demand; no-match and no-change are valid. Read boundaries when authority, scope, evidence or delivery is at issue. Do not invent a runtime, hidden machine artifact or workflow to finish an ordinary change.
Closeout
Report in this shape. Plans, activity, reviews and saved pages earn no
capability credit, and an unchecked item is reported, not a reason to keep
validating. The report is the result; create no machine artifact for it. A
persisted verdict, when a caller or declared consumer requires one, is
Validate's verdict.v2.
Result: done | stopped: <cancelled | refused | needs decision: <choice> | bound spent | stalled: <unknown cause | recurrence | no progress | wrong objective> - <observed fact>> | NOT_PLANNED | NOT_BUILT
Subject: <commit, branch or diff identity>
Acceptance: <criterion> -> <evidence: check, receipt or ref>, one line each
Checked: <checks run on the final subject, with results>
Not checked: <what was not run or not covered, and why> | none
Judgment: none (checks and CI gate an ordinary change) | <validator context id>: PASS | FAIL | NOT_PROVEN
Not as briefed: <steps refused, held, worked around or unverified, and departures from the literal ask, one line with its reason each> | none
Limits: <gaps: material missing evidence and known failures; each open decision in full; adjacent work noticed but not done> | none
A departure is a call made within authority that the caller would want to know: building differently than asked, declining or disputing a finding, or following a mid-run steer. Routine fixes stay out; with no such call, add none.
NOT_PLANNED (stopped before an actionable slice existed) and NOT_BUILT
(stopped before a candidate change existed) describe progress, not semantic
verdicts.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 318k | Updated | Claude CodeCodex | Unverified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 318k | Updated | Claude CodeCodex | Unverified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 318k | Updated | Claude CodeCodex | Unverified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 318k | Updated | Claude CodeCodex | Unverified | Install |