Individual skill

reflect

Spawn three parallel review children over the active T3 thread, surface learnings, and route each to a concrete edit on an existing skill. Use when the user says reflect.

t3/overrides/reflect/SKILL.md

Read pinned source

Source commit 91251ca92b107de606d3958e86454441910f1179

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Local scripts
Last checked
Nov 5, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
18
Repository last updated
Nov 4, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# 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.

[The runtime's Modes section](../pstack-runtime/SKILL.md#modes) sets the mode lines of every brief this skill writes and how its spawns run in light mode.

## 1. Locate the active thread

Before fanning out, find this conversation's T3 thread, which the reviewers read with `t3_thread_read` (see the runtime's [History section](../pstack-runtime/SKILL.md#history)). Do not read threads from other projects. That reads private chats from unrelated work.

Use the thread id if the host already names it. Otherwise call `t3_thread_list` with `statuses: ["running"]` and take the newest candidates. Child task threads this session spawned are threads too. List them with `t3_thread_list` and `includeSubagents: true` when a reviewer needs a child's work.