Menü
Drift analysis — check if deployed skills, steering, and AGENTS.md still match project reality. Use periodically or after major refactors.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
Dispatch Codex to review all unreviewed repository work, then verify its correlated findings ticket or clean result. Use when requesting an independent Codex review, auditing all changes, checking work since the last review, or waiting for Codex findings. Trigger: dispatch codex review, independent review, review all changes, check codex findings, run review agent.
Always-on: when a project has tickets, work the frontier (first unblocked open ticket), mark done, update plan status.
Incremental and full-history repository review with resumable adoption batches. Use when reviewing new work, initializing review tracking, reviewing all work to date, resuming historical review, inspecting unreviewed commits, or reviewing changed tickets. Trigger: review new work, adopt repository, review all history, resume review, review marker, unreviewed commits.
End-of-session handoff that captures current state for the next session. Use when ending a work session, switching context, or before a long break.
Consolidate project artifacts — promote scratch to memory, deduplicate memory, process decisions, organize scripts, update steering/skills accuracy. Use periodically or when the project feels cluttered.
Run and interpret crew-research evals — run.sh flags, scores.jsonl fields, activation TPR/FPR verdicts, resuming interrupted runs. Use when running evals, reading eval results, diagnosing a failing definition, or resuming a dead run. Trigger: run the evals, eval results, scores.jsonl, activation test, TPR, delta threshold, resume the run, skip-completed, known gap.
| name | project-audit |
| description | Drift analysis — check if deployed skills, steering, and AGENTS.md still match project reality. Use periodically or after major refactors. |
| metadata | {"type":"process","invocation":"user-only","practice":null} |
Check whether the crew-research deployment still matches project reality.
.kiro/steering/verification-protocol.mdpackage.json scripts / Makefile / Cargo.toml.memory/, .scratch/, .kiro/) exist?.kiro/steering/ files reference paths/tools that exist?.references/ used consistently (not resources/ or bare references/)?resources/ or references/ exists and is gitignored → flag for rename to .references/.references/ in .gitignore?decisions.md, DECISIONS.md, docs/decisions.md.memory/adr/ (ADR-worthy) or .memory/CONTEXT.md (terms).memory/decisions.md — should entries be promoted to ADRs?## Audit Results
- Verification: ✅/❌ (commands work?)
- AGENTS.md: ✅/❌ (accurate?)
- Steering: ✅/❌ (references valid?)
- Skills: N deployed, N relevant, N gaps
- CONTEXT.md: N terms, N stale, N missing
- Config: ✅/❌ (matches reality?)
- References: ✅/❌ (consistent naming, gitignored?)
- Decisions: ✅/❌ (all processed?)
## Actions Taken
- [fixes applied]
## Recommended
- [remaining items needing user decision]