pace-analyst

Analyze development iteration metrics and generate retrospective reports from historical project data.

73|6|Updated Feb 20, 2026
One-click install
npx skills add https://github.com/arch-team/devpace --skill pace-analyst
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pace-analyst
Source: https://github.com/arch-team/devpace/tree/main/skills/pace-retro
Command: npx skills add https://github.com/arch-team/devpace --skill pace-analyst

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides in-depth analysis of development iterations, identifies bottlenecks, and offers data-driven recommendations to improve quality, efficiency, and predictability.

Core Features & Use Cases

  • Iteration Review: Generates comprehensive reports on delivery, quality, and value metrics.
  • Trend Analysis: Tracks key performance indicators over multiple iterations to identify long-term trends and stability.
  • Predictive Forecasting: Forecasts delivery probability and flags potential risks based on historical data.
  • Use Case: At the end of an iteration, use /pace-retro to get a full report on what went well, what didn't, and actionable advice for the next cycle. Use /pace-retro compare to see how this iteration stacks up against the last.

Quick Start

Run /pace-retro to generate a full retrospective report for the current iteration.

Frequently Asked Questions about pace-analyst

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

FAQPage Schema
How do I generate a retrospective report for my development iteration?

To generate a retrospective report, run the `/pace-retro` command. This analyzes your iteration metrics to review delivery performance, assess quality, and provide actionable insights for process improvement.

Can I compare delivery performance metrics across multiple iterations?

Yes, you can compare delivery performance metrics by running `/pace-retro compare`. This tracks key performance indicators over multiple iterations to identify long-term trends and stability.

How does predictive forecasting work for software delivery?

Predictive forecasting analyzes historical project data to calculate delivery probability. It evaluates past iteration logs and dashboard metrics to flag potential risks and forecast outcomes for upcoming cycles.

What data do I need for iteration trend analysis and quality assessment?

Iteration trend analysis requires access to your project backlog, iteration logs, and dashboard metrics. Providing this comprehensive historical data ensures accurate quality assessment and reliable performance forecasting.

What's the best way to identify development bottlenecks using historical metrics?

The best way to identify bottlenecks is analyzing historical iteration logs with retrospective reporting tools. This evaluates delivery and quality metrics to pinpoint inefficiencies and offer data-driven recommendations.

Does this iteration analysis approach work for any project scale?

Iteration analysis works for any project scale where historical backlog and dashboard metrics are available. Comprehensive evaluation requires consistent iteration logs to generate accurate trend analysis and forecasting.