[Extension]: Add specjudge

[JoaquinRuiz]

Extension ID

specjudge

Extension Name

SpecJudge — right-size the model before you implement

Version

0.5.4

Description

Recommends the model that fits your tasks, citing the spec fragment behind every level.

Author

Joaquín Ruiz

Repository URL

https://github.com/JoaquinRuiz/SpecJudge

Download URL

https://github.com/JoaquinRuiz/SpecJudge/releases/download/v0.5.4/spec-kit-specjudge.zip

License

MIT

Homepage (optional)

https://github.com/JoaquinRuiz/SpecJudge

Documentation URL (optional)

https://github.com/JoaquinRuiz/SpecJudge/blob/main/extensions/spec-kit/README.md

Changelog URL (optional)

https://github.com/JoaquinRuiz/SpecJudge/blob/main/extensions/spec-kit/CHANGELOG.md

Required Spec Kit Version

=0.13.0

Required Tools (optional)

- specjudge (>=0.5.0) - required

Number of Commands

1

Number of Hooks (optional)

1

Tags

cost, model-selection, local-first, ollama

Key Features

• Runs after /speckit.tasks, the one moment where the choice is both informed and free
• Cites the fragment of your own spec behind every demand level, so you can disagree with a sentence rather than a verdict
• Marks each citation as a stated requirement (MUST, FR-NNN) or a habit, derived from the text rather than asked of the model
• Runs entirely locally through Ollama; specs never leave the machine
• Writes nothing (effect: read-only) and never blocks the spec-kit flow — no judge, no Ollama or too thin a spec, and it says so in one line and gets out of the way

Testing Checklist

• Extension installs successfully via download URL
• All commands execute without errors
• Documentation is complete and accurate
• No security vulnerabilities identified
• Tested on at least one real project

Submission Requirements

• Valid extension.yml manifest included
• README.md with installation and usage instructions
• LICENSE file included
• GitHub release created with version tag
• All command files exist and are properly formatted
• Extension ID follows naming conventions (lowercase-with-hyphens)

Testing Details

Tested on:

• macOS (Apple silicon) with Spec Kit 0.15.2 and SpecJudge 0.5.4
• Linux Ubuntu 22.04 with Spec Kit 0.15.2 and SpecJudge 0.5.4
• Judge: devstral-small-2 (24B) via Ollama 0.32.6

Test project: a real Streamlit multi-project wiki feature — 20 functional
requirements, 29 tasks, an SQLite migration and a permission-resolution rewrite.

Test scenarios:

1. Installed from the release URL with specify extension add specjudge --from <url>
2. Ran /speckit.tasks; the optional after_tasks hook offered the recommendation and
   was declined once, confirming it does not run unprompted
3. Ran /speckit.specjudge.recommend directly; it produced a podium, a constraint
   table citing fragment ids from the project's own spec, and the warnings verbatim
4. Ran with SpecJudge absent and with an over-thin project: both exit non-zero, the
   command reports one line and the spec-kit flow continues

Example Usage

# Install
specify extension add specjudge --from https://github.com/JoaquinRuiz/SpecJudge/releases/download/v0.5.4/spec-kit-specjudge.zip

# It offers itself after /speckit.tasks, or run it directly
/speckit.specjudge.recommend

Proposed Catalog Entry

