skills.rest
AIS-Commercial-Business-Unit
AIS-Commercial-Business-UnitOFFICIAL
Explore all skills by this author →
GitHub

ais.report.retrospective

Generate project retrospective reports from repository state and workflow data.

Updated Jul 1, 2026
Search Tags:#project management#retrospective#reporting#spec-driven development#project assessment
One-click install
npx skills add https://github.com/AIS-Commercial-Business-Unit/CBU_Specify --skill ais-report-retrospective
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ais.report.retrospective
Source: https://github.com/AIS-Commercial-Business-Unit/CBU_Specify/tree/main/.cursor/skills/ais.report.retrospective
Command: npx skills add https://github.com/AIS-Commercial-Business-Unit/CBU_Specify --skill ais-report-retrospective

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, gh, python, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill automates the generation of internal project retrospective reports, analyzing spec-driven development adoption and identifying improvement areas.

Core Features & Use Cases

  • Repo State Analysis: Reviews the repository state for spec inventory, task progress, and branch/PR activity.
  • Retrospective Report: Creates an internal report highlighting adoption, workflow fit, drift, and improvement candidates.
  • Use Case: Use this Skill after a project milestone to assess the team's spec-driven development practices and document actionable insights.

Quick Start

Generate a retrospective report for the last 30 days by running the command: /ais.report.retrospective

Frequently Asked Questions about ais.report.retrospective

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

FAQPage Schema
How do I generate a project retrospective report from GitHub repository data?▼

Generating a project retrospective report automates the analysis of repository state and workflow data to assess spec-driven development practices. It reviews spec inventory, task progress, and branch or PR activity to produce actionable Markdown reports.

What is spec-driven development retrospective and when do I need it?▼

A spec-driven development retrospective is an assessment of team adoption and workflow fit after a project milestone. You need it to identify workflow drift, evaluate spec inventory, and document improvement candidates for internal project management tracking.

Do I need the GitHub CLI and Python to run retrospective reporting scripts?▼

Yes, you need the GitHub CLI and Python to run retrospective reporting scripts. The analysis requires Python for data processing and the GitHub CLI to access repository state, branch activity, and PR data for automated report generation.

How to assess spec-driven development adoption using bash and Python?▼

Assess spec-driven development adoption by running automated bash scripts to collect repository state and using Python for analysis. This evaluates task progress, workflow fit, and spec inventory to highlight improvement areas in a Markdown report.

What's the best way to document project improvement candidates after a milestone?▼

The best way to document project improvement candidates is to automate a retrospective report analyzing repository workflow data. This identifies spec-driven development drift, evaluates task progress, and outputs an internal Markdown report with actionable insights.

Related Skills

Explore More Product & Management Skills→
HeartcoolmanHeartcoolman
88

pr-comments

Fetch and display GitHub PR review comments for the current branch.

Community
Advanced
bradtaylorsfbradtaylorsf
8

jira-retro

Generate retrospective reports from Jira metrics with customizable templates and JQL patterns.

Community
Advanced
markus41markus41
18

jira:status

Retrieve the status of a current Jira work session or issue.

Community
Basic
TzuhuanhsuTzuhuanhsu

speckit-converge

Assess codebases against feature specifications and generate tasks for missing work.

Community
Advanced