cdd-status

Generate a project progress dashboard from workflow-catalog.yaml and governance artifacts.

18|5|Updated Nov 25, 2025
One-click install
npx skills add https://github.com/wsman/MY-DOGE-MICRO --skill cdd-status-wsman
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cdd-status
Source: https://github.com/wsman/MY-DOGE-MICRO/tree/main/.agents/skills/cdd-status
Command: npx skills add https://github.com/wsman/MY-DOGE-MICRO --skill cdd-status-wsman

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns the workflow catalog and project artifacts into a clear, durable progress dashboard, so teams can see the current phase, blocker, and next actions without manually auditing the repository.

Core Features & Use Cases

  • Reads authoritative project inputs such as the workflow catalog, stage markers, sprint status, and memory-bank records.
  • Classifies required steps as complete, partial, missing, manual, or not applicable, then identifies the current blocker and next commands.
  • Produces a saved roadmap for product or game projects and mirrors it into governance memory when available.
  • Use it to generate an up-to-date readiness snapshot before a review, handoff, or gate check.

Quick Start

Ask the cdd-status skill to inspect the repository and produce the current project roadmap from the workflow catalog.

Frequently Asked Questions about cdd-status

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

FAQPage Schema
How do I generate a project progress dashboard from a workflow catalog?

To generate a project progress dashboard, you parse workflow-catalog.yaml and governance artifacts to evaluate required steps, sequence phases, and identify blockers, then safely write the results into a project-roadmap.md file.

What is phase detection and required-step auditing for product repositories?

Phase detection and required-step auditing is the process of parsing workflow catalogs, evaluating required-when conditions, and sequencing phases to classify steps as complete, partial, missing, or manual across memory-bank and production surfaces.

How do I identify current blockers and next actions before a gate check?

You identify current blockers and next actions by auditing required steps within the workflow catalog and memory-bank records, classifying their completion status, and generating an up-to-date readiness snapshot for review.

Does this roadmap generation approach work with game repositories and memory-bank surfaces?

Yes, this roadmap generation approach applies to both product and game repositories, explicitly supporting phase detection and artifact glob matching across production and memory-bank surfaces.

What's the best way to maintain a durable roadmap without manually auditing the repository?

The best way to maintain a durable roadmap without manual repository audits is to automate catalog parsing and safe write gating to persist a project-roadmap.md file that mirrors governance memory records.

Why do I need safe write gating when persisting a project roadmap?

You need safe write gating when persisting a project roadmap to ensure that artifact glob matching, phase sequencing, and required-when evaluation logic only save verified, accurate readiness states into the project-roadmap.md file.