speckit-progress

To generate a spec progress report, the Skill aggregates memory bank entries, specs folders, and conversation history to summarize completed tasks, in-progress work, and blockers. It requires a spec-kit structure with memory-bank files and specs/*/tasks.md to compute task metrics.

A spec-kit workflow uses memory-bank files and specs/*/tasks.md to track project status. Task metrics tracking works by cross-referencing these sources to compute task counts, generate per-phase breakdowns, and flag mismatches between progress logs and task status.

Yes, this progress reporting tool works with memory-bank files and optionally cross-references conversation summaries. It reads memory bank entries to extract completed work, recent changes, and recorded decisions to validate completed items.

Yes, you can detect discrepancies between your memory bank logs and spec task status. The Skill computes task counts and percentages, generates per-phase breakdowns, and actively flags mismatches between recorded progress logs and actual task status.

The best way to track blocked items and verification status is by aggregating memory bank entries and optional conversation summaries into a structured report. This provides a single actionable view of blockers, open questions, and recommended next steps.

If your spec project is missing specs/*/tasks.md files, the Skill cannot compute task metrics or generate per-phase breakdowns. A spec-kit structure with memory-bank files and task definitions is required to calculate progress and recommend Memory Bank updates.