ais.report.status

Generate client-facing project status reports from repository state and spec counts.

Updated Jul 1, 2026
One-click install
npx skills add https://github.com/AIS-Commercial-Business-Unit/CBU_Specify --skill ais-report-status
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ais.report.status
Source: https://github.com/AIS-Commercial-Business-Unit/CBU_Specify/tree/main/.cursor/skills/ais.report.status
Command: npx skills add https://github.com/AIS-Commercial-Business-Unit/CBU_Specify --skill ais-report-status

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill streamlines the creation of detailed, client-facing status reports for project management, ensuring transparency and accuracy in project progress communication.

Core Features & Use Cases

  • Project State Collection: Gather current repository state with scripts and project context.
  • Executive Summary: Provide a concise overview of project health and next steps.
  • Progress Summary: Aggregate spec counts by status category (Complete, In Progress, Planned, Blocked).
  • Delivery Outcomes: Include measured or estimated values that are appropriate for stakeholder consumption.
  • Pipeline Details: Group specs into sections with descriptions and progress percentages.
  • Pending Decisions: Extract and present open decisions that need client input.
  • Risks: Summarize active risks with current mitigation status.
  • Next Steps: List concrete actions for the upcoming period.

Quick Start

Use the ais.report.status skill to generate a client-facing project status report.

Frequently Asked Questions about ais.report.status

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

FAQPage Schema
How do I automate client-facing project status reports from repository changes?

Automate project status reports by collecting repository state, summarizing progress, and listing risks with next steps. This streamlines stakeholder communication by aggregating spec counts and pending decisions into a structured document.

What is the best way to summarize project health and risks for client communication?

Summarize project health by providing an executive overview, aggregating spec statuses, and extracting active risks with mitigation details. This ensures transparent and accurate client communication regarding delivery outcomes and pipeline progress.

Can I generate a status report that groups project specs by completion percentage?

Yes, generate status reports that group specs into pipeline sections with descriptions and progress percentages. This categorizes specs by Complete, In Progress, Planned, or Blocked statuses to clearly communicate project pipeline details.

Does project status report automation require specific repository scripts and templates?

Yes, status report automation requires specific files including a prompt definition, a bash script to gather repository state, and a status template. These components collect project context and format the final stakeholder document.

How do pending decisions and next steps get extracted for a project status report?

Extract pending decisions by identifying open items requiring client input and listing concrete actions for the upcoming period. This surfaces critical project decisions and next steps directly within the generated status report.

When should I not use automated status report generation for project management?

Avoid automated status report generation when a project lacks structured repository specs or when stakeholder communication does not require detailed risk and pipeline tracking, as the output relies on aggregating structured spec data.