skills.rest
akshay-na
akshay-naCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

meta-learning-engineering-retrospection

Guide structured retrospectives to document lessons and refine decision-making heuristics.

4|Updated Oct 31, 2024
Search Tags:#learning#retrospective#feedback loop#engineering#growth#reflection
One-click install
npx skills add https://github.com/akshay-na/dotfiles --skill meta-learning-engineering-retrospection
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: meta-learning-engineering-retrospection
Source: https://github.com/akshay-na/dotfiles/tree/main/cursor/.cursor/skills/meta-learning-engineering-retrospection
Command: npx skills add https://github.com/akshay-na/dotfiles --skill meta-learning-engineering-retrospection

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you build a feedback-driven improvement loop to accelerate long-term growth by deliberately extracting lessons from projects, incidents, and decisions.

Core Features & Use Cases

  • Structured Retrospectives: Guides you through asking "What went well, what went wrong, and what would I change?"
  • Flawed Assumption Identification: Helps pinpoint beliefs that turned out to be incorrect.
  • Heuristic Refinement: Updates personal rules of thumb based on observed outcomes.
  • Use Case: After a major feature launch, use this Skill to document surprises, identify root causes of any issues, and refine your decision-making heuristics for future projects.

Quick Start

Use the meta-learning-engineering-retrospection skill to perform a personal retrospective on the recent project launch.

Frequently Asked Questions about meta-learning-engineering-retrospection

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

FAQPage Schema
How do I run an engineering retrospective after a software project launch?▼

An engineering retrospective systematically documents surprises, traces root causes of issues, and identifies flawed assumptions to refine decision-making heuristics for future software launches.

What is the best way to identify flawed assumptions during software development?▼

Identifying flawed assumptions requires a structured reflection process that compares initial project beliefs against actual observed outcomes and documented surprises to pinpoint inaccuracies.

How does a structured reflection process improve engineering decision-making?▼

A structured reflection process improves engineering decision-making by systematically extracting reusable lessons from past incidents, which updates personal rules of thumb and refines heuristics.

Can I use this structured retrospection approach for product development contexts?▼

Yes, structured retrospection applies directly to product development contexts, helping teams document surprises, trace root causes of incidents, and foster continuous improvement.

What should a continuous improvement feedback loop include after a major incident?▼

A continuous improvement feedback loop should include documenting surprises, tracing root causes of issues, and updating decision-making heuristics to prevent recurrence and accelerate growth.

Related Skills

Explore More Software Engineering Skills→
brian915brian915
1

code-skillz

Enforce stepwise human approval in AI-assisted coding sessions.

Community
Basic
fmflurryfmflurry
171

security-review-says-user-corrections-2

Extract recurring user corrections into reusable guidance rules with frontmatter metadata.

Community
Intermediate
gztcodegztcode

findmy

Automate Apple device and AirTag tracking via FindMy.app with AppleScript.

Community
Advanced
pr-pmpr-pm
121

thoroughness

Enforce a three-phase workflow of analysis, implementation, and verification for complex tasks.

Official
Basic