neb-retro

Classify task outcomes from Git history and PR evidence into retrospective categories.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/nebinfra/nebcore-ai-skills --skill neb-retro
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: neb-retro
Source: https://github.com/nebinfra/nebcore-ai-skills/tree/main/neb-retro
Command: npx skills add https://github.com/nebinfra/nebcore-ai-skills --skill neb-retro

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Initiative Retrospective helps teams analyze completed projects, extract patterns from task reports, identify failure modes, and capture durable learnings by updating a centralized MEMORY repository.

Core Features & Use Cases

  • Pattern extraction from execution histories to inform future planning.
  • Task classification into clean success, retry, blocked, failed, or gap-spawned with evidence.
  • Memory updates generation and synchronization to ensure institutional knowledge remains current.
  • Guided workflow that collects evidence (git history, PR outcomes, workspace remnants) and produces a structured retrospective.

Quick Start

Provide the initiative name to begin the retrospective and follow the workflow to generate findings.

Frequently Asked Questions about neb-retro

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

FAQPage Schema
How do I extract learning patterns from project execution histories?▼

Extracting learning patterns from project execution histories involves gathering objective evidence like Git history and PR outcomes, classifying task outcomes into success or failure modes, and generating actionable learnings.

What is the best way to run a retrospective on completed project tasks?▼

The best way to run a retrospective on completed tasks is to follow a guided workflow that collects objective artifacts, classifies them into clean success, retry, blocked, or failed categories, and produces structured findings.

Can I use Git history and PR outcomes to identify project failure modes?▼

Yes, Git history and PR outcomes provide objective execution evidence used to classify task outcomes into failure modes like blocked, failed, or abandoned, which helps identify patterns for future planning.

How do I classify task outcomes for root-cause analysis?▼

Task outcomes for root-cause analysis are classified into clean success, retry success, blocked then resolved, failed or abandoned, and gap-spawned categories based on objective execution evidence gathered from project artifacts.

How does a project retrospective update institutional memory?▼

A project retrospective updates institutional memory by capturing durable learnings from classified task outcomes and synchronizing them as memory updates to a centralized repository, ensuring institutional knowledge remains current.

What do I need to start an initiative retrospective?▼

To start an initiative retrospective, you need to provide the initiative name, which locates the relevant project artifacts and defines the tasks to review before gathering execution evidence and generating actionable learnings.