speckit.status

Scan .specify/features directories and generate a phase-based progress dashboard with blockers.

Updated Oct 4, 2025
One-click install
npx skills add https://github.com/peancharoen/lcbp3 --skill speckit-status-peancharoen
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit.status
Source: https://github.com/peancharoen/lcbp3/tree/main/.agents/skills/speckit.status
Command: npx skills add https://github.com/peancharoen/lcbp3 --skill speckit-status-peancharoen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Consolidates scattered specification, planning, task, and checklist files into a single, actionable dashboard so teams can quickly see feature progress, completion percentages, and concrete blockers.

Core Features & Use Cases

  • Automated Discovery: Scans .specify/features directories to find feature folders and relevant artifacts such as spec.md, plan.md, tasks.md, checklists, and validation reports.
  • Phase-Based Progress: Computes completion across phases (Specify, Plan, Tasks, Implement, Validate) and renders human-friendly progress bars and tables.
  • Blocker Detection & Next Actions: Flags [NEEDS CLARIFICATION], unfinished tasks, failed checklist items, and missing dependencies, and suggests the next actionable step.
  • Outputs: Prints a terminal dashboard and can optionally write a consolidated .specify/STATUS.md for team consumption.

Quick Start

Generate a speckit.status dashboard for the repository to list all features, their phase completion percentages, blockers, and recommended next actions.

Frequently Asked Questions about speckit.status

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

FAQPage Schema
How do I generate a project status dashboard from .specify feature directories?

A project status dashboard is generated by scanning .specify/features directories to discover feature folders containing spec.md, plan.md, tasks.md, and validation reports. It computes completion percentages across phases like Specify, Plan, Tasks, Implement, and Validate, then renders human-friendly progress bars and tables.

What is the best way to track feature blockers and incomplete tasks in a spec-driven repository?

The best way to track feature blockers is by scanning the filesystem state to detect [NEED CLARIFICATION] markers, unfinished tasks, and failed checklist items. This process identifies missing dependencies and suggests the next actionable step to resolve release readiness issues.

How do I visualize phase-based completion percentages for my project's feature tracking?

You visualize phase-based completion percentages by computing progress across Specify, Plan, Tasks, Implement, and Validate phases using your feature tracking artifacts. This renders human-friendly progress bars and tables into a consolidated terminal dashboard.

Can I write a consolidated status report to a file for team consumption?

Yes, you can write a consolidated status report by generating an optional .specify/STATUS.md file alongside the terminal dashboard. This file captures feature progress, completion percentages, blockers, and recommended next actions for team consumption.

Does this dashboard tool work with repositories missing validation-report.md files?

Yes, the dashboard tool works with repositories missing validation-report.md files by scanning available artifacts like spec.md, plan.md, and tasks.md. It computes progress based on existing files and flags missing dependencies as blockers for release readiness.