dev-status

Parse spec files and reports to generate a project status dashboard.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/MaxGiu67/plugin-MUCC --skill dev-status
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev-status
Source: https://github.com/MaxGiu67/plugin-MUCC/tree/main/dev-methodology/skills/dev-status
Command: npx skills add https://github.com/MaxGiu67/plugin-MUCC --skill dev-status

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Centralizes project progress and health into a concise dashboard by reading repository spec files and summary reports, removing the need to manually inspect multiple markdowns to understand current phase, completion, and risks.

Core Features & Use Cases

  • Spec inventory: Scans specs/ for existing spec files, sizes, and recent updates to estimate completion.
  • Progress extraction: Reads specs/_status.md and specs/05-sprint-plan.md to determine current phase, sprint progress, and planned vs completed story points.
  • Risk signals: Pulls recent entries from specs/_changelog.md and optional technical reports to surface quality, technical debt, and security vulnerability counts.
  • Actionable next steps: Generates a concise visual dashboard and recommended next actions for the team or stakeholder updates.

Quick Start

Show me the current project status, progress percentage, key spec files, recent changelog entries, and recommended next steps.

Frequently Asked Questions about dev-status

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

FAQPage Schema
How do I generate a project status dashboard from markdown spec files?

To generate a project status dashboard, this Skill scans your repository's specs/ directory, reads markdown files like _status.md and sprint plans, and extracts progress metrics to display current phase and completion.

How does changelog parsing surface risk signals for software development repositories?

Changelog parsing surfaces risk signals by reading recent entries from specs/_changelog.md and technical reports to extract quality metrics, technical debt indicators, and security vulnerability counts.

Can I track sprint progress and planned vs completed story points from markdown files?

Yes, you can track sprint progress by reading specs/05-sprint-plan.md to determine the current phase and compare planned versus completed story points.

Does this project dashboard require a specific directory structure to estimate completion?

Yes, the project dashboard requires a specs/ directory structure containing markdown specification files and summary reports like _status.md and _changelog.md to scan file sizes and recent updates.

What is the best way to consolidate quality and security metrics for stakeholder updates?

The best way to consolidate quality and security metrics is parsing technical summary lines and changelog entries from your specs directory, generating a concise visual dashboard with recommended next actions.