catalog: add wireframe extension (v0.1.1) by TortoiseWolfe · Pull Request #2262 · github/spec-kit · GitHub
Skip to content

catalog: add wireframe extension (v0.1.1)#2262

Merged
mnriem merged 6 commits intogithub:mainfrom
TortoiseWolfe:feat/catalog-add-wireframe-extension
Apr 22, 2026
Merged

catalog: add wireframe extension (v0.1.1)#2262
mnriem merged 6 commits intogithub:mainfrom
TortoiseWolfe:feat/catalog-add-wireframe-extension

Conversation

@TortoiseWolfe
Copy link
Copy Markdown
Contributor

@TortoiseWolfe TortoiseWolfe commented Apr 17, 2026

Description

Adds spec-kit-extension-wireframe v0.1.1 to extensions/catalog.community.json and the Community Extensions table in the main README.

A visual feedback loop for Spec-Driven Development: SVG wireframe generation, review, and sign-off. Approved wireframes become spec constraints honored by /speckit.plan, /speckit.tasks, and /speckit.implement — no changes to core Spec Kit required.

Supersedes #1410, which I opened on 2025-12-31 before the extension system introduced in #1551. That PR proposed commands under templates/commands/, which is no longer the right home for third-party functionality. Closing #1410 after this lands.

Version

Catalog entry points at v0.1.1 (release). v0.1.1 corrects the slash-command references in the extension's own extension.yml and README.md from the unprefixed /plan, /tasks, /implement forms to the canonical /speckit.plan, /speckit.tasks, /speckit.implement names — the same fix applied here in the catalog description and README row. Version bump was folded into this PR per maintainer request so the catalog lands on the corrected release directly, rather than shipping v0.1.0 and immediately following up.

Provides

  • 6 commands: speckit.wireframe.{generate, prep, review, inspect, screenshots, view}
  • 3 hooks: after_specify, before_plan, after_implement
  • Interactive browser viewer with dynamic manifest-driven navigation, keyboard shortcuts, zoom, focus mode
  • Light (tan) / dark (charcoal) SVG theme templates for frontend vs backend/architecture features

Links

Testing

  • Tested locally with uv run specify --help — catalog JSON parses cleanly
  • Ran existing tests with uv sync && uv run pytest — skipped (this PR only adds a single JSON entry + a README table row; no code changes that tests would cover)
  • Tested with a sample project — extension installed via specify extension add --dev, all 6 commands registered, 3 hooks fire, end-to-end loop verified (generate → review → sign-off into spec.md → plan/tasks/implement honor the wireframe paths)

The entry's schema matches existing catalog entries (validated by diffing keys against worktrees), and the v0.1.1 download_url release zip returns HTTP 200.

AI Disclosure

  • I did not use AI assistance for this contribution
  • I did use AI assistance (describe below)

Used Claude Code (Opus 4.7) to help author the extension itself (spec-kit-extension-wireframe) — porting a wireframe pipeline from a sibling project into a self-contained, portable extension and building the interactive viewer. This catalog PR adds a single JSON entry and one README row referencing the independently-maintained extension repo.

Copy link
Copy Markdown
Collaborator

@mnriem mnriem left a comment

Choose a reason for hiding this comment

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

Please also add a row in the Community Extensions section in the main README (it is sorted alphabetically)

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 the community catalog entry for the wireframe extension (spec-kit-extension-wireframe v0.1.0) to make it discoverable via Spec Kit’s extension catalog.

Changes:

  • Add a new wireframe extension descriptor (metadata, URLs, requirements, provides counts, tags) to extensions/catalog.community.json.
Show a summary per file
File Description
extensions/catalog.community.json Adds the wireframe community catalog entry so it can be discovered via specify extension search/info.

Copilot's findings

Tip

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

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

Comment thread extensions/catalog.community.json Outdated
Comment thread extensions/catalog.community.json Outdated
@mnriem
Copy link
Copy Markdown
Collaborator

mnriem commented Apr 17, 2026

One small note the extension system was introduced in #1551 And can you please address the Copilot feedback

