Skip to content

Add opt-in clarify-spec-gate wrap preset - #4515

Closed
gyanu2507 wants to merge 1 commit into
github:mainfrom
gyanu2507:preset/clarify-spec-gate
Closed

gyanu2507 wants to merge 1 commit into
github:mainfrom
gyanu2507:preset/clarify-spec-gate

Conversation

@gyanu2507

@gyanu2507 gyanu2507 commented Sep 10, 2026

Copy link
Copy Markdown
Contributor

Description

Follow-up to #4507 / #1717. Core /speckit.clarify keeps a bounded deferral. The stage-gate procedure, the >60% defer-ratio audit, and the MUST-NOT block are methodology, so they live in an opt-in wrap of speckit.clarify.

Install with specify preset add clarify-spec-gate. The wrapper uses {CORE_TEMPLATE}, so core command updates still compose.

Testing

  • uv run pytest tests/test_presets.py::TestClarifySpecGatePreset tests/contract/test_wheel_bundled_presets.py tests/test_presets.py::TestConstitutionSyncPreset

Stage-gate procedure, defer-ratio audit, and MUST-NOT belong in a
preset, not core /speckit.clarify. Teams that want that enforcement
can install clarify-spec-gate.
@gyanu2507
gyanu2507 requested a review from mnriem as a code owner September 10, 2026 17:01
@mnriem mnriem added triage-must-have Verdict: high-value, important work for Spec Kit — do first triage-nice-to-have Verdict: evidence-backed fix or greenlit feature — land after review and removed triage-must-have Verdict: high-value, important work for Spec Kit — do first labels Sep 11, 2026
@mnriem

mnriem commented Sep 14, 2026

Copy link
Copy Markdown
Collaborator

@gyanu2507— genuinely, thank you for this. You took the #1717 problem, accepted the rescope on #4507 without friction, and turned the methodology into a clean, well-built, well-tested preset. This is exactly the kind of thoughtful, responsive contribution that makes the project better, and I want to be clear the work is landing — just in the right place.

Now that I can see the preset itself, the call is about hosting, not quality: an opinionated clarify methodology belongs in the community catalog (externally hosted), not as a first-party preset bundled inside spec-kit. The bundled set (presets/catalog.jsonlean/constitution-sync) is a small, foundational, github-maintained group, and keeping methodology opinions in the community catalog is consistent with #4507 removing this from core so it isn't imposed on everyone. Per presets/PUBLISHING.md, community presets live in your own public repo and come in via the [Preset] submission issue → validated → added to catalog.community.json.

So I'm closing this against the repo itself, but everything you built carries straight over: publish clarify-spec-gate from your own repo (the README, preset.yml, and wrapped speckit.clarify.md are already done), tag a release, and open a [Preset] submission issue — I'll validate it and get it into the community catalog. The core bounded-deferral change from #4507 stays in-repo separately, so the two compose exactly as you designed. Thanks again, and I'm looking forward to the catalog submission.

(Drafted with AI assistance — GitHub Copilot.)

@mnriem mnriem closed this Sep 14, 2026
@mnriem mnriem added the triage-out-of-scope Verdict: won't land in core — invalid, duplicate, off-mission, or redirected to an extension label Sep 14, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

triage-nice-to-have Verdict: evidence-backed fix or greenlit feature — land after review triage-out-of-scope Verdict: won't land in core — invalid, duplicate, off-mission, or redirected to an extension

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants