reflect-on-work

Generate post-task reflections with what_worked, what_failed, and patterns_noticed fields.

Updated Dec 1, 2025
One-click install
npx skills add https://github.com/Clouder0/dotagent --skill reflect-on-work-clouder0
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reflect-on-work
Source: https://github.com/Clouder0/dotagent/tree/main/.claude/skills/reflect-on-work
Command: npx skills add https://github.com/Clouder0/dotagent --skill reflect-on-work-clouder0

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pattern for producing quality reflections after completing work. Required for all agent outputs.

Core Features & Use Cases

  • Reflection fields: What worked, what failed, patterns noticed.
  • Knowledge updates: Capture learnings for knowledge base.

Quick Start

Produce compact, honest reflections including what worked, what failed, and patterns noticed.

Frequently Asked Questions about reflect-on-work

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

FAQPage Schema
How do I capture reflections after completing a task to improve future work?

Post-task reflections systematically document what worked, what failed, and patterns noticed after task execution. This Skill generates structured reflections in compact JSON format to ensure consistency across all agent outputs and create a foundation for knowledge updates that inform system evolution.

What should I include in a work reflection to make it useful?

Effective reflections capture three core elements: what worked (successful approaches and decisions), what failed (obstacles and ineffective strategies), and patterns noticed (recurring themes across executions). This structure ensures reflections are honest, actionable, and feed directly into knowledge base updates.

Can reflections be automated for every task execution?

Yes. This Skill applies mandatory post-task reflections across all domains and task types, generating structured outputs automatically after each execution. The consistent JSON schema ensures reflections scale across diverse workflows without manual formatting.

How do reflections connect to learning and system improvement?

Reflections feed knowledge_updates fields that capture learnings for your knowledge base. By tracking what worked and what failed systematically, reflections create a compounding record that informs agent behavior refinement and prevents repeated mistakes across future executions.

What format do reflections use to stay compact and consistent?

Reflections conform to a defined JSON schema with dedicated fields for what_worked, what_failed, and patterns_noticed, plus knowledge_updates sections. This compact structure keeps reflections machine-readable and easily parsed downstream without sacrificing detail.

Related Skills