Agent skill
retro-memory-enterprise
Enterprise post-session retrospective: writes evidence-ledger, delegates to retro-auditor subagent (isolated context), updates .claude/rules, runs validations.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/retro-memory-enterprise
SKILL.md
Enterprise Retro Memory (governed)
ARGUMENTS: $ARGUMENTS
Mode
- full (default): evidence-ledger + update all .claude/rules/*.md + run validate_rules.sh
- light: evidence-ledger + update only active-context.md + run validate_rules.sh
Guardrails (anti-hallucination)
- Use ONLY information from the current conversation + existing repo files.
- Anything not explicit must be marked as Assumption (confidence: high/med/low), or excluded.
- Any inferred rule MUST include "Evidence:" referencing what in the chat supports it.
- Never store secrets/tokens/credentials. If found, redact and add "[REDACTED]".
Step A — Create Evidence Ledger (main context)
-
Ensure directories exist:
- ./.claude/retro/
-
Write a new file: ./.claude/retro/-evidence.md Use format: YYYY-MM-DDTHH-MM (e.g. 2026-02-17T14-30-evidence.md)
Include sections:
-
Decisions & Agreements (explicit only)
-
Preferences (explicit only)
-
Failure Modes Observed (repeated problems)
-
Inefficient Loops to Avoid
-
Effective Patterns to Repeat
-
Open Questions / Unknowns
-
Assumptions (minimize; include confidence)
-
Redactions (if any)
-
-
Keep it short but evidence-rich. Use bullet points. Short quoted fragments (<= 1 line each).
Step B — Delegate to isolated subagent
Use the retro-auditor agent and pass:
- ledger path
- mode
Prompt: "Use the retro-auditor agent to process ./.claude/retro/-evidence.md in MODE=<full|light> and update ./.claude/rules accordingly."
Step C — Validate & Fix
Run:
bash .claude/skills/retro-memory-enterprise/scripts/validate_rules.sh
If warnings/errors occur, fix and re-run until clean.
Step D — Return summary
Output in chat:
- Ledger path created
- Files updated (list)
- Top 5 rule changes
- Assumptions introduced (if any)
- Contradictions resolved (if any)
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?