Community Showcase: OpenSpec Propose as a hosted skill on SkillGild

[PiPlusTheta]

SkillGild (skillgild.dev) hosts the openspec-propose skill for Claude Code, Codex, Cursor and Gemini CLI, credited and linked to this repo under its MIT license: https://skillgild.dev/skills/openspec-propose

I would like to add it to the Community Showcase (docs/community.md) with one line, disclosing that it requires a SkillGild account and that the free tier includes 25 runs a month. PR to follow; happy to change the wording or drop it if it does not fit the showcase.

[PiPlusTheta]

Update after the feedback on #2046: thanks @clay-good. That PR listed a hosted copy of openspec-propose, which ships free with openspec init, so it didn't meet the bar. We've since built something the CLI doesn't do, and I'd like to propose that for the showcase instead.

OpenSpec Review (https://skillgild.dev/skills/openspec-review) turns an open change into a private review link for people who won't read delta files in a terminal: a PM, a client, a lead.

• The page shows each requirement added, modified, removed or renamed, merged into the current main spec the way openspec archive merges it (a port of specs-apply.ts), with a line diff. It says up front when archive would refuse the change.
• Anyone with the link can approve, request changes or comment per requirement, or on the whole change, without an account. Publishing a revision keeps the link; approvals of requirements whose text changed are marked outdated.
• The agent reads the decisions back and holds /opsx:apply or archive until the change is approved (related: archive --yes proceeds on self-reported task status — should archive be able to require evidence? #1652, [Feature Request] Cross-artifact quality review between propose/ff and apply #783).
• It flags requirements that other open changes also touch, before either is archived (Overlap between open changes is invisible until one archives (parallel-merge plan, Phase 1) #1669), and checks validate passes today: scenarios without WHEN/THEN (validate: a scenario with no WHEN/GIVEN or THEN step counts as a scenario and passes #2078), missing SHALL/MUST, vague wording.

Example: on OpenSpec 1.14.1, openspec validate --strict reports our demo change as valid, while the review flags a conflict with another open change that edits a requirement this one removes, plus a scenario with no WHEN/THEN.

Disclosures: it needs a SkillGild account (the free tier includes 25 runs a month). The change content the agent sends is stored on SkillGild for 30 days so the link can show it, and no AI model processes it on SkillGild. It was built with Claude Code (Claude Opus 5.5) and tested end to end against production.

PR to follow. Happy to reword it or drop it if it still doesn't fit.

[PiPlusTheta]

Update: #2046 was closed because hosting a core skill adds nothing beyond the CLI, which is fair. So we built two things the CLI does not do, and opened #2094 for them:

• OpenSpec Review: a private review link for a change. Reviewers who never open a terminal can approve or comment per requirement. It shows each requirement diffed against the current spec, the spec as openspec archive would write it, and overlaps with other open changes.
• OpenSpec Compact: reads all main specs, finds duplicated requirements and archive leftovers, and writes the cleanup as a normal OpenSpec change.

When I ran Compact on this repo's own specs, it found cli-change stating interactive selection twice ("Interactive show selection" and "Interactive validation selection", 70% overlap) and the same pattern in cli-spec. Details are in the PR. Happy to adjust or drop the entry.