{
  "specjudge": {
    "name": "SpecJudge — right-size the model before you implement",
    "id": "specjudge",
    "description": "Recommends the model that fits your tasks, citing the spec fragment behind every level.",
    "author": "Joaquín Ruiz",
    "version": "0.1.2",
    "download_url": "https://github.com/JoaquinRuiz/SpecJudge/releases/download/v0.5.4/spec-kit-specjudge.zip",
    "repository": "https://github.com/JoaquinRuiz/SpecJudge",
    "homepage": "https://github.com/JoaquinRuiz/SpecJudge",
    "documentation": "https://github.com/JoaquinRuiz/SpecJudge/blob/main/extensions/spec-kit/README.md",
    "changelog": "https://github.com/JoaquinRuiz/SpecJudge/blob/main/extensions/spec-kit/CHANGELOG.md",
    "license": "MIT",
    "category": "process",
    "effect": "read-only",
    "requires": {
      "speckit_version": ">=0.13.0",
      "tools": [{ "name": "specjudge", "version": ">=0.5.0", "required": true }]
    },
    "provides": { "commands": 1, "hooks": 1 },
    "tags": ["cost", "model-selection", "local-first", "ollama"],
    "verified": false,
    "downloads": 0,
    "stars": 0,
    "created_at": "2026-08-12T00:00:00Z",
    "updated_at": "2026-08-12T00:00:00Z"
  }
}

Additional Context

No response

[github-actions]

cc @github/spec-kit-maintainers — new catalog submission for review.

[github-actions]

Validation Results

Thank you for submitting the SpecJudge extension! I ran the automated validation checks and found 1 issue that needs to be fixed before this submission can be merged.

---

❌ Failed Checks

Version / Download URL mismatch

The Version field says 0.1.2, but the Download URL points to v0.5.3:

Download URL: https://github.com/JoaquinRuiz/SpecJudge/releases/download/v0.5.3/spec-kit-specjudge.zip

Additionally, release v0.1.2 does not exist in your repository — the available releases near that range are v0.1.1, v0.1.3, and v0.1.4.

How to fix: Update the Version field to match the download URL — it should be 0.5.3 (no v prefix, following semver X.Y.Z format). The proposed catalog entry's "version" field also needs to be corrected to "0.5.3".

---

✅ Passed Checks

• Extension ID specjudge is valid (lowercase, hyphens only)
• Repository is publicly accessible at https://github.com/JoaquinRuiz/SpecJudge
• extension.yml found at extensions/spec-kit/extension.yml ✓
• README.md found at extensions/spec-kit/README.md ✓
• LICENSE file present ✓
• GitHub release v0.5.3 exists ✓
• Download URL format is valid ✓
• All submission checklist items are checked ✓

---

Please edit the issue and correct the Version field to 0.5.3 and the "version" field in the Proposed Catalog Entry to "0.5.3". Once the fix is submitted, re-apply the extension-submission label to re-trigger validation.

Posted on behalf of @mnriem by GitHub Copilot (model: claude-sonnet-4.6)

Generated by 🧩 Add Community Extension from Issue Submission for issue #4068 · 85.6 AIC · ⌖ 12.2 AIC · ⊞ 35.3K · ◷

[mnriem]

@JoaquinRuiz Please address Copilot feedback

[JoaquinRuiz]

Thanks for the validation run — the mismatch was real, and I've fixed it at the source rather than in the form.

The extension used to carry its own version (0.1.2) while living in the SpecJudge repository, which is what produced a 0.1.2 declared against a v0.5.3 tag. It is now versioned in lockstep with the tool, so the manifest, the release tag and this submission all say the same thing.

Updated in the issue above:

• Version: 0.5.4
• Download URL: https://github.com/JoaquinRuiz/SpecJudge/releases/download/v0.5.4/spec-kit-specjudge.zip
• Same two changes in the proposed catalog entry.

Verified after publishing: the asset at that URL unzips with extension.yml at its root declaring version: "0.5.4", matching the tag. The archive attached to v0.5.3 is left exactly as it was published rather than rewritten in place, since it already had downloads.

One correction to the validation message, in case it helps the checker: v0.1.2 does exist in the repository — it is a SpecJudge release from July, from before the extension existed. The tags in that range (v0.1.1 … v0.1.4) are the tool's early history, not extension releases, which is exactly the ambiguity this change removes.

I can't apply labels on this repository — could someone re-apply extension-submission to re-trigger validation? Happy to make further changes if anything else comes up.