skills.rest
jameswp0
jameswp0COMMUNITY
Explore all skills by this author →
GitHub

spec-driven-development

Verify and update spec files across codebases under specs/ or app_spec/.

Updated Aug 23, 2026
Search Tags:#documentation#spec-driven#test-generation#specs#health-check#todo-analysis
One-click install
npx skills add https://github.com/jameswp0/spec-driven-development --skill spec-driven-development-jameswp0
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec-driven-development
Source: https://github.com/jameswp0/spec-driven-development/tree/main/skills/spec-driven-development
Command: npx skills add https://github.com/jameswp0/spec-driven-development --skill spec-driven-development-jameswp0

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Projects drift between intent, implementation, and tests because specs are missing, outdated, or inconsistent, causing unclear requirements, brittle tests, and AI-assisted work that hallucinates or invents behavior. This Skill enforces reading reality before writing, detects mismatches between specs and code, and provides automated fixes and guardrails so documentation, implementation, and tests stay aligned.

Core Features & Use Cases

  • Spec Health Check: glob for spec files, verify referenced file paths, extract actual function signatures, replace placeholder paths, fill empty table cells, and ensure minimum error/edge cases with auto-fixes for trivial issues.
  • Test Health Check & Generation: generate tests from UserStory/REQ mappings, validate @spec references, detect LLM anti-patterns (circular mocks, happy-path bias, over-mocking), and auto-fix broken imports.
  • Workflows & Templates: bootstrap specs for existing codebases, analyze and prioritize todos, and provide templates for overview/feature specs and implementation documentation.
  • Use Cases: bootstrapping a repo with no specs, running a repo-wide spec health check after implementation, generating tests from requirements, and surfacing actionable todos or bugs from specs.

Quick Start

Run a spec health check on the repository (look under specs/ or app_spec/) to verify paths, extract real signatures, fill placeholders, enforce ≥3 error and edge cases, validate test @spec links, and auto-fix trivial issues.

Frequently Asked Questions about spec-driven-development

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

FAQPage Schema
What is spec-driven development and how does it keep documentation and tests aligned?▼

Spec-driven development makes specification files the single source of truth, checking and updating specs across a codebase to detect mismatches between intent, implementation, and tests so documentation and behavior stay aligned.

How do I run a spec health check on my existing codebase?▼

Run a spec health check by globbing for spec files under specs/ or app_spec/, verifying referenced file paths, extracting actual function signatures, replacing placeholder paths, and enforcing at least three error and edge cases.

Can I generate tests automatically from requirements and spec files?▼

Yes, you can generate tests from UserStory and REQ mappings by validating @spec test references, detecting LLM anti-patterns like circular mocks or happy-path bias, and auto-fixing broken imports.

Does spec-driven development work for bootstrapping a repository with no existing specs?▼

Yes, it supports bootstrapping specs for existing codebases by providing templates for overview and feature specs, analyzing and prioritizing todos, and generating implementation documentation.

How do I fix outdated spec files that reference incorrect file paths?▼

Perform a spec health check to verify file existence, extract actual code signatures, replace placeholder paths, fill empty table cells, and auto-fix trivial path mismatches during the validation process.

What are the limitations of enforcing spec-driven development across a project?▼

It requires spec files to be located under specs/ or app_spec/ directories, and while it auto-fixes trivial issues, complex mismatches between specs and code require manual intervention to update requirements or implementation.

Related Skills

Explore More Software Engineering Skills→
pradeepmoulipradeepmouli
2

speckit-baseline

Generate baseline-spec.md and current-state.md from repository analysis.

Community
Advanced
Patasse97Patasse97

spec-driven-workflow

Generate RFC-compliant spec templates and extract executable tests from acceptance criteria.

Community
Advanced
baekenoughbaekenough
34

fix-refs

Identify and fix broken agent references and symlinks via mgr-supplier audits.

Community
Intermediate
open-circleopen-circle
1.1k

repo-website-api-review

Review API documentation routes against source code for accuracy.

Official
Intermediate