reflect

Generate structured five-section post-task critique reports for development tasks.

4|Updated Jan 29, 2026
One-click install
npx skills add https://github.com/danmestas/wardrobe --skill reflect-danmestas
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reflect
Source: https://github.com/danmestas/wardrobe/tree/main/skills/reflect
Command: npx skills add https://github.com/danmestas/wardrobe --skill reflect-danmestas

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a structured, post-task critique to capture learnings, assess performance, and guide improvements after meaningful work.

Core Features & Use Cases

  • Generates a five-section reflection report (Summary, What went well, What didn't, Specific actionable proposals, Open questions) to aid learning and iteration.
  • Supports mode hints to tailor the critique toward design, ops, or coding perspectives for relevant projects.
  • Useful for human review, knowledge capture, and feeding improvements into future planning or memory systems.

Quick Start

Invoke /reflect after completing a meaningful task to generate a structured critique.

Frequently Asked Questions about reflect

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

FAQPage Schema
How do I generate a structured post-task critique after completing a development task?

A structured post-task critique is automatically generated after meaningful work, producing a five-section markdown report covering Summary, What went well, What didn't, actionable proposals, and open questions to support learning and improvement.

Can I tailor a retrospective report for code reviews versus design tasks?

Yes, retrospective reports support mode hints that tailor the critique toward design, ops, or coding perspectives, ensuring the post-task feedback is relevant to the specific project context.

What's the best way to capture learnings from a pull request review?

Capturing learnings from a pull request review is done by generating a structured reflection report that assesses performance, documents what went well and what didn't, and proposes specific actionable improvements for future planning.

Does this post-mortem approach work for project retrospectives?

Yes, this post-mortem approach works for project retrospectives by automatically creating a structured critique that captures knowledge, evaluates outcomes, and feeds specific actionable proposals into future planning or memory systems.

What sections are included in a structured task review report?

A structured task review report includes five markdown sections: Summary, What went well, What didn't, Specific actionable proposals, and Open questions, providing a comprehensive framework for self-assessment and iteration.