All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.
- Added explicit instruction prohibiting manual directory scanning or file inference — agent must use script JSON or stop with an error
- Sections 3, 4, and 5 now driven entirely from script JSON — agent no longer scans directories, checks file existence, or reads files manually
- Constitution status now derived from script JSON (
constitution.exists) — no manual file reading
- Removed remaining YAML/frontmatter terminology from command body — constitution version lookup now described in plain terms (look for
## Versionheading orversion:field)
- Removed last "frontmatter" wording from command body — constitution version extraction now described as reading YAML at top of file, avoiding confusion with the
scripts:key that was removed in v1.2.6
- Removed
scripts:frontmatter fromcommands/show.md— speckit now wraps commands as skills, which don't support thescripts:key - Inlined explicit script paths directly in the command body so the execution instruction is self-contained and works in both skill and command contexts
1.2.5 - 2026-04-08
- Trimmed description to ≤100 chars to meet spec-kit catalog publishing requirements
- Dropped
visibilitytag fromextension.yml(it's the README category, not a tag per the guide's tag taxonomy) - Renamed
commands/status.md→commands/show.mdto match the final segment of thespeckit.status-report.showcommand
1.2.4 - 2026-04-04
- PowerShell
PadRight()error — cast[char]symbols to[string]so string methods work
1.2.3 - 2026-04-04
- PowerShell script fails on Windows due to UTF-8 encoding — replaced Unicode literals with
[char]escape sequences
1.2.2 - 2026-04-04
- Renamed command to
speckit.status-report.showto match requiredspeckit.{extension}.{command}pattern
1.2.1 - 2026-04-04
- Attempted namespace fix (invalid — missing
speckit.prefix)
1.2.0 - 2026-04-03
- Removed cache logic — always performs a fresh scan and writes a new status file on every run
1.1.5 - 2026-03-25
- Compacted command spec from ~320 to ~150 lines for better LLM processing
- Front-loaded script execution requirement to prevent Claude from skipping it
1.1.4 - 2026-03-20
- Renamed extension ID from
statustostatus-reportto avoid collision with existing community extension - Renamed extension from "Project Status" to "Status Report"
- Updated script paths in command spec to match new extension ID
1.1.3 - 2026-03-16
- Fix specs directory lookup order to prefer
specs/over.specify/specs/
1.1.2 - 2026-03-15
- Removed incorrect "Read-Only Operation" claim from command spec — the command writes/updates
spec-status.mdas designed
1.1.1 - 2026-03-15
- Bash script compatibility with macOS bash 3.2 — replaced
declare -Aassociative arrays with indexed arrays - Replaced
grep -oP(Perl regex) with portablesedfor cache field extraction - Fixed
grep -cexit code 1 on zero matches causing doubled output in task counting - Script path resolution after extension installation — frontmatter now uses full
.specify/extensions/status/scripts/...paths - Replaced
{SCRIPT}placeholder in command body with reference to frontmatter scripts
1.1.0 - 2026-03-03
- Cache file (
{SPECS_DIR}/spec-status.md) — human-readable markdown summary written by the scripts after each run and committed to git - Git-based staleness detection — only feature folders changed since the cache was last committed are rescanned; unchanged features are served from cache
- Task counting in scripts —
tasks_totalandtasks_completedare now computed by the scripts and included in JSON output, eliminating the need for the AI to read individualtasks.mdfiles from_cachefield in JSON output per feature — indicates whether data came from cache or a fresh scancache_filefield in JSON output — path to the written cache file
commands/status.md— updated to use pre-computed task counts from script JSON output instead of counting lines fromtasks.md
1.0.0 - 2026-02-27
/speckit.status-report.showcommand — display project status, feature progress, and recommended next actions- Support for
--all,--verbose,--json, and--featureflags - Bash discovery script (
scripts/bash/get-project-status.sh) - PowerShell discovery script (
scripts/powershell/Get-ProjectStatus.ps1) - Pipeline view showing all features with workflow stages (Specify → Plan → Tasks → Implement)
- Artifact status for the current/selected feature
- Task completion tracking for features in implementation
- Next action recommendations based on current state
- JSON output format for machine-readable integration