Skip to main content
skill CX Codex

trajectory-review — Claude Code skill: what it does, install

trajectory-review is a Claude Code skill that examines an agent’s path to a result. It runs after a task or eval finishes, fails, or changes outcome.

MIT ★ 741 updated 2026-11-11

Install into Claude Code · Plugin marketplace All methods and platforms ↓
/plugin marketplace add MiniMax-AI/mcode-stack
/plugin install ronny@mcode-stack
Open on GitHub

What trajectory-review does

trajectory-review reconstructs an agent run from a session transcript, tool-call log, or eval trace. It records the intent, key arguments, returned data, and next decision for each step. The review flags unchecked assumptions, detours, wrong tools or arguments, wasted context, ignored warnings, and broken earlier constraints.

It identifies the earliest step that made a failed run unlikely to succeed, or the riskiest step in a passing run. Each finding is tied to a concrete prompt, harness, or project-rule change, while isolated quirks stay out of shared rules. The run record is required for the review. Fixes are checked with harness-experiment by rerunning the task several times and comparing trajectories as well as outcomes.

What it helps with

  • reconstruct an agent’s step-by-step execution from a run record
  • locate the first decision that led a failed task off course
  • separate checked evidence from assumptions made during execution
  • spot repeated tool calls, idle polling, and other wasted turns
  • map a trajectory issue to a prompt, harness, or project-rule fix

Example prompts for the agent

  • Review the latest run from its transcript and mark every unchecked assumption.
  • Build a compact timeline with each goal, tool call, response, and next decision.
  • Find the riskiest step in this passing eval and suggest a check with harness-experiment.

How to install trajectory-review

1Plugin marketplace

/plugin marketplace add MiniMax-AI/mcode-stack
/plugin install ronny@mcode-stack

This installs the whole ronny plugin with all its skills

2Skills CLI (Vercel)

npx skills add MiniMax-AI/mcode-stack --skill trajectory-review -a claude-code

3Manually: put the files in place

~/.claude/skills/trajectory-review/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/trajectory-review/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about trajectory-review

How do I install trajectory-review in Claude Code?

Add the marketplace with /plugin marketplace add MiniMax-AI/mcode-stack, then install the plugin with /plugin install ronny@mcode-stack.

What does trajectory-review do?

It examines the recorded path behind an agent result, including tool use, detours, assumptions, missed signals, and instruction drift. The findings are turned into specific changes to prompts, the harness, or project rules.

What does trajectory-review need to work?

It needs an actual run record such as a session transcript, tool-call log, or eval trace. The review also records the model, settings, and repository state; fixes are checked with harness-experiment.

Source text

SKILL.md · MIT
---
name: trajectory-review
description: Review how an agent reached its result, not only whether the result passed, covering tools called, detours, unverified assumptions and wasted round trips, and turn the findings into concrete harness or prompt fixes. Use after an agent task finishes or fails, when an eval task flips, or when asked to look at the process behind a result.
---

# Trajectory Review

A passing result can hide a fragile process: an assumption that happened to
hold, a lucky retry, ten round trips where two would do. A failing result
usually has its cause several steps before the error. Review the path, not
only the end point.

## 1. Get the real trajectory

Use the actual record of the run: the session transcript, tool-call log, or
eval trace. Note the model, settings and repository state. Do not reconstruct
the run from memory.

## 2. Walk it step by step

Build a compact timeline. For each step: what the agent intended, which tool
it called with which key arguments, what came back, and what it decided next.

While walking, mark:

- **Unverified assumptions.** The agent states or acts on something it never
  checked ("callers already validate this", "the test passes").
- **Detours.** Loops, repeated searches with changing keywords, re-reading the
  same file, retries without a change in approach.
- **Wrong tool or wrong arguments.** Including tools it could not find.
- **Context waste.** Large outputs pulled in and never used, polling instead of
  waiting for a notification.
- **Missed signals.** Errors, warnings or test failures it saw and ignored.
- **Instruction drift.** Earlier constraints it later broke, often after
  compaction.

## 3. Find the first point where it went wrong

For a failure, find the earliest step after which success became unlikely.
For a pass, find the riskiest step: where a slightly different input would
have broken it.

## 4. Turn findings into fixes

Map each finding to the cheapest durable fix:

| Finding | Typical fix |
| --- | --- |
| Assumption never checked | A verification step in a skill or project rules |
| Could not find or picked the wrong tool | Tool description, naming or grouping (see `tool-budget-audit`) |
| Lost an earlier constraint | Write it into a file the agent reloads (see `long-session-check`) |
| Polling or waiting idle | Background tasks with notification (see `long-command-check`) |
| Repeated per-turn overhead | Context injection review (see `context-tax-audit`) |
| Model limitation | Record it; re-check after the next model upgrade |

Keep one-off quirks out of project-wide rules. Only propose a rule for
something that has happened more than once or caused real damage.

## 5. Confirm

A fix is a harness change, so check it with `harness-experiment`: rerun the
same task several times and compare the trajectory, not only the outcome.

## Output

The compact timeline with marked steps, the first wrong (or riskiest) step,
and a short list of proposed fixes, each tied to a specific step.

© Ronny (MiniMax Code team) · MIT · MiniMax-AI/mcode-stack

Similar skills

All skills for Code review and refactoring →

From the same set27

The whole set →
ronny ronny is a Claude Code plugin with skills for code review, agent workflows, and checking agent output. It comes into play for reviewing changes, delegating work, and auditing how agents operate. CX Codex ★ 741repo stars handoff-doc handoff-doc is a Claude Code skill that writes a structured handover file before a session reset or task switch. It preserves critical context without relying on full chat history. CX Codex +1 ★ 741repo stars review-capacity-check review-capacity-check is a Claude Code skill that checks unfinished agent work before another launch. It runs before parallel batches and during weekly reviews. CX Codex +1 ★ 741repo stars taste-to-checks taste-to-checks is a Claude Code skill that turns repeated review fixes into tests, lint rules, hooks, CI steps, or project rules. It activates after the same miss returns. CX Codex +1 ★ 741repo stars harness-experiment Harness-experiment is a Claude Code skill that runs controlled experiments to validate agent scaffolding changes. It triggers when adjusting prompts, tools, or subagent layouts for performance tracking. CX Codex +1 ★ 741repo stars independent-review independent-review is a Claude Code skill that reviews changes from a clean context before merge. It compares the diff with the requirement and test output. CX Codex +1 ★ 741repo stars agent-brief The agent-brief skill for Claude Code structures task delegation to AI agents. It forces clarity on stakes, hypotheses, and verification criteria before an agent starts working. CX Codex +1 ★ 741repo stars evidence-first-review evidence-first-review is a Claude Code skill that audits an agent’s finished work from command logs and test evidence. It runs before a PR merge or an analysis is accepted. CX Codex +1 ★ 741repo stars

Project sponsors

Companies that keep this analytics open