wtf.reflect

Route session learnings into TECH, QA, DESIGN, or VISION steering docs.

7|2|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/xiduzo/wtf --skill wtf-reflect
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wtf.reflect
Source: https://github.com/xiduzo/wtf/tree/main/skills/wtf.reflect
Command: npx skills add https://github.com/xiduzo/wtf --skill wtf-reflect

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps developers capture hard-won learnings from sessions and route them into the correct steering documents, ensuring that insights from AI-human collaboration inform future work.

Core Features & Use Cases

  • Routes learnings to TECH, QA, DESIGN, or VISION steering docs under a "Hard-Won Lessons" section.
  • Tracks intervention triggers from prompts and flags when a session should be summarized, reset, or escalated.
  • Orchestrates creation or updating of docs with a fallback to LEARNINGS.md when steering docs are missing.

Quick Start

Record a session's learnings and route them into the appropriate steering document sections.

Frequently Asked Questions about wtf.reflect

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

FAQPage Schema
How do I document AI-human collaboration learnings into steering docs?

You can capture session learnings and route them directly into TECH, QA, DESIGN, or VISION steering docs under a "Hard-Won Lessons" section during developer sessions and AI-human collaboration.

What is the best way to track interventions and mistakes during a developer session?

You can track intervention triggers from prompts and flag when a session should be summarized, reset, or escalated by using the hooks/track-interventions.sh script during your developer sessions.

Do I need a specific repo structure to route session learnings to steering documents?

Yes, you need a working repo with a docs/steering directory structure and the hooks/track-interventions.sh script to validate steering doc existence and append captured learnings to the correct sections.

What happens to session learnings if steering docs are missing?

If steering docs are missing, the skill orchestrates a fallback to create or update a LEARNINGS.md file, ensuring your hard-won lessons and session interventions are still documented.

When should I run a post-session retrospective for documentation?

You should run a post-session retrospective when prompt interventions trigger a flag indicating the session needs to be summarized, allowing you to capture hard-won lessons and route them to the appropriate steering docs.