status

Collect CR metadata from specs/cr/*.cr.md and classify into status groups.

Updated Mar 17, 2026

Search Tags:#automation #workflow #reporting #status #project-management #cr

Ready to run

npx skills add https://github.com/Angel1104/architecture-docs --skill status-angel1104

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: status
Source: https://github.com/Angel1104/architecture-docs/tree/main/FE-MOBILE/commands/status
Command: npx skills add https://github.com/Angel1104/architecture-docs --skill status-angel1104

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

CR tracking across a project is often spread across multiple sources. This Skill provides a concise, up-to-date view of all CRs, including open, in progress, blocked, and recently closed items, in a single place.

Core Features & Use Cases

Collects CR metadata from specs/cr/*.cr.md and classifies CRs into In Progress, Blocked, Open, and Recently Closed.
Flags blocked items when required artifacts are missing and surfaces a clean, shareable report for stakeholders.
Useful for sprint planning, daily standups, and status updates to align teams on current work and priorities.

Quick Start

Run the status command to generate a live overview of all CRs.

Frequently Asked Questions about status

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

FAQPage Schema

How do I get a quick overview of all CRs in a project?▼

To get an overview of all CRs, the system collects metadata from specs/cr/*.cr.md files and classifies items into In Progress, Blocked, Open, and Recently Closed groups. This structured report provides a complete view of all change requests in a single place.

How are blocked CRs identified during project status reporting?▼

Blocked CRs are identified by checking for missing required artifacts within the change request files. The system flags these blocked items and surfaces them in a clean report, helping teams quickly spot work that cannot proceed until dependencies are resolved.

What is the best way to track CR status for sprint planning?▼

The best way to track CR status for sprint planning is to generate a live overview of all change requests. By classifying CRs into Open, In Progress, Blocked, and Recently Closed states, the report aligns teams on current priorities and work status.

Can I use this CR status report for daily standups?▼

Yes, this CR status report is useful for daily standups and status updates. It provides a concise, up-to-date view of open, in progress, blocked, and recently closed items, allowing project leads and developers to align on current work.

Do I need external integrations to track CR status across multiple sources?▼

No external integrations are needed. The tracking mechanism consolidates CR data by reading metadata directly from local specs/cr/*.cr.md files, computing the groups, and presenting a structured report without relying on external project management platforms.