[Extension]: Update Status Report to v1.4.2

[jwesleye]

Extension ID

status-report

Extension Name

Status Report

Version

1.4.2

Description

Project status, feature progress, and next-action recommendations for spec-driven workflows.

Author

Open-Agent-Tools

Repository URL

https://github.com/Open-Agent-Tools/spec-kit-status

Download URL

https://github.com/Open-Agent-Tools/spec-kit-status/archive/refs/tags/v1.4.2.zip

License

MIT

Homepage (optional)

https://github.com/Open-Agent-Tools/spec-kit-status

Documentation URL (optional)

https://github.com/Open-Agent-Tools/spec-kit-status/blob/main/README.md

Changelog URL (optional)

https://github.com/Open-Agent-Tools/spec-kit-status/blob/main/CHANGELOG.md

Required Spec Kit Version

=1.0.0

Required Tools (optional)

• none — Bash, PowerShell and Python runtimes all ship with the extension, and Spec Kit selects the variant the project was initialized with. Git is optional.

Number of Commands

1

Number of Hooks (optional)

0

Tags

workflow, project-management, status

Key Features

• Pipeline view of every feature with its workflow stage (Specify, Plan, Tasks, Implement)
• Artifact status for the current feature: spec, plan, tasks, research, data model, quickstart, contracts, checklists
• Task completion counts and percentages, computed by the script rather than inferred by the agent
• Checklist progress tracking
• Recommends the exact next command to run, written as __SPECKIT_COMMAND_*__ tokens so it renders in each agent's own invocation style
• --json output for tooling
• Bash, PowerShell and Python runtimes, with cross-runtime parity asserted by the repo's test suite

Testing Checklist

• Extension installs successfully via download URL
• All commands execute without errors
• Documentation is complete and accurate
• No security vulnerabilities identified
• Tested on at least one real project

Submission Requirements

• Valid extension.yml manifest included
• README.md with installation and usage instructions
• LICENSE file included
• GitHub release created with version tag
• All command files exist and are properly formatted
• Extension ID follows naming conventions (lowercase-with-hyphens)

Testing Details

Tested on: macOS 15 (arm64) with Spec Kit 1.0.5, PowerShell 7.6.6, Python 3.13

Test project: a throwaway project created with specify init --here --integration claude, plus the repo's own fixture harness at tests/test-status.sh

Test scenarios:

1. Installed from the v1.4.2 release archive with specify extension add status-report --from <url>. Installs cleanly and registers the skill at .claude/skills/speckit-status-report-show/SKILL.md.
2. Inspected the rendered skill. {SCRIPT} resolves to the installed extension path, and __SPECKIT_COMMAND_*__ tokens render in the active agent's style (/speckit-plan for a skills-based Claude install).
3. Ran the discovery script from the installed location against a project with features, tasks and checklists, and confirmed the JSON matches what the command spec expects.
4. Ran tests/test-status.sh, which executes the full assertion suite against each installed runtime and then asserts they agree. 26 assertions per runtime, plus cross-runtime parity on both the JSON output and the rendered status file.

Coverage of Spec Kit 1.0.x behaviour:

• Current-feature resolution follows Spec Kit's own precedence from scripts/bash/common.sh: SPECIFY_FEATURE_DIRECTORY, then .specify/feature.json, then SPECIFY_FEATURE, then the git branch. Each path has a test.
• Feature discovery covers every prefix shape Spec Kit emits, including --timestamp directories and sequential prefixes longer than three digits.
• Three defects were found and fixed during this verification pass, each with a regression test: a branch misread in a repository with no commits (1.4.1), a forwarded agent-level flag aborting the script, and a wildcard accepted as a feature name on PowerShell (1.4.2).

On the security checkbox: no formal security audit or scanner was run. The basis for checking that box is that the extension is read-mostly Bash, PowerShell and Python that performs no network calls, handles no credentials, and writes exactly one file inside the project (specs/spec-status.md). Happy to provide more if maintainers want a stronger standard here.

