القائمة
Show what changed in spec.md and predict downstream impact on plan and tasks
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Detects whether Spectatui has fallen behind upstream GitHub Spec-Kit by capturing the real `specify` CLI surface (via uvx, not by reading prose), reading spec-kit's actual upstream source — slash-command templates, document skeletons, shared scripts — for features invisible to `--help`, and comparing all of that against Spectatui's actual code. Use this whenever the user asks whether Spectatui supports something from Spec-Kit, mentions Spec-Kit/specify-cli releases or changelogs, asks what's new upstream, wants a gap analysis or integration roadmap between Spectatui and Spec-Kit, or wants to know if the CLI wrapper is out of date — even if they just say "check for spec-kit updates" or "are we behind on spec-kit" without naming this skill.
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
Generate a custom checklist for the current feature based on user requirements.
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
Create or update the project constitution from interactive or provided principle inputs, ensuring all dependent templates stay in sync.
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
| name | speckit-refine-diff |
| description | Show what changed in spec.md and predict downstream impact on plan and tasks |
| compatibility | Requires spec-kit project structure with .specify/ directory |
| metadata | {"author":"github-spec-kit","source":"refine:commands/speckit.refine.diff.md"} |
Preview the impact of spec.md changes on downstream artifacts before propagating. Use this to understand the blast radius of a refinement.
$ARGUMENTS
You MUST consider the user input before proceeding (if not empty).
.specify/ directoryLoad all artifacts: Read from the current feature directory:
spec.md (check for **Refined**: entries)plan.md (if exists)tasks.md (if exists)Extract refinement history: Parse all **Refined**: entries in spec.md to build a change log:
## Refinement History
- [DATE]: [Description of change]
- [DATE]: [Description of change]
Analyze spec changes: For each refinement, classify the impact:
| Change Type | Spec Impact | Plan Impact | Tasks Impact |
|---|---|---|---|
| New user story | New section added | New structure/complexity entry | New phase with tasks |
| Modified requirement | Updated requirement text | May affect technical context | May affect task descriptions |
| Removed requirement | Strikethrough marking | Sections to mark removed | Tasks to mark removed |
| Changed priority | Reordered user story | May affect implementation order | May reorder phases |
| New success criterion | Added to criteria list | Minimal | May need verification task |
Generate impact report: Output a structured diff report:
# Spec Refinement Impact Report
## Changes Detected
- [List each change from refinement notes]
## Downstream Impact
### plan.md
- **Status**: [Up to date | Stale | Does not exist]
- **Sections affected**: [List of plan sections that need updates]
- **Estimated changes**: [Number of sections to add/modify/remove]
### tasks.md
- **Status**: [Up to date | Stale | Does not exist]
- **Tasks affected**: [List of task IDs that need updates]
- **New tasks needed**: [Count]
- **Tasks to mark removed**: [Count]
- **Dependency changes**: [Yes/No — describe if yes]
## Consistency Check
- [ ] All spec user stories have plan sections: [Pass/Fail]
- [ ] All spec requirements have task coverage: [Pass/Fail]
- [ ] No orphaned tasks from removed requirements: [Pass/Fail]
## Recommended Action
- Run `/speckit.refine.propagate` to apply these changes
- Or run `/speckit.refine.propagate only plan` to update plan.md first
Report: Output the impact report. Do not modify any files — this command is read-only.