status

Name: status
Availability: InStock
Author: Atelier

Aggregate ADLC specs, tasks, and bugs into a consolidated status dashboard.

159|41|Updated Mar 18, 2026

Search Tags:#metrics #dashboard #pipeline #status #bugs #specs #adlc

Ready to run

npx skills add https://github.com/atelier-fashion/adlc-toolkit --skill status-atelier-fashion

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: status
Source: https://github.com/atelier-fashion/adlc-toolkit/tree/main/status
Command: npx skills add https://github.com/atelier-fashion/adlc-toolkit --skill status-atelier-fashion

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Show the current state of all ADLC work across the project in a single, shareable view, enabling quick coordination and focus.

Core Features & Use Cases

Aggregates statuses from specs, tasks, and bugs across .adlc directories.
Tracks active pipelines, progress, and blockers to support planning and reviews.
Provides recently completed work and open bugs to surface high-priority items.

Quick Start

Run the status skill in the project root to generate the current ADLC dashboard.

Frequently Asked Questions about status

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

FAQPage Schema

How do I check the current status of all ADLC tasks, specs, and bugs across my repository?▼

To check the current status of ADLC work, run the status skill in your project root to aggregate frontmatter from .adlc directories and pipeline-state.json, producing a consolidated dashboard of progress, blockers, and bugs.

Can I filter the ADLC dashboard to only show specific REQ IDs or keywords?▼

Yes, you can filter the ADLC dashboard by REQ IDs, statuses, or keywords to prepare targeted views for project reviews, surfacing only the relevant specs, tasks, and bugs matching your query.

What is the best way to track active pipelines and blockers in an ADLC project?▼

The best way to track active pipelines and blockers is to generate the ADLC dashboard, which reads pipeline-state.json and aggregates progress across .adlc directories to surface high-priority items and recently completed work.

How does the ADLC status aggregation mechanism work?▼

The ADLC status mechanism works by reading frontmatter from .adlc/specs/REQ-* directories and pipeline-state.json, counting tasks, and aggregating progress, blockers, and bugs into a single shareable view.

Do I need specific directory structures to generate an ADLC project status view?▼

Yes, generating an ADLC status view requires projects to have specs, tasks, and bugs tracked under .adlc directories, along with a pipeline-state.json file to aggregate the dashboard data correctly.

Why is my ADLC status dashboard not showing recently completed work or open bugs?▼

Your ADLC status dashboard may not show recently completed work or open bugs if the .adlc directories lack proper frontmatter or if pipeline-state.json is missing, preventing the skill from aggregating the necessary metrics.