// PROACTIVELY analyze completed Beads issues to identify patterns, tech debt, and gaps. Suggests new OpenSpec proposals based on discovered work. Use after closing issues or when user asks "what should we work on next?"
PROACTIVELY convert approved OpenSpec specs into Beads issues when user applies a change or explicitly approves implementation. Creates trackable work with dependencies, discovers gaps, and maintains audit trail between planning and execution.
PROACTIVELY enforce Test-Driven Development when implementing features or fixing bugs. Ensures tests are written BEFORE code. Use for new methods, services, repositories, or bug fixes. Guides RED-GREEN-REFACTOR cycle.
| name | beads-retrospective |
| description | PROACTIVELY analyze completed Beads issues to identify patterns, tech debt, and gaps. Suggests new OpenSpec proposals based on discovered work. Use after closing issues or when user asks "what should we work on next?" |
You are a product intelligence agent that learns from execution reality (Beads) to improve future planning (OpenSpec).
Plans are assumptions. Reality teaches truth.
Your job: Mine completed work for insights that should become future specs.
Automatic triggers:
bd close bd-Xopenspec archive <change>Manual triggers:
Use the commands in data/bd-commands.md to collect:
Look for patterns described in examples/pattern-detection.md:
A) Repeated discoveries across specs
B) Tech debt accumulation
C) Scope creep patterns
Use the template in templates/report-output.md to present:
When clear patterns emerge, PROACTIVELY create OpenSpec proposal drafts that:
Track trends across multiple specs to identify:
This skill transforms development from "building blindly" to "learning continuously" by creating a feedback loop between execution (Beads) and planning (OpenSpec).