---
# upstream: https://github.com/cursor/plugins/blob/main/pstack/skills/reflect/SKILL.md
name: reflect
description: Spawn three parallel review subagents over the active transcript, surface learnings, and route each to a concrete edit on an existing skill. Use when the user says reflect.
disable-model-invocation: true
---

# Reflect

Mine the current conversation for durable learnings, then route them into skill edits.

Invoke when the user says "reflect" or "/reflect". Skip when the conversation is trivial, off-topic, or already covered by an existing skill the parent followed correctly. One-offs are not learnings.

## 1. Locate the active transcript

Before fanning out, find this conversation's transcript in the workspace's transcripts: Claude Code keeps `~/.claude/projects/<slug>/<session>.jsonl` (slug = workspace path with `/` and `.` turned into `-`; subagents in `<session>/subagents/`), Codex keeps `~/.codex/sessions/YYYY/MM/DD/rollout-*.jsonl` (the first line, `session_meta`, holds `cwd`). Do not glob across `~/.claude/projects/*/` in Claude Code, and do not read Codex rollouts whose `cwd` is another workspace. That crosses workspace boundaries and reads private chats from unrelated projects.

```bash
ls -t <transcripts>/*.jsonl <transcripts>/*/subagents/*.jsonl 2>/dev/null | head -10
```

For Codex, list the rollouts under `~/.codex/sessions/` instead and keep those whose `cwd` is this workspace. For each candidate, read the first user message in the JSONL. Take the file that contains the conversation's opening user prompt. If none matches, pass a tight digest of the session instead.

## 2. Spawn three reviewers in parallel

One message, three subagent calls (`Agent` in Claude Code, `spawn_agent` in Codex), `subagent_type: "general-purpose"` in Claude Code, with full tool access. Reviewers need MCP access to look up the tickets, chat threads, and observability traces the transcript references, and a read-only agent can lose MCPs.

Each reviewer and the synthesizer name a role line in the `mstack-models` rule and a default. Set `model` to that line's value, or to the default if the rule or the line is missing. Leave `model` unset when the value is `auto` or `inherit-parent`. If the subagent tool rejects a slug, use the default and say so. If it rejects the default, use the closest valid slug from its error message. Pick each subagent's reasoning level and fast or standard speed for the job, per the Subagents section of the **mineru-mode** skill.

| Lens | Role line | Default `model` | Prompt template |
|---|---|---|---|
| Judgment | `reflect judgment, divergent, synthesizer` | `opus xhigh` | `references/judgment-reviewer.md` |
| Tooling | `reflect tooling` | `inherit-parent` | `references/tooling-reviewer.md` |
| Divergent | `reflect judgment, divergent, synthesizer` | `opus xhigh` | `references/divergent-reviewer.md` |

Pass each template verbatim, substituting the transcript path or digest where marked. Reviewers return findings in the subagent response.

## 3. Synthesize

One subagent call, `subagent_type: "general-purpose"` in Claude Code, `model` from the `reflect judgment, divergent, synthesizer` line (default `opus xhigh`), with full tool access. It spot-verifies citations through MCP, and a read-only agent can lose MCPs. Pass `references/synthesizer.md` verbatim, with each reviewer's full output inlined where marked. It returns an Accepted / Rejected / Backlog list.

## 4. Structural enforcement check

Move any Accepted item that a lint rule, script, metadata flag, or runtime check would enforce more reliably to Backlog. See the **encode-lessons-in-structure** principle skill.

## 5. Apply

Present the synthesizer's full Accepted / Rejected / Backlog output and wait for explicit approval before applying any Accepted edit. The user picks the subset and may redirect routings. Skill changes affect every future agent in the org. Do not auto-apply.

File each Backlog item to your team's devex or backlog tracker without waiting. Only the Accepted list waits for approval.

Follow each approved row's Routing exactly:

- Trivial existing-skill edit (a one-line bullet, a tightened sentence, a stale fact corrected): the parent does it directly.
- Substantive existing-skill edit (a new section, a new pattern table, more than ~10 lines): hand to the `skill-creator` skill (`$skill-creator` in Codex) and run its draft / test / iterate loop.
- `tune description: <skill path>` (the skill exists but didn't trigger when it should have): hand to `skill-creator` and run its description-optimization loop.
- `new skill via skill-creator: <kebab-name>`: hand creation to `skill-creator`. Do not invent the shape ad hoc.

If your environment ships a SKILL.md validator, run it on every touched skill before declaring done.

## 6. Summarize for the user

Short list, no preamble:

- Edits applied: `<skill path>`. What changed, one line each.
- New skills created: `<skill path>`. One line each (rare).
- Backlog filed to the devex tracker: `<issue title>` (`<tags>`). One line each.
- Dropped: one line per rejected finding + reason from the synthesizer.