Menu
Check if recorded Kauri decisions are stale. Use when assessing code changes, reviewing decisions, or when a staleness warning was raised by a hook.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Consult existing Kauri decisions before planning or implementing changes. Use BEFORE making architectural choices, changing conventions, picking libraries, or modifying files that might be covered by a recorded decision.
Record a project decision using Kauri. Use when you've chosen an architectural pattern, library, convention, boundary, or resolved a trade-off.
Draft a Kauri decision for human review before recording it. This skill should be used proactively — when the user makes, confirms, or rejects a non-trivial choice (picking a library, rejecting an approach, choosing an architecture, resolving a trade-off, establishing a convention), invoke this skill to draft a decision for their approval. Signals include "let's go with X", "let's use X", "X is better", rejecting an alternative after discussion, or choosing between trade-offs. Do NOT propose for trivial choices, temporary workarounds, or single-line fixes.
Review recent code changes against Kauri decisions. Use after implementing changes, before committing, during PR review, or when asked "does this look right?" to verify consistency with recorded decisions.
| name | check-staleness |
| description | Check if recorded Kauri decisions are stale. Use when assessing code changes, reviewing decisions, or when a staleness warning was raised by a hook. |
| disable-model-invocation | false |
| user-invocable | true |
| allowed-tools | mcp__kauri__kauri_check mcp__kauri__kauri_show mcp__kauri__kauri_validate |
| argument-hint |
Run a staleness check on all active Kauri decisions and help the user resolve any stale records.
Run the check: Use kauri_check to scan all active records.
For each stale record:
kauri_show to see the full decision content.Resolve each stale record by asking the user to choose:
kauri_validate with verdict still_valid to refresh the timestamp.kauri_record with supersedes to create a new decision replacing the old one.kauri_validate with verdict deprecate.A record is stale when:
ttl_days have passed since last validation (default 90 days).Stale does NOT mean wrong — it means "please review." The decision might still be perfectly valid.