reflect

Spawns parallel review subagents over session transcripts to route learnings into skill edits.

Updated Jul 29, 2026
One-click install
npx skills add https://github.com/mmdmcy/fluttAIrbar --skill reflect-mmdmcy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: reflect
Source: https://github.com/mmdmcy/fluttAIrbar/tree/main/plugins/pstack/skills/reflect
Command: npx skills add https://github.com/mmdmcy/fluttAIrbar --skill reflect-mmdmcy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Valuable lessons learned during long agent sessions disappear when the conversation ends, forcing future agents to rediscover the same fixes, tool quirks, and workflow patterns. ## Core Features & Use Cases - Parallel multi-lens review: Spawns three reviewer subagents (judgment, tooling, divergent) over the active transcript, each surfacing durable learnings from a different angle. - Structured synthesis: A synthesizer subagent merges findings into an Accepted / Rejected / Backlog list with explicit routing to existing skills, description tuning, or new skill creation. - Approval-gated edits: Presents the full synthesis to the user before applying any change, routing substantive edits through the $skill-creator workflow. - Use Case: After a complex debugging session where the agent hit dead ends and found a working path, invoke reflect to capture the generalizable recipe as an edit to the relevant skill so the next agent avoids the same dead ends. ## Quick Start Say "reflect" after a complex task completes to mine the session transcript and route durable learnings into skill edits.

Frequently Asked Questions about reflect

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

FAQPage Schema
How do I capture learnings from an agent session?▼

Invoke the reflect skill after a complex task completes. It locates the active transcript, spawns three parallel reviewer subagents with different lenses, synthesizes their findings, and routes approved learnings into edits on existing skills.

When should I run a reflection review on a conversation?▼

Run it after complex tasks with 5+ tool calls that landed cleanly, after the agent hit dead ends and found a generalizable path, or after user corrections. Skip trivial conversations and one-offs that are already covered by existing skills.

Does reflect modify skill files automatically?▼

No. The synthesizer produces an Accepted/Rejected/Backlog list that is presented to the user for explicit approval before any edit is applied. Substantive edits are handed to the $skill-creator workflow rather than applied directly.

What happens to learnings that don't fit an existing skill?▼

Findings with no existing skill home are routed as new skill proposals via $skill-creator, while items better enforced by lint rules or scripts go to a backlog tracker. Findings that fail durability or specificity criteria are rejected with reasons.

Why does reflect need the session transcript file?▼

Reviewers need the actual transcript to cite concrete evidence for each learning, including turn numbers and quotes. If no transcript path resolves, a digest of the session is passed to reviewers instead.