skills.rest
navapbc
navapbcOFFICIAL
Explore all skills by this author →
WebsiteGitHub

retro

Assess project health metrics and create a remediation plan with acceptance criteria.

6|1|Updated Mar 16, 2026
Search Tags:#code quality#tech debt#project health#CI#epic#retro
One-click install
npx skills add https://github.com/navapbc/digital-service-orchestra --skill retro-navapbc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/navapbc/digital-service-orchestra/tree/main/plugins/dso/skills/retro
Command: npx skills add https://github.com/navapbc/digital-service-orchestra --skill retro-navapbc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Proactively assess project health, identify maintainability issues, and plan remediation to improve development flow and reduce technical debt.

Core Features & Use Cases

  • Health data collection and analysis across codebase metrics, test quality, and CI trends.
  • Structured remediation planning with Epic and task creation.
  • Guided phases: Health Assessment, Codebase Review, Findings Report.

Quick Start

Initiate the retro workflow with /dso:retro to start Phase 1 health assessment.

Frequently Asked Questions about retro

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

FAQPage Schema
What is a project health retro and when do I need one?▼

A project health retro evaluates codebase metrics, test quality, and CI trends to identify maintainability issues. You need one to proactively manage technical debt and improve development flow before bottlenecks stall delivery.

How do I create a technical debt remediation plan with clear acceptance criteria?▼

To create a technical debt remediation plan, run a structured health assessment and codebase review to generate findings. These findings guide prioritization and are exported as actionable tasks with clear acceptance criteria for a targeted retro epic.

Can I use this to analyze CI trends and process bottlenecks for my codebase?▼

Yes, you can analyze CI trends and process bottlenecks by collecting health data across your codebase metrics. The workflow summarizes this data to identify maintainability issues and plan targeted remediation to improve development flow.

What's the best way to prioritize technical debt findings for stakeholder decisions?▼

The best way to prioritize technical debt findings is using a guided findings report. This report summarizes codebase health metrics and process bottlenecks, applying structured phases to guide prioritization and inform stakeholder decisions.

How do I start a project health assessment workflow?▼

To start the project health assessment workflow, initiate the retro process to begin Phase 1. This phase collects and analyzes health data across codebase metrics, test quality, and CI trends to establish a baseline for remediation.

Related Skills

Explore More Software Engineering Skills→
ResearchMonkeyResearchMonkey

review-tests

Analyze test quality and coverage to identify gaps and flaky tests.

Community
Intermediate
enigmaicon-engenigmaicon-eng
1

bmad-retrospective

Facilitate evidence-driven epic retrospectives with structured dialogue and action items.

Community
Advanced
Intense-VisionsIntense-Visions
18

Harness Dependency Health

Identify structural health issues in a codebase using graph metrics and static analysis.

Official
Advanced
mcauduro0mcauduro0
1

ln-626-dead-code-auditor

Audit codebases for dead code, unused assets, and legacy patterns.

Community
Advanced