Conversation
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— 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 ( So I'm closing this against the repo itself, but everything you built carries straight over: publish (Drafted with AI assistance — GitHub Copilot.) |
Description
Follow-up to #4507 / #1717. Core
/speckit.clarifykeeps 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 ofspeckit.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