pradeepmouli/speckit-refine-status
.claude/skills/speckit-refine-status/SKILL.md
Show sync status between spec, plan, and tasks — identify stale artifacts
$ install --global
skillsauthnpx skillsauth add pradeepmouli/lspeasy speckit-refine-statusInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 16, 2026, 4:51 AM5.7s1 file scanned
SKILL.md
- 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
- author:
- github-spec-kit
- source:
- refine:commands/speckit.refine.status.md
Artifact Sync Status
Show the synchronization status between spec.md, plan.md, and tasks.md. Identifies which artifacts are stale and need propagation.
User Input
$ARGUMENTS
You MUST consider the user input before proceeding (if not empty).
Prerequisites
- Verify a spec-kit project exists by checking for
.specify/directory - Locate the current feature's spec directory
Outline
-
Locate 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 contracts
-
Check each artifact: For each file that exists, determine:
- Last modified: File modification timestamp
- Has refinement notes: Check for
**Refined**:entries (spec.md) - Has propagation notes: Check for
**Propagated**:entries (plan.md, tasks.md) - Has staleness warning: Check for
⚠️ **STALE**marker - Spec user story count: Number of user stories in spec.md
- Plan section count: Number of
##-level sections in plan.md - Task count: Number of
- [ ]items in tasks.md
-
Determine 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.
Rules
- Read-only — this command never modifies any files
- Always show all artifacts — include missing ones so user knows what to create
- Use clear status indicators — ✅ for current, ⚠️ for stale, ❌ for missing
Related Skills
pradeepmouli/lsp-refactor
tools
VerifiedTrustedCommunity
Use for ANY rename, file-move, or move-symbol refactor — especially rename-heavy work across multiple files. Claude Code's built-in LSP tool is READ-ONLY (find references, but no rename / file-move / move-symbol). Hand-editing those refactors silently misses re-exports, aliased imports, type-only imports, and {@link} doc references. This skill drives a real language server via the `lspeasy` CLI to apply a correct WorkspaceEdit that catches every reference. Trigger when the user asks to rename a function/class/variable/type project-wide, move a file and fix its importers, or pull a symbol out into another module.
2SKILL.mdUpdated Jun 3, 2026
pradeepmouli/lspeasy-core
tools
VerifiedTrustedCommunity
Documentation site for lspeasy Use when: You are building a browser-based LSP client, a WebSocket-backed language....
2SKILL.mdUpdated Apr 17, 2026
pradeepmouli/lspeasy-client
tools
VerifiedTrustedCommunity
Documentation site for lspeasy Use when: You are implementing a custom client layer and need the same validation....
2SKILL.mdUpdated Apr 17, 2026
pradeepmouli/lspeasy
tools
VerifiedTrustedCommunity
Use when working with lspeasy (client, core, server). Covers: lsp, language-server-protocol, lsp-client, language-client, jsonrpc, transport, lsp-server, language-server.
1SKILL.mdUpdated Apr 25, 2026