Menú
Show sync status between spec, plan, and tasks — identify stale artifacts
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional 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-status |
| description | Show sync status between spec, plan, and tasks — identify stale artifacts |
| compatibility | Requires spec-kit project structure with .specify/ directory |
| metadata | {"author":"github-spec-kit","source":"refine:commands/speckit.refine.status.md"} |
Show the synchronization status between spec.md, plan.md, and tasks.md. Identifies which artifacts are stale and need propagation.
$ARGUMENTS
You MUST consider the user input before proceeding (if not empty).
.specify/ directoryLocate artifacts: Find all artifacts in the current feature directory:
spec.md — the source of truthplan.md — implementation plantasks.md — task breakdownresearch.md — research notesdata-model.md — data modelcontracts/ — interface contractsCheck each artifact: For each file that exists, determine:
**Refined**: entries (spec.md)**Propagated**: entries (plan.md, tasks.md)⚠️ **STALE** marker##-level sections in plan.md- [ ] items in tasks.mdDetermine sync status: Compare artifacts to assess synchronization:
| Condition | Status |
|---|---|
| spec.md refined after plan.md last propagated | plan.md is STALE |
| spec.md refined after tasks.md last propagated | tasks.md is STALE |
plan.md has ⚠️ **STALE** marker | plan.md is STALE |
tasks.md has ⚠️ **STALE** marker | tasks.md is STALE |
| No refinement notes and no staleness markers | All artifacts are IN SYNC |
| Artifact does not exist | MISSING |
Output status dashboard:
# Artifact Sync Status: [Feature Name]
| Artifact | Status | Last Modified | Notes |
| ------------- | ---------- | ------------- | ------------------------------------- |
| spec.md | ✅ Current | [date] | [N user stories, M requirements] |
| plan.md | ⚠️ Stale | [date] | Refined on [date], not yet propagated |
| tasks.md | ⚠️ Stale | [date] | [X total tasks, Y completed] |
| research.md | ✅ Present | [date] | — |
| data-model.md | ❌ Missing | — | — |
| contracts/ | ❌ Missing | — | — |
## Refinement History
- [DATE]: [Change description]
## Recommended Actions
1. Run `/speckit.refine.propagate` to update stale artifacts
2. Run `/speckit.refine.diff` to preview impact before propagating
Report: Output the dashboard. Do not modify any files — this command is read-only.