Example Usage

# Install
specify extension add status-report --from https://github.com/Open-Agent-Tools/spec-kit-status/archive/refs/tags/v1.4.2.zip

# Show the overview plus detail for the current feature
/speckit.status-report.show

# Overview only, or with task and checklist breakdowns
/speckit.status-report.show --all
/speckit.status-report.show --verbose

# Target a specific feature, by name or number
/speckit.status-report.show 002-dashboard
/speckit.status-report.show --feature 002-dashboard --json

Output:

Spec-Driven Development Status

Project: my-app
Branch: 002-dashboard
Constitution: ✓ Defined (v1.0.0)

Features
+-----------------+---------+------+-------+------------------+
| Feature         | Specify | Plan | Tasks | Implement        |
+-----------------+---------+------+-------+------------------+
| 001-onboarding  |    ✓    |  ✓   |   ✓   | ✓ Complete       |
| 002-dashboard < |    ✓    |  ✓   |   ✓   | ● 12/18 (67%)    |
+-----------------+---------+------+-------+------------------+

Legend: ✓ complete  ● in progress  ○ ready  - not started

002-dashboard

Artifacts:
  ✓ spec.md        ✓ plan.md        ✓ tasks.md
  ✓ research.md    - data-model.md  - quickstart.md
  - contracts/     - checklists/

Next: /speckit.implement
  Continue implementation (12/18 tasks complete)

Proposed Catalog Entry

{
  "status-report": {
    "name": "Status Report",
    "id": "status-report",
    "description": "Project status, feature progress, and next-action recommendations for spec-driven workflows.",
    "author": "Open-Agent-Tools",
    "version": "1.4.2",
    "download_url": "https://github.com/Open-Agent-Tools/spec-kit-status/archive/refs/tags/v1.4.2.zip",
    "repository": "https://github.com/Open-Agent-Tools/spec-kit-status",
    "homepage": "https://github.com/Open-Agent-Tools/spec-kit-status",
    "documentation": "https://github.com/Open-Agent-Tools/spec-kit-status/blob/main/README.md",
    "changelog": "https://github.com/Open-Agent-Tools/spec-kit-status/blob/main/CHANGELOG.md",
    "license": "MIT",
    "category": "visibility",
    "effect": "read-write",
    "requires": {
      "speckit_version": ">=1.0.0"
    },
    "provides": {
      "commands": 1,
      "hooks": 0
    },
    "tags": [
      "workflow",
      "project-management",
      "status"
    ],
    "verified": false,
    "downloads": 0,
    "stars": 0,
    "created_at": "2026-03-16T00:00:00Z",
    "updated_at": "2026-09-11T00:00:00Z"
  }
}

Additional Context

This is an update to an entry already in extensions/catalog.community.json, not a new
addition. created_at, downloads and stars above are carried over unchanged from the
existing entry.

Three fields change beyond the version bump, and two of them are corrections rather than
consequences of the release:

1. effect: read-only → read-write. The existing entry has always been wrong about
   this. The command writes a specs/spec-status.md snapshot on every run, so it has never
   been read-only. This also affects the row in docs/community/extensions.md, where Status
   Report is currently listed as Read-only and should read Read+Write.
2. requires.speckit_version: >=0.1.0 → >=1.0.0. The old floor was carried over from
   the extension's first release. The extension now resolves the current feature through
   .specify/feature.json, and 1.0.5 is the only version it is verified against, so the
   narrower floor reflects what is actually tested.
3. version and download_url move to 1.4.2.

One note for whoever reviews the generated PR: category and effect are present on the live
catalog entries but are absent from the entry structure in the
add-community-extension workflow's own template. Please make sure the effect correction
survives into the merged entry, since it is the main point of this submission.

There is also a separate, unrelated extension in the catalog under the id status ("Project
Status" by KhawarHabibKhan). This submission does not touch it.