Skip to content

hashgraph-online/awesome-codex-plugins / plugins/boshu2/agentops/skills/rpi

Drive 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.

FileKindSize
SKILL.mdskill md9.1 KB
references/boundaries.mdmarkdown3.9 KB
references/outer-goal.mdmarkdown1.5 KB

references/outer-goal.md

View on GitHub
# Optional outer goal

Use this reference only when the caller explicitly selected a sustained goal or
several outcomes. The native caller/controller keeps work selection, aggregate
budgets, stops and delivery authority. No AO scheduler, new command or goal
ledger is required. The RPI charter already owns a single authorized outcome
through finish; an outer goal is not permission needed for ordinary repair.

A crafted goal orchestrates many RPIs over one bead graph.
[Craft Goal](../../craft-goal/SKILL.md) writes and lints the frozen goal prompt;
[Navigate](../../navigate/SKILL.md) is the graph walk the goal applies each
wave. The goal still selects work, and neither adds a scheduler or a ledger.

Carry accepted terminal outcome and scope, measured remaining allowance and the
current causal incident in the native work/handoff source. Choose the smallest
acceptance-advancing action or consequential uncertainty. Reserve capacity for
integration, required repairs, a fresh judgment where one is warranted and a useful handoff before
spending the whole allowance on discovery or reviews.

Apply the charter's [causal-stall rule](../SKILL.md#causal-stall-and-bounds) to
a genuine stall: a repeated wakeup, new context or renamed finding is not a new
incident, and native blocked-status thresholds are bookkeeping, not permission
to renew time, cost, quota or helper use.

No objective text, saved plan or simulated stop proves aggregate runtime
enforcement. Stricter host or user helper and stopping rules still apply; this
guide does not override them.
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 implementationStars: 322kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 322kUpdated Claude CodeCodexVerifiedInstall
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 fallbackStars: 322kUpdated Claude CodeCodexVerifiedInstall
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 alwaysStars: 322kUpdated Claude CodeCodexVerifiedInstall