skills.rest
jbabin91
jbabin91COMMUNITY
Explore all skills by this author →
GitHub

beads-retrospective

Analyze completed Beads issues to identify patterns, tech debt, and gaps and generate follow-up issues.

5|Updated Oct 27, 2025
Search Tags:#automation#beads#retrospective#data-analytics#issue-tracking#tech-debt#pattern-detection
One-click install
npx skills add https://github.com/jbabin91/autocomplete-rs --skill beads-retrospective
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: beads-retrospective
Source: https://github.com/jbabin91/autocomplete-rs/tree/main/.claude/skills/beads-retrospective
Command: npx skills add https://github.com/jbabin91/autocomplete-rs --skill beads-retrospective

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Beads retrospective analyzes completed work to surface patterns, tech debt, and gaps, enabling proactive improvement and automation of follow-up work.

Core Features & Use Cases

  • Automatic extraction of patterns, gaps, and tech debt from closed issues and work streams.
  • Proactively create follow-up beads issues to address discovered work.
  • Cross-epic intelligence to unify insights across multiple initiatives. Example: after a UI overhaul, identify recurring blockers and generate a template checklist.

Quick Start

Run beads retrospective after a completed work stream to surface patterns, tech debt, and gaps and automatically create follow-up issues.

Frequently Asked Questions about beads-retrospective

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

FAQPage Schema
How do I identify patterns and tech debt from completed issue tracking data?▼

Analyzing completed issue tracking data identifies patterns and tech debt by reviewing closed issues to surface recurring blockers and gaps. This retrospective process extracts cross-epic intelligence to enable proactive improvement and automate follow-up work generation.

How do I automatically generate follow-up issues after closing project work streams?▼

Automatically generating follow-up issues after closing project work streams involves analyzing completed issues to discover gaps and tech debt. The retrospective tool then orchestrates findings into actionable new issues, proactively addressing discovered work without manual entry.

Can I use retrospective pattern detection on closed issues across multiple initiatives?▼

Retrospective pattern detection works on closed issues across multiple initiatives by applying cross-epic intelligence. It unifies insights from various work streams, extracting recurring blockers and tech debt to generate a cohesive view of project gaps.

What is the best way to surface recurring blockers from a completed UI overhaul?▼

The best way to surface recurring blockers from a completed UI overhaul is running a retrospective analysis on the closed issues. This identifies patterns and tech debt, enabling you to generate template checklists and follow-up issues for futureOverhauls.

When should I run a retrospective analysis on my issue tracking data?▼

You should run a retrospective analysis on issue tracking data immediately after closing issues or completing a work stream. It can also be triggered on demand using prompts like 'what's next?' to surface patterns and suggest actionable follow-up tasks.

Does the beads retrospective Skill require external dependencies to analyze tech debt?▼

The beads retrospective Skill requires no external dependencies to analyze tech debt. It operates autonomously using internal guidance files and report templates to orchestrate discoveries and create follow-up issues from your closed work data.

Related Skills

Explore More Data & Analytics Skills→
kirvinkirvin

retro

Analyze git log and beads closed-issue data to generate improvement issues.

Community
Advanced
AugustEmnaAugustEmna

follow-up-tasks

Convert current work into categorized follow-up tasks via proposeFollowUpTasks.

Community
Intermediate
githubgithub
4.9k

temporary-id-safe-output

Resolve temporary IDs to real issue numbers in workflow runs.

Official
Advanced
shuu5shuu5

twl:workflow-tech-debt-triage

Inventory and triage tech-debt issues across labels into actionable remediation tasks.

Community
Advanced