You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
OpenSpec is a Spec Kit extension that adds structured, spec-driven change-management workflows to a project. Instead of jumping straight into code, it guides you through a lifecycle for each change:
explore – investigate the codebase/problem space
propose – scaffold a change with a proposal, spec delta, and design doc
apply – implement the change, tracked via a generated task list
verify – audit the implementation against the spec for completeness, correctness, and coherence
archive – move the completed change to an archive and sync spec deltas into the canonical specs
It also offers supporting commands (new, continue, ff, update, sync, bulk-archive, onboard) and a Python helper (change.py) that handles change discovery, status tracking, scaffolding, and archival — giving teams a lightweight, file-based system for proposing, implementing, and recording changes with traceability from requirement → design → task → code.
Extension description exceeds the 100-character limit
extensions/catalog.community.json:3702
This 149-character description exceeds the publishing guide's under-100-character requirement (extensions/EXTENSION-PUBLISHING-GUIDE.md:84-89). Please shorten it here and make the same change in the generated community table so the two listings remain synchronized.
…estamp
The openspec entry's sha256 did not match the bytes of the published
openspec-v0.1.0/openspec.zip release asset, which would cause install
integrity verification to fail. Recompute it from the tagged archive.
Also refresh the catalog's top-level updated_at to reflect this change.
Assisted-by: GitHub Copilot (model: Claude Opus 4.8, autonomous)
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Pushed via maintainer edit access on behalf of @mnriem. Fixes and analysis were AI-generated by GitHub Copilot (model: Claude Opus 4.8), operating autonomously under maintainer direction.
Two metadata fixes in extensions/catalog.community.json:
sha256 corrected — the entry's digest (21b55eff…) did not match the bytes of the published openspec-v0.1.0/openspec.zip asset. Installs would fail integrity verification. Recomputed from the exact tagged archive: 9d3b384d5a13c36547352009cc11ce059d45c5f0624b3e3311559e2e5766cdf9.
Top-level updated_at refreshed to 2026-09-28 so catalog consumers see the change.
The two remaining high-severity findings are now stale — since they were filed, the author published the openspec-v0.1.0 release with the openspec.zip asset, and that archive's extension.yml declares version 0.1.0, matching the catalog:
Nonexistent release asset — the openspec-v0.1.0/openspec.zip asset now exists and downloads successfully.
Version mismatch (v0.1.0 tag manifest was 1.0.0) — the catalog points at the openspec-v0.1.0 release, whose bundled extension.yml declares 0.1.0. No mismatch remains against the referenced archive.
Verified: openspec.zip downloads cleanly, its extension.yml version is 0.1.0, the recomputed digest is stable across re-downloads, and tests/contract/test_catalog_schema.py passes (46 tests).
For a new extension, the repository workflow requires both per-entry timestamps to use today’s UTC date (.github/workflows/add-community-extension.md:267-300). This catalog change is dated 2026-09-28 at the top level, but the new entry is dated 2026-09-26, so its metadata incorrectly predates its addition. Set both values to 2026-09-28.
Use the PR addition date for both OpenSpec catalog timestamps.
Assisted-by: GitHub Copilot (model: GPT-5.6 Sol Fast, autonomous)
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Addressed this review round in 78590d351e389710701b4816d2211343dd365846.
Validated the published openspec-v0.1.0/openspec.zip asset: its manifest declares 0.1.0, and its SHA-256 is 9d3b384d5a13c36547352009cc11ce059d45c5f0624b3e3311559e2e5766cdf9, matching the catalog. Updated the OpenSpec entry’s created_at and updated_at to 2026-09-28T00:00:00Z; JSON parsing and metadata assertions pass.
Posted on behalf of @mnriem with GitHub Copilot using GPT-5.6 Sol Fast in autonomous mode; release-metadata validation, catalog edit, and validation.
Thank you! To avoid PR churn on catalog entries please use the catalog submission issue templates the next time
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
triage-can-waitVerdict: valid and in-scope but deprioritized; held behind the evidence gate
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
mnriem
added
the
triage-can-wait
OpenSpec is a Spec Kit extension that adds structured, spec-driven change-management workflows to a project. Instead of jumping straight into code, it guides you through a lifecycle for each change:
It also offers supporting commands (
new,continue,ff,update,sync,bulk-archive,onboard) and a Python helper (change.py) that handles change discovery, status tracking, scaffolding, and archival — giving teams a lightweight, file-based system for proposing, implementing, and recording changes with traceability from requirement → design → task → code.