session-reflection

Conducts a two-question session-end reflection to surface confidence gaps and blind spots.

Updated Apr 9, 2014
One-click install
npx skills add https://github.com/thoroc/thoroc.github.io --skill session-reflection-thoroc
Or copy as Structured Prompt for Agentâ–¼
Please help me install this Agent Skill.
Skill: session-reflection
Source: https://github.com/thoroc/thoroc.github.io/tree/main/.agents/skills/session-reflection
Command: npx skills add https://github.com/thoroc/thoroc.github.io --skill session-reflection-thoroc

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? AI agents are poor judges of their own completeness, so sessions often end with unverified assumptions, skipped checks, or dropped threads that silently invalidate the work. This Skill forces a structured confidence audit and blind-spot check at the cheapest possible moment: right before the user walks away. ## Core Features & Use Cases - Two-question reflection protocol: Sequentially asks "What am I least confident about?" (3-7 concrete, file-level items) and "What's the biggest thing I'm missing?" (1-3 broad patterns), never combined into one message. - Inline or sub-agent modes: Runs inline for short sessions, or spawns a sub-agent with a concrete session summary for deep multi-file sessions, with guidance on cheap model selection. - Gap persistence: Converts verified-but-deferred findings into known-issue documents via the context-file skill, with honest severity ratings, instead of leaving them as chat mentions. - Use Case: After a multi-file refactor touching retry logic and DynamoDB writes, the user says "we're done." The Skill triggers a reflection that surfaces an unverified GSI assumption, which is then investigated or filed as a known-issue before the session closes. ## Quick Start When the user signals the session is wrapping up, initiate the reflection by asking what you are least confident about, wait for the response, then ask the blind-spot question.

Frequently Asked Questions about session-reflection

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

FAQPage Schema
How do I run a session-end reflection with an AI agent?â–¼

Trigger it when the user signals completion with phrases like "we're done" or "that's all." Ask the confidence-audit question first, wait for the response, then ask the blind-spot question separately, and investigate or file any flagged items before closing.

What questions should an AI ask before ending a work session?â–¼

Two questions: "What am I least confident about right now?" producing 3-7 specific items naming files, functions, or assumptions, and "What's the biggest thing I'm missing about this situation?" targeting unverified assumptions and unexplored alternatives.

When should the session reflection not be triggered?â–¼

Skip it for brief single-answer queries, automated or CI contexts, the middle of active work, or when the user explicitly asks to skip it. The reflection overhead is only justified at genuine session-end boundaries.

When should I use a sub-agent for session reflection instead of inline?â–¼

Use the sub-agent spawn pattern for deep sessions with significant multi-file work, providing a concrete summary of files touched, commands run, and assumptions made. Short sessions are better served by the inline mode to avoid spawn overhead.

What happens to gaps found during reflection that won't be fixed now?â–¼

Verified, concrete gaps that are deferred must be filed as known-issue documents via the context-file skill with status ACTIVE and an honest severity rating. Leaving them as chat mentions only is treated as a failure mode.