Add Status Report extension to community catalog

[jwesleye]

Extension Submission

Extension Name: Status Report
Extension ID: status-report
Version: 1.2.5
Author: Open-Agent-Tools
Repository: https://github.com/Open-Agent-Tools/spec-kit-status

Description

Project status, feature progress, and next-action recommendations for spec-driven workflows. Provides the /speckit.status-report.show command with:

• Pipeline view of all features with workflow stages (Specify → Plan → Tasks → Implement)
• Artifact existence checks per feature
• Task completion tracking with percentages
• Next-action recommendations
• JSON output for tooling integration
• Cross-platform: Bash (macOS/Linux) and PowerShell (Windows)

Resubmission notes

This replaces the previously closed #1860. All reviewer feedback has been addressed:

• Catalog entry alphabetized by ID — status-report is now placed adjacent to and after the existing status entry, per the alphabetization-by-id convention
• README row placed in correct alphabetical position — between Staff Review Extension and Superpowers Bridge
• Full ISO-8601 timestamps with time-of-day precision — no rounded midnight values
• Distinct README link text — uses Open-Agent-Tools/spec-kit-status to disambiguate from the existing Project Status extension
• Version/tag/PR body all aligned — everything references v1.2.5 consistently
• Description trimmed to 92 chars — meets the ≤100 char catalog rule
• Command name corrected — speckit.status-report.show matches the required speckit.{extension}.{command} pattern
• Rebased on current main — edits the current extensions table location in root README.md (not the old extensions/README.md)

Checklist

• Valid extension.yml manifest
• README.md with installation and usage docs
• LICENSE file included (MIT)
• GitHub release created (v1.2.5)
• Extension tested on real project
• All commands working
• Added to extensions/catalog.community.json
• Added to Community Extensions table in README.md
• CHANGELOG.md included

Testing

Tested locally on macOS with a multi-feature spec-kit project. Verified:

• Script runs on macOS bash 3.2 (no bash 4+ dependencies)
• PowerShell script runs on Windows (v1.2.3 fixed UTF-8 parse, v1.2.4 fixed PadRight on [char])
• Correct JSON and text output
• Feature detection, task counting, and artifact checks all working

🤖 Generated with Claude Code

[Copilot]

Pull request overview

Adds the Status Report community extension to the Spec Kit community catalog and the root README’s Community Extensions table.

Changes:

• Added status-report entry (v1.2.5) to extensions/catalog.community.json, including metadata, URLs, tags, and timestamps.
• Added a corresponding row to the Community Extensions table in README.md.
• Updated the catalog’s top-level updated_at timestamp.

Show a summary per file

File	Description
README.md	Adds the “Status Report” row in the community extensions table (alphabetically placed).
extensions/catalog.community.json	Registers the status-report extension in the community catalog and updates updated_at.

Copilot's findings

Tip

Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

• Files reviewed: 2/2 changed files
• Comments generated: 0

[mnriem]

Please resolve conflicts

[Copilot]

Pull request overview

Adds the “Status Report” community extension to Spec Kit’s community catalog and README so users can discover/install it.

Changes:

• Added a new status-report entry to extensions/catalog.community.json (v1.2.5 metadata + URLs).
• Updated the root README.md Community Extensions table with the new extension row.
• Bumped the community catalog updated_at timestamp.

Show a summary per file

File	Description
README.md	Adds “Status Report” to the Community Extensions table with repo link and category/effect.
extensions/catalog.community.json	Adds status-report catalog entry (metadata, URLs, tags, timestamps) and updates top-level updated_at.

Copilot's findings

Tip

Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

• Files reviewed: 2/2 changed files
• Comments generated: 0 new

[mnriem]

Please address conflicts

[jwesleye]

Rebased on latest main to resolve merge conflicts:

• README.md — upstream reorganized the extensions table; removed duplicate "Staff Review" and "Superpowers Bridge" rows from the old conflict region and placed the "Status Report" row in the correct alphabetical position (between Staff Review and Superpowers Bridge)
• catalog.community.json — resolved updated_at timestamp conflict, updated to 2026-04-09T14:30:00Z

JSON validated, no remaining conflict markers. Should be clean to merge now.

[Copilot]

Pull request overview

Adds the Status Report community extension (status-report) to the Spec Kit community extension catalog and surfaces it in the root README community extensions table.

Changes:

• Added a new status-report entry to extensions/catalog.community.json (v1.2.5) and updated the catalog updated_at timestamp.
• Added a corresponding row to the Community Extensions table in README.md, placed in the correct alphabetical position.

Show a summary per file

File	Description
README.md	Adds the Status Report row to the Community Extensions table (category visibility, link to Open-Agent-Tools repo).
extensions/catalog.community.json	Registers the status-report extension metadata (download URL, docs/changelog links, timestamps) and updates catalog updated_at.

Copilot's findings

Tip

Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

• Files reviewed: 2/2 changed files
• Comments generated: 0 new

[mnriem]

Thank you!