adv-reflect

Analyze archived engineering change data to generate structured postmortem reports.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the lack of systematic learning in AI-assisted development by providing a structured post-change reflection methodology that captures project execution metrics and system friction without disrupting active workflows.

Core Features & Use Cases

  • Two-Plane Analysis: Evaluates both project execution efficiency and systemic tool friction to identify process bottlenecks.
  • Automated Reporting: Generates a standardized reflection document containing metrics like retry density, TDD compliance, and gate completion.
  • Wisdom Accumulation: Maps recurring errors and manual workarounds to specific friction categories, enabling long-term process improvements.

Quick Start

Run the adv-reflect skill to analyze the most recently archived change and generate a reflection report.

Frequently Asked Questions about adv-reflect

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

FAQPage Schema
How do I generate a postmortem report from archived engineering task logs?

To generate a postmortem report, the skill analyzes archived engineering change data, historical task logs, and gate completion records to synthesize project execution metrics and system friction patterns into a standardized reflection document.

What is the best way to map technical debt and workflow bottlenecks to actionable wisdom?

Mapping technical debt and workflow bottlenecks to actionable wisdom is achieved by evaluating recurring errors and manual workarounds against project execution efficiency, categorizing systemic tool friction for long-term process improvements.

How does two-plane analysis identify process bottlenecks in software engineering?

Two-plane analysis identifies process bottlenecks by simultaneously evaluating project execution efficiency and systemic tool friction, surfacing metrics like retry density, TDD compliance, and gate completion from historical task data.

Can I measure TDD compliance and retry density from historical gate completion records?

Yes, you can measure TDD compliance and retry density by operating on historical task logs and gate completion records to extract structured execution metrics, which are then formatted into an automated reflection report.

When do I need to run an automated reflection on archived engineering changes?

You need to run an automated reflection when you have archived engineering change data and want to capture project execution metrics without disrupting active workflows, facilitating continuous improvement through structured post-change analysis.

What limitations exist when analyzing error recovery data to synthesize project execution metrics?

A key limitation is that synthesizing project execution metrics requires pre-existing archived error recovery data and gate completion records; without historical task logs, the skill cannot map friction patterns or generate a standardized reflection document.