Refresh the community marketplace listing — it is pinned to a stale sha

[sgraczyk]

Problem

Our entry in anthropics/claude-plugins-community pins a bare commit sha:

{"name": "spec-first",
 "description": "Claude Code plugin that guides you from requirements to working code — ...",
 "source": {"source": "url",
            "url": "https://github.com/bitcraft-apps/spec-first.git",
            "sha": "c56860e7469602394f367da258f5f740ee351831"}}

c56860e is chore(main): release 1.3.0, dated 2026-03-16 — the submission date. As of 2026-08-04, main is 48 commits ahead at VERSION 1.3.1.

A bare sha never updates. So every user who installs spec-first@claude-community gets March code. They do not get /sf:implement --isolate, anything under docs/, or five months of fixes.

Other entries in the same marketplace.json use "ref": "main" or "ref": "v1.0.1", so they track a moving target. Ours does not.

The listed description is also stale. It opens "Claude Code plugin", but the plugin now installs on 15+ hosts through .agents/skills — see docs/supported-hosts.md.

Action

Resubmit through the Console form: https://platform.claude.com/plugins/submit

The clau.de/plugin-directory-submission link now 302s to the docs page. The other live route,
https://claude.ai/admin-settings/directory/submissions/plugins/new, needs Team/Enterprise
directory-management access, which we do not have — so the Console form it is.

Ask for the pin to be re-pointed at current main and the auto-bump re-armed. Do not ask for a
tracking ref (see Corrections below). Supply a description that is not Claude-only.

Pull requests against the mirror repo are closed automatically — every change flows through the
internal review pipeline, so the form is the only route.

Acceptance Criteria

• Resubmitted through https://platform.claude.com/plugins/submit — 2026-08-04, against main at 2597582
• marketplace.json entry resolves to 1.3.1 or later
• Pin auto-bump confirmed working — re-check the catalog after a later commit lands on main
• Description does not describe the plugin as Claude Code only — fix: drop Claude-only framing from marketplace metadata #299

Notes

Checking status: https://claude.ai/settings/plugins/submissions. No confirmation email arrived for the March submission, so expect to verify by reading marketplace.json directly.

Corrections

Two premises above were wrong. Recorded so nobody re-derives them.

A tracking ref is not on offer. The docs state approved plugins "are pinned to a specific commit
SHA … and CI bumps the pin automatically as you push new commits to your repository". Of 2298
entries in the community catalog, 1892 carry a bare sha; the 402 with a ref are nearly all
git-subdir sources and carry a sha alongside it anyway. The sha pin is the design. Our actual
defect is that the automatic bump has not fired since 2026-03-16 — so the ask is "re-arm the bump",
not "give us a ref".

The submission URL moved, as covered under Action.

[sgraczyk]

Resubmitted 2026-08-04 through the Console form (platform.claude.com/plugins/submit), against main at 2597582.

Submitted values: name spec-first (same as the existing entry, so this should update it rather than create a second one), repo https://github.com/bitcraft-apps/spec-first, no subdirectory path, homepage the repo, MIT, platform Claude Code only, description the host-neutral text from #299.

The form has no free-text notes field, so the "pin is stuck at c56860e, please re-arm the auto-bump" message had nowhere to go. A fresh submission against current main should re-pin on its own. If the catalog still reads c56860e after a few nightly syncs, that needs chasing through another channel.

Verify with:

gh api -H "Accept: application/vnd.github.raw" \
  repos/anthropics/claude-plugins-community/contents/.claude-plugin/marketplace.json \
  | python3 -c "import json,sys; [print(json.dumps(p,indent=2)) for p in json.load(sys.stdin)['plugins'] if p['name']=='spec-first']"