@TortoiseWolfe
Copy link
Copy Markdown
Contributor Author

Thanks for the review! Addressed both Copilot comments in ab9b2a3:

  • Moved the wireframe entry alphabetically between whatif and worktree
  • Simplified author to "TortoiseWolfe" (exact-match filter in ExtensionCatalog.search). Portfolio URL lives in homepage/repository.

@mnriem — thanks for the correction on the extension system intro. I had #2130 noted in the PR body but #1551 is the right landing PR. Let me know if you'd like me to edit the PR description to reflect that, or if landing-as-is with this comment on the record is fine.

Ready for another look.

@mnriem mnriem requested a review from Copilot April 17, 2026 19:24
TortoiseWolfe pushed a commit to TortoiseWolfe/TurtleWolfe that referenced this pull request Apr 17, 2026
Adds an entry to OTHER_PROJECTS pointing at the live demo at
https://tortoisewolfe.github.io/spec-kit-extension-wireframe/.
Ships a sample SVG as the card image — same one the live demo
renders, so the portfolio preview stays consistent with what
visitors land on after clicking through.

The extension provides a visual feedback loop for Spec-Driven
Development: generate SVG wireframes from specs; on sign-off
they become spec constraints honored by /plan, /tasks, and
/implement. Catalog PR pending at github/spec-kit#2262.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@mnriem
Copy link
Copy Markdown
Collaborator

mnriem commented Apr 17, 2026

Still need the row for the main README?

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.

Copilot's findings

Tip

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

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

Comment thread extensions/catalog.community.json Outdated
Comment thread extensions/catalog.community.json
@TortoiseWolfe TortoiseWolfe force-pushed the feat/catalog-add-wireframe-extension branch from ab9b2a3 to 27b6b02 Compare April 18, 2026 15:24
@TortoiseWolfe
Copy link
Copy Markdown
Contributor Author

Added the README row in 27b6b02 — slotted alphabetically between What-if Analysis and Worktree Isolation, categorized as visibility / Read+Write (the sign-off step writes approved wireframe paths into spec.md). Also rebased onto latest main so the diff is minimal.

Ready for another look, thanks!

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.

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

TortoiseWolfe added a commit to TortoiseWolfe/spec-kit that referenced this pull request Apr 21, 2026
Address remaining Copilot review comment on PR github#2262. The actual
commands are /speckit.plan, /speckit.tasks, /speckit.implement;
the unprefixed names would mislead catalog users.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@TortoiseWolfe
Copy link
Copy Markdown
Contributor Author

Addressed the remaining Copilot comment in 8fcaa47 — updated both the catalog description and the README row to use the /speckit.-prefixed command names (/speckit.plan, /speckit.tasks, /speckit.implement). All four Copilot comments are now resolved.

Ready for another look, thanks!

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.

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

@TortoiseWolfe TortoiseWolfe force-pushed the feat/catalog-add-wireframe-extension branch from 8fcaa47 to aeff60d Compare April 21, 2026 14:25
TortoiseWolfe added a commit to TortoiseWolfe/spec-kit that referenced this pull request Apr 21, 2026
Address remaining Copilot review comment on PR github#2262. The actual
commands are /speckit.plan, /speckit.tasks, /speckit.implement;
the unprefixed names would mislead catalog users.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@mnriem mnriem requested a review from Copilot April 21, 2026 14:28
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.

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

TortoiseWolfe added a commit to TortoiseWolfe/spec-kit-extension-wireframe that referenced this pull request Apr 21, 2026
The unprefixed /plan, /tasks, /implement never existed in published
Spec Kit releases — the actual commands are /speckit.plan,
/speckit.tasks, /speckit.implement. Correct this in all three
documentation surfaces:

- extension.yml:7 — description field (shown by `specify extension info`)
- README.md:10 — tagline paragraph
- README.md:16 — how-it-works paragraph

Bumps version to 0.1.1 and adds CHANGELOG entry. Resolves #1.

Flagged during review of github/spec-kit#2262.

Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@TortoiseWolfe
Copy link
Copy Markdown
Contributor Author

Quick status update:

  • Rebased onto latest upstream/main (now at aeff60d) — picks up the recent community-catalog additions and .zenodo.json / CITATION.cff. No conflicts, still MERGEABLE.
  • On the extension side, I shipped spec-kit-extension-wireframe v0.1.1 to correct the same /plan, /tasks, /implement/speckit.plan, /speckit.tasks, /speckit.implement references that were flagged here (they appeared in extension.yml and README.md too).

Happy to open a tiny follow-up PR bumping the catalog entry's version0.1.1 and download_urlv0.1.1.zip once this one lands — or I can roll that bump into this PR if you'd prefer a single entry at the newer version. Your call, thanks!

@mnriem
Copy link
Copy Markdown
Collaborator

mnriem commented Apr 21, 2026

Please add it to the PR. Make sure the title/description of the PR reflect it

TurtleWolfe and others added 5 commits April 22, 2026 10:07
Adds https://github.com/TortoiseWolfe/spec-kit-extension-wireframe
(v0.1.0) to the community catalog. Provides a visual feedback loop
for spec-driven development: SVG wireframe generation, review, and
sign-off. Approved wireframes become spec constraints honored by
/plan, /tasks, and /implement.

Supersedes github#1410 — the old PR predated the extension system
introduced in github#2130 and proposed commands in templates/commands/,
which is no longer the right home for third-party commands.
Two changes per Copilot review:
- Move `wireframe` entry alphabetically between `whatif` and
  `worktree` (was appended after `worktrees`).
- Simplify `author` from "TortoiseWolfe (turtlewolfe.com)" to
  just "TortoiseWolfe" so the exact-match author filter in
  `ExtensionCatalog.search` finds the entry. Portfolio URL
  remains accessible via `homepage`/`repository`.

Thanks @Copilot, @mnriem for the review.
Addresses @mnriem's follow-up: the README extension table also
needs an entry, not just the catalog JSON. Slots in alphabetically
between "What-if Analysis" and "Worktree Isolation" with category
`visibility` and Read+Write effect (since sign-off writes the
approved wireframe paths into spec.md).
Address remaining Copilot review comment on PR github#2262. The actual
commands are /speckit.plan, /speckit.tasks, /speckit.implement;
the unprefixed names would mislead catalog users.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
v0.1.1 of spec-kit-extension-wireframe ships the /speckit.-prefixed
command references in extension.yml and README.md. This updates the
catalog entry to point at the new release tag so `specify extension
add wireframe` installs the corrected version.
@TortoiseWolfe TortoiseWolfe force-pushed the feat/catalog-add-wireframe-extension branch from aeff60d to 2fa642f Compare April 22, 2026 14:08
@TortoiseWolfe TortoiseWolfe changed the title catalog: add wireframe extension catalog: add wireframe extension (v0.1.1) Apr 22, 2026
@TortoiseWolfe
Copy link
Copy Markdown
Contributor Author

Done — bumped in this PR:

  • extensions/catalog.community.json: version 0.1.00.1.1, download_urlv0.1.1.zip, updated_at2026-04-22
  • PR title: catalog: add wireframe extensioncatalog: add wireframe extension (v0.1.1)
  • PR description: updated all v0.1.0 references → v0.1.1 and added a short "Version" section explaining the bump
  • Rebased onto latest upstream/main (now at deb8095) to pick up the recent red-team and superpowers-bridge catalog additions — no conflicts, alphabetical ordering preserved (whatifwireframeworktree)

v0.1.1 release zip returns HTTP 200. Ready for another look, thanks!

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.

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: 1

Comment thread extensions/catalog.community.json Outdated
Per EXTENSION-PUBLISHING-GUIDE.md: newly added entries should use
the current timestamp for both created_at and updated_at. The 04-17
value reflected when I drafted the entry locally, not when the
catalog submission landed.
@mnriem mnriem self-requested a review April 22, 2026 14:19
@mnriem mnriem merged commit c52ea23 into github:main Apr 22, 2026
11 checks passed
@mnriem
Copy link
Copy Markdown
Collaborator

mnriem commented Apr 22, 2026

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.

4 participants