Skip to content

feat: add 5 lifecycle extensions to community catalog#2049

Merged
mnriem merged 4 commits intogithub:mainfrom
arunt14:feat/add-lifecycle-extensions
Apr 1, 2026
Merged

feat: add 5 lifecycle extensions to community catalog#2049
mnriem merged 4 commits intogithub:mainfrom
arunt14:feat/add-lifecycle-extensions

Conversation

@arunt14
Copy link
Copy Markdown
Contributor

@arunt14 arunt14 commented Apr 1, 2026

Extension Submission

5 Community Extensions for the Development Lifecycle

These extensions fill gaps in the post-implementation lifecycle — code review, QA, shipping, retrospective, and pre-implementation critique. Originally submitted as core commands (PRs #2041-#2045), restructured as community extensions per maintainer feedback.

Extensions

Extension ID Category Effect Repository
Staff Review staff-review code Read-only spec-kit-staff-review
QA Testing qa code Read-only spec-kit-qa
Ship Release ship process Read+Write spec-kit-ship
Retro retro process Read+Write spec-kit-retro
Spec Critique critique docs Read-only spec-kit-critique

Workflow

/speckit.plan -> /speckit.critique.run -> /speckit.tasks -> /speckit.implement -> /speckit.staff-review.run -> /speckit.qa.run -> /speckit.ship.run -> /speckit.retro.run

Checklist

  • Valid extension.yml manifest for each extension
  • README.md with installation and usage docs
  • LICENSE file included (MIT)
  • GitHub release created (v1.0.0) for all 5 extensions
  • Added to extensions/catalog.community.json
  • Added to Community Extensions table in README.md

Supersedes

This PR supersedes PRs #2041, #2042, #2043, #2044, #2045 (which delivered these as core commands).

arunt14 and others added 3 commits April 1, 2026 11:22
… ship, retro)

Add 5 new core command templates inspired by Garry Tan's GStack to complete
the spec-driven development lifecycle:

- /speckit.critique: Dual-lens product + engineering review before implementation
- /speckit.review: Staff-level code review (correctness, security, performance)
- /speckit.qa: Systematic QA testing (browser-driven and CLI modes)
- /speckit.ship: Release automation (pre-flight, changelog, CI, PR creation)
- /speckit.retro: Sprint retrospective with metrics and improvement suggestions

Each command includes:
- Command template in templates/commands/
- Output report template in templates/
- Extension hook support (before_*/after_*)
- YAML frontmatter with prerequisite scripts

Updated README.md workflow from 6 to 11 steps and added CHANGELOG entry.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Add the following community extensions:
- staff-review: Staff-engineer-level code review
- qa: Systematic QA testing with browser/CLI validation
- ship: Release engineering automation
- retro: Sprint retrospective with metrics
- critique: Dual-lens spec and plan critique

Each extension is hosted in its own repository under arunt14/
with v1.0.0 releases available.
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Adds five new lifecycle-focused community extensions (critique, staff review, QA, ship, retro) to the Spec Kit community catalog and surfaces them in the main README list.

Changes:

  • Add 5 new extension entries to extensions/catalog.community.json (critique, qa, retro, ship, staff-review)
  • Update README.md community extensions table with the new entries
  • Bump the community catalog updated_at timestamp

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 10 comments.

File Description
README.md Adds the five new community extensions to the published community extensions table.
extensions/catalog.community.json Adds full catalog metadata for the five extensions and updates catalog timestamp.

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

- Fix double-encoded em dashes and arrows in catalog.community.json
- Sort extension entries alphabetically by key
- Rename 'Retrospective Extension' to 'Retro Extension' to avoid
  name collision with existing 'retrospective' extension
@arunt14
Copy link
Copy Markdown
Contributor Author

arunt14 commented Apr 1, 2026

All 10 review comments addressed in the latest push:

  • Mojibake (8 comments): Fixed double-encoded UTF-8 em dashes and arrows throughout catalog.community.json. Root cause was bytes being misinterpreted as Windows-1252 during re-serialization.
  • Alphabetical ordering: Extension entries are now sorted by key throughout the entire catalog.
  • Name conflict: Renamed 'Retrospective Extension' to 'Retro Extension' to differentiate from the existing 'retrospective' extension.

Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Copilot reviewed 2 out of 2 changed files in this pull request and generated no new comments.


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

@mnriem mnriem merged commit b606b38 into github:main Apr 1, 2026
12 checks passed
@mnriem
Copy link
Copy Markdown
Collaborator

mnriem commented Apr 1, 2026

Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants