Kartik-Doye/Ravengard-AI-Recruiter / .agents/skills/pilot
pilot
VerifiedImplements an approved plan one coherent slice at a time with fresh inspection, risk-appropriate verification, diff review, and clean handoff state. Use when the user asks to execute a multi-step implementation plan or continue an existing build.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 9.4 KB |
| references/completion-gate.md | markdown | 2.3 KB |
| references/execution-protocol.md | markdown | 1.3 KB |
| references/research.md | markdown | 797 B |
references/execution-protocol.md
View on GitHub# Execution protocol: one verified slice at a time
Use this reference for medium or high-risk work, deviations, failures, or an
interrupted implementation. Low-risk slices can use entrypoint loop.
## Slice record
Record outcome, current evidence, files touched, protected invariants,
verification, recovery path, deviations, and status: done, blocked, deferred,
or needs replan. A checkbox is evidence-backed state, not intent.
## Deviation triage
| Type | Action |
| --- | --- |
| Local implementation adjustment | record reason and verification; continue after checks |
| Unknown file or behavior | discovery before implementation continues |
| Architecture or scope change | stop and return affected slices to masterplan |
| New external, destructive, paid, or production effect | apply gate and await authorization |
## Failed-check response
1. Preserve command output, diff, and baseline comparison if available.
2. Identify a distinct hypothesis or diagnostic.
3. Repair inside active slice unless evidence requires replan.
4. Re-run relevant verification and inspect diff.
5. Stop after two unproductive attempts; report blocker.
## Interruption handoff
State active slice, changed paths, checks and results, dirty-tree overlap,
recovery path, unresolved risk, and next safe action. Never claim completion
from partial implementation.
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: 322k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 322k | Updated | Claude CodeCodex | Verified | 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: 322k | Updated | Claude CodeCodex | Verified | 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: 322k | Updated | Claude CodeCodex | Verified | Install |