feat: add /speckit-delta — constitution-driven vision-gap analysis#2947
Open
jzhao401 wants to merge 1 commit into
Open
feat: add /speckit-delta — constitution-driven vision-gap analysis#2947jzhao401 wants to merge 1 commit into
jzhao401 wants to merge 1 commit into
Conversation
Closes the loop between a project's constitution and its feature pipeline. /speckit-delta reads the constitution's Vision & Direction section (North Star, Target Users & Value, Long-Term Objectives, Non-Goals), inspects the current repo state (code + specs), and recommends the next feature with a handoff into /speckit-specify. Included: - templates/commands/delta.md — the command (registers across integrations) - templates/constitution-template.md — adds the Vision & Direction section the command depends on - templates/plan-template.md — adds a Vision Alignment Check gate so plans are checked against the Vision, not just the principles - templates/commands/constitution.md — guidance for populating Vision (infer from README/docs when absent; TODO(VISION) markers, never bare placeholders) - one-line registrations (SKILL_DESCRIPTIONS, _FALLBACK_CORE_COMMAND_NAMES, claude ARGUMENT_HINTS) + tests/test_delta_and_vision.py + expected-file inventory updates All additions are backward-compatible: existing projects are unaffected until they regenerate their constitution. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What this adds
Spec Kit's loop today covers the life of a single feature — specify → clarify → plan → tasks → implement. The decision which feature to build next lives outside the toolkit. This PR closes that loop with a new core command:
/speckit-deltareads the constitution's Vision & Direction section, inspects the current repo state (code + merged specs), computes the gap between the two, and recommends the next feature — with a handoff straight into/speckit-specify.Concretely:
templates/commands/delta.md— the command template (200 lines; registers across integrations like every core command).templates/constitution-template.md— adds a Vision & Direction section (North Star, Target Users & Value, Long-Term Objectives, Non-Goals). Long-Term Objectives are required to be observable — phrased so progress can be assessed by inspecting repo state — which is what makes the gap computation meaningful.templates/plan-template.md— adds a Vision Alignment Check gate next to the existing Constitution Check, so each plan is validated against where the project is going, not only against its principles.templates/commands/constitution.md— instructs the constitution command to populate Vision (inferring from README/docs when user input is silent;TODO(VISION)markers instead of bare placeholders).SKILL_DESCRIPTIONS,_FALLBACK_CORE_COMMAND_NAMES, claudeARGUMENT_HINTS) plustests/test_delta_and_vision.py(14 tests) and expected-file inventory updates in the integration suites.Why in core rather than a preset
The command is fully generic — it contains no org-specific content and works for any project whose constitution states a vision. We've been running it in production across our repos (currently distributed as a preset command) and the loop-closing step has proven to be the part of spec-driven development the core pipeline doesn't yet cover. Upstreaming makes it available at bare
specify init.Backward compatibility
Purely additive. Existing projects see no change until they regenerate their constitution; projects without a Vision section get inference +
TODO(VISION)guidance rather than failures.Testing
tests/test_delta_and_vision.py(14 new tests) plus the full touched suites — extensions, CLI, claude/copilot/generic and base integration suites — pass locally on top of currentmain(485 tests across the touched files).