project-status

Generate project status reports with metrics, dependencies, blockers, and risks from project artifacts.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/christophevg/c3 --skill project-status-christophevg
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: project-status
Source: https://github.com/christophevg/c3/tree/main/skills/project-status
Command: npx skills add https://github.com/christophevg/c3 --skill project-status-christophevg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It eliminates guesswork about project health by turning scattered planning and progress artifacts into a single, consistently structured status report.

Core Features & Use Cases

  • Executive status report generation: Produces a STATUS.md with an executive summary, clear health indicator (GREEN/YELLOW/RED), and trend-aware metrics.
  • Metrics, dependencies, blockers, and risks: Computes completion rates and task breakdowns, then detects dependencies, active blockers, impediments, and risks from TODO.md, analysis/, and prior STATUS.md.
  • Persistent reporting for continuity: Creates or updates STATUS.md so future runs can compare trends and keep stakeholders aligned.

Quick Start

Ask the agent: "/project status" to generate an updated STATUS.md in the project root.

Frequently Asked Questions about project-status

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

FAQPage Schema
How do I generate a project status report from existing planning artifacts?

Generate a project status report by reading TODO.md and analysis artifacts to compute completion rates, detect dependencies, identify blockers, and write an updated STATUS.md. This provides an executive summary with health indicators and trend-aware metrics.

How do I track project blockers and risks for an executive summary?

Track project blockers and risks by analyzing TODO.md and prior STATUS.md files to detect impediments and dependency issues. The process computes completion rates and risk indicators, producing a STATUS.md with a clear GREEN/YELLOW/RED health indicator for stakeholder review.

Can I use TODO.md for computing task metrics and dependency tracking?

Yes, you can use TODO.md for computing task metrics and dependency tracking. The process reads TODO.md to calculate completion rates, detect active blockers, and map dependencies, then writes the computed metrics into an updated STATUS.md file.

What's the best way to keep project health metrics transparent across reporting cycles?

Keep project health metrics transparent by creating or updating a persistent STATUS.md file for trend comparison. This approach stores executive summaries and health indicators across runs, ensuring future reporting cycles can compare trends and keep stakeholders aligned.

Does project status reporting require specific file formats to function?

Project status reporting requires a TODO.md file in the project root and optionally reads related analysis artifacts and prior STATUS.md files. It outputs an updated STATUS.md, so no external databases or specific frameworks are needed to compute metrics and detect blockers.

Why does my project status report show a RED health indicator?

A project status report shows a RED health indicator when risk assessment logic detects active blockers, unresolved dependencies, or impediments within TODO.md. The computed completion rates and risk factors determine whether the status is GREEN, YELLOW, or RED in the STATUS.md output.