skills.rest
Uguryldz
UguryldzCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

spec-driven-development

Keeps implementation code synchronized with markdown specs stored in .claude/specs/.

Updated Apr 9, 2026
Search Tags:#specification#drift detection#n8n#spec-driven development#documentation sync#code verification#markdown specs
One-click install
npx skills add https://github.com/Uguryldz/n8nclean --skill spec-driven-development-uguryldz
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec-driven-development
Source: https://github.com/Uguryldz/n8nclean/tree/main/.claude/plugins/n8n/skills/spec-driven-development
Command: npx skills add https://github.com/Uguryldz/n8nclean --skill spec-driven-development-uguryldz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Implementation code and specification documents frequently drift apart during development, causing outdated API contracts, stale architecture notes, and untracked TODO items. This Skill enforces a workflow where specs in .claude/specs/ remain the source of truth and are updated whenever code diverges. ## Core Features & Use Cases - Spec-First Workflow: Locates and reads relevant specs in .claude/specs/ before writing code, and prompts creating one for non-trivial features. - Drift Detection and Repair: Verifies API endpoints, config variables, module structure, and type definitions against the spec, then updates the spec or code to resolve divergence. - Progress Tracking: Maintains TODO checkboxes in specs, ticking completed items and annotating deliberately skipped decisions. - Use Case: After implementing a new backend module, ask for a self-review against the spec to receive a structured report of aligned items, drift to fix, and gaps remaining as future work. ## Quick Start Ask the assistant to verify the current implementation against the spec in .claude/specs/ and update any drift it finds.

Frequently Asked Questions about spec-driven-development

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I keep implementation code in sync with a spec document?▼

Read the spec before coding, reference its decisions during implementation, and update the spec immediately whenever the code diverges. After finishing, re-read both side by side and fix any drift in endpoints, config, or structure.

How to verify implementation against a specification?▼

Run a verification pass comparing each spec section against the code: API endpoints versus controllers, env vars versus config classes, file tree versus module structure, and types versus @n8n/api-types. Report aligned items, drift, and gaps separately.

Where should spec files be stored in a project?▼

Specs live in the .claude/specs/ directory, with one or more markdown files per feature. Files can be split by concern, such as separate backend and frontend specs, without enforcing a rigid naming scheme.

What should I do when no spec exists for a new feature?▼

If the task is non-trivial, such as a new module, API, or architectural change, ask the user whether to create a spec first before writing code. Trivial changes can proceed without one.

How are completed and skipped spec items tracked?▼

Completed TODO checkboxes are ticked from - [ ] to - [x]. Deliberately skipped or replaced items are struck through and annotated with a brief reason explaining the replacement decision.

Related Skills

Explore More Software Engineering Skills→
avibebuilderavibebuilder
113

give-plan

Create a reviewable implementation plan from repository files before coding.

Official
Intermediate
erclxerclx
2

claude-address-review

Apply code fixes and update documentation for GitHub pull request review findings.

Community
Advanced
dogganidhaldogganidhal
43

run-tests

Run type checks and test suites with green/red status reports.

Community
Intermediate
mei28mei28
3

doc-gen

Generate OpenAPI specs and Markdown API references from codebases.

Community
Advanced