meta-review

Distills closed-goal mistakes into reusable patterns and rules in .loop/memory/.

1|1|Updated Jun 21, 2026
One-click install
npx skills add https://github.com/Navdeepgambhir9023/nav --skill meta-review-navdeepgambhir9023
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: meta-review
Source: https://github.com/Navdeepgambhir9023/nav/tree/main/skills/meta-review
Command: npx skills add https://github.com/Navdeepgambhir9023/nav --skill meta-review-navdeepgambhir9023

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After a goal closes, lessons from the session are usually lost. This Skill reviews the goal's journal, verification evidence, and state to record mistakes, detect recurring failure patterns, and promote proven lessons into durable rules so future agent sessions avoid repeating the same errors. ## Core Features & Use Cases - Mistake Ledger: Appends structured mistake entries (kind, root cause, fix, recurrence potential) to an append-only mistakes.nav file. - Pattern Distillation: Writes generalizable observations to patterns.md as advisory guidance for future planners and executors. - Evidence-Based Rule Promotion: Promotes mistakes to mandatory rules in rules.md only after 2+ recurrences or explicit owner approval, preventing rule bloat. - Use Case: After /loop closes a migration goal, the Skill scans the journal for blocked tasks and verification failures, logs two new mistakes, and promotes a recurring wrong-path error into a rule that all future sessions must follow. ## Quick Start Run a retroactive meta-review on the goal that just closed to record its mistakes and update the memory index.

Frequently Asked Questions about meta-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run a meta-review after a goal closes?

Meta-review runs automatically inline when /loop closes a goal, dispatched after the gate verdict and before the registry status flip. You only invoke it manually for retroactive review of an older goal by passing that goal's ID.

When does a mistake get promoted to a rule?

A mistake is promoted to rules.md only when 2+ entries with the same kind exist in mistakes.nav, when the owner explicitly sets promoted_to_rule on an entry, or when a high-recurrence-potential mistake appears across multiple stages. Single occurrences stay as mistakes or patterns.

What is the difference between mistakes, patterns, and rules?

Mistakes are append-only records of what went wrong in a specific goal. Patterns are advisory observations generalizable across goals. Rules are mandatory imperatives every future agent must follow, promoted only with recurrence evidence or owner approval.

Can meta-review modify the goal contract or plan?

No. Hard gates forbid modifying the contract, plan, registry, or any state.json field outside memory's own files. It also cannot delete entries from mistakes.nav, which is strictly append-only.

When is meta-review skipped for a closed goal?

Meta-review is optional for goals closed as CANCELLED that never produced evidence, since there may be nothing to learn. In that case /loop appends a META_REVIEW_SKIPPED event to the journal instead.