pradeepmouli/speckit-refine-diff
.agents/skills/speckit-refine-diff/SKILL.md
Show what changed in spec.md and predict downstream impact on plan and tasks
$ install --global
skillsauthnpx skillsauth add pradeepmouli/zod-to-form speckit-refine-diffInstall 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 29, 2026, 11:38 PM10.2s1 file scanned
SKILL.md
- name:
- speckit-refine-diff
- description:
- Show what changed in spec.md and predict downstream impact on plan and
- compatibility:
- Requires spec-kit project structure with .specify/ directory
- author:
- github-spec-kit
- source:
- refine:commands/speckit.refine.diff.md
Diff Spec Changes
Preview the impact of spec.md changes on downstream artifacts before propagating. Use this to understand the blast radius of a refinement.
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
- Verify spec.md exists
Outline
-
Load 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.
Rules
- Read-only — this command never modifies any files
- Always show impact — even if no downstream artifacts exist, report what would be needed
- Be specific — list exact section names and task IDs affected, not vague summaries
Related Skills
pradeepmouli/zod-to-form
tools
VerifiedTrustedCommunity
Use when working with zod-to-form (core, react, cli, codegen, vite).
1SKILL.mdUpdated May 10, 2026
pradeepmouli/zod-to-form-vite
tools
VerifiedTrustedCommunity
Vite plugin for zod-to-form — transforms ?z2f imports into generated form components and optionally replaces <ZodForm> JSX call sites with generated components at build time Use when: You want `import SignupForm from './signup.schema?z2f'` to Just Work in a.... Also: vite, vite-plugin, zod, zod-v4, codegen, forms, form-generation, schema-driven, react-hook-form, build-plugin, jsx-transform.
1SKILL.mdUpdated Apr 20, 2026
pradeepmouli/zod-to-form-react
development
VerifiedTrustedCommunity
Runtime <ZodForm> renderer for Zod v4 schemas Use when: You need form rendering in storybook, playgrounds, or low-traffic admin UIs —.... Also: zod, zod-v4, react, forms, form-generation, react-hook-form, schema-driven, dynamic-forms, form-renderer, hookform-resolver, zod-form-renderer.
1SKILL.mdUpdated Apr 20, 2026
pradeepmouli/zod-to-form-core
development
VerifiedTrustedCommunity
Schema walker and processor registry for Zod v4 form generation Use when: You want per-field validation instead of whole-form validation. Also: zod, zod-v4, forms, form-generation, schema, schema-walker, processor-registry, react-hook-form, schema-driven, form-schema, zod-registry.
1SKILL.mdUpdated Apr 20, 2026