spec-driven

Name: spec-driven
Availability: InStock
Author: seeker71

Implement features strictly from provided specification files.

3|Updated Feb 12, 2026

Search Tags:#developer tools #spec-driven #feature development #code generation #implementation #specification adherence

Ready to run

npx skills add https://github.com/seeker71/Coherence-Network --skill spec-driven-seeker71

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: spec-driven
Source: https://github.com/seeker71/Coherence-Network/tree/main/.cursor/skills/spec-driven
Command: npx skills add https://github.com/seeker71/Coherence-Network --skill spec-driven-seeker71

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures that new features and modifications are implemented precisely according to predefined specifications, preventing scope creep and maintaining adherence to design requirements.

Core Features & Use Cases

Strict Adherence to Specs: Implements features solely based on the content of specification files.
Targeted File Modification: Modifies only the files explicitly listed within a given spec.
Use Case: When tasked with adding a new user authentication flow, this Skill will ensure only the specified backend API endpoints, frontend components, and database schemas are altered, as detailed in the specs/ directory.

Quick Start

Implement the feature described in the spec file specs/001-user-profile-update.md.

Frequently Asked Questions about spec-driven

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

FAQPage Schema

How do I implement features strictly from a specification file?▼

To implement features strictly from a specification file, you need a process that reads the spec first and modifies only the designated files listed in the "Files to Create/Modify" section to ensure adherence to defined requirements.

What is the best way to prevent scope creep during feature development?▼

The best way to prevent scope creep during feature development is by implementing features solely based on the content of predefined specification files, ensuring only explicitly listed files are modified.

Can I limit code generation to only modify specific files defined in specs?▼

Yes, you can limit code generation to specific files by strictly following the "Files to Create/Modify" section within your specification, ensuring targeted file modification and preventing unauthorized changes.

Why should I use a spec-driven approach for adding new features?▼

You should use a spec-driven approach for adding new features to ensure new modifications are implemented precisely according to predefined specifications, maintaining strict adherence to design requirements and preventing scope creep.

Does spec-driven development work with existing specification documents?▼

Yes, spec-driven development works with existing specification documents by reading the provided spec files first and implementing the exact feature requirements, such as backend API endpoints and database schemas, detailed within them.