skills.rest
maxoreric
maxorericCOMMUNITY
Explore all skills by this author →
GitHub

reflect-skill

Analyzes task outcomes and generates improvement suggestions in a markdown file.

Updated Jan 20, 2026
Search Tags:#post-mortem#continuous improvement#lessons learned#reflection#task review
One-click install
npx skills add https://github.com/maxoreric/sop-engine --skill reflect-skill
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: reflect-skill
Source: https://github.com/maxoreric/sop-engine/tree/main/%24workflow.input.user_intent/skills/reflect-skill
Command: npx skills add https://github.com/maxoreric/sop-engine --skill reflect-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you systematically review completed or failed tasks to extract valuable lessons learned, ensuring continuous improvement and preventing recurring mistakes.

Core Features & Use Cases

  • Post-task analysis: Automatically generates a structured reflection after task completion or failure.
  • Identifies successes and failures: Differentiates what went well, what didn't, and why.
  • Suggests improvements: Formulates actionable steps for future tasks.
  • Use Case: After a complex project, use this skill to generate a comprehensive "lessons learned" document that can be shared with the team to improve future project planning and execution.

Quick Start

Use the reflect skill to summarize the key takeaways from the recent project execution.

Frequently Asked Questions about reflect-skill

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

FAQPage Schema
How do I generate a structured post-mortem for a completed software task?▼

To generate a structured post-mortem, you review task outcomes to identify successes, failures, and root causes of discrepancies. This facilitates structured reflection by analyzing objectives and results to produce actionable improvement insights.

What is the best way to document lessons learned from a failed project execution?▼

Documenting lessons learned involves analyzing task outcomes to extract valuable insights and prevent recurring mistakes. It differentiates what went well from what didn't, generating actionable steps for future tasks in a markdown file.

Can I automatically analyze unexpected findings from a task review for continuous improvement?▼

Yes, you can analyze task outcomes to identify unexpected findings for continuous improvement. The process reviews objectives and results to formulate actionable insights and improvement suggestions documented in a markdown file.

Do I need any external dependencies to perform a structured task reflection?▼

No external dependencies are required to perform structured task reflection. You can independently review task objectives, results, and root causes to generate a markdown file containing actionable insights and improvement suggestions.

Are there limitations when using automated task review for post-mortem analysis?▼

Limitations of automated task review depend on the available context of the task execution provided. Without sufficient details on objectives and results, generating accurate root cause analysis and actionable improvement suggestions may be constrained.

Related Skills

Explore More Software Engineering Skills→
yohayetsionyohayetsion
4

roi-report

Generates reports of saved time and ROI from user activity data.

Community
Intermediate
andreadellacorteandreadellacorte
5

groove-work-compound

Document lessons learned and update project rules, templates, and documentation.

Community
Advanced
KaimingWanKaimingWan
103

debug

Reproduce software bugs and analyze root causes with knowledge base integration.

Community
Intermediate
awinogradovawinogradov
5

pr:monitor

Monitor pull requests for review approval and CI check status.

Community
Intermediate