spec-driven-development

Name: spec-driven-development
Availability: InStock
Author: Haydern

Draft structured specifications before coding to clarify requirements.

Updated Jun 11, 2026

Search Tags:#workflow #planning #documentation #specification #requirements #software-engineering #gated

Ready to run

npx skills add https://github.com/HaydernCenterpoint/Codex-Skills --skill spec-driven-development-hayderncenterpoint

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: spec-driven-development
Source: https://github.com/HaydernCenterpoint/Codex-Skills/tree/main/.grok/skills/spec-driven-development
Command: npx skills add https://github.com/HaydernCenterpoint/Codex-Skills --skill spec-driven-development-hayderncenterpoint

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writes a structured specification before coding to make requirements explicit, serving as the shared source of truth for what we're building, why, and how success is measured.

Core Features & Use Cases

Spec Template: A canonical template to capture objective, tech stack, commands, project structure, code style, testing strategy, boundaries, success criteria, and open questions.
Gated Workflow: SPECIFY → PLAN → TASKS → IMPLEMENT with human reviews at each stage to ensure alignment.
Verification Checklist: A built-in checklist to ensure spec completeness and approval before implementation.
Grok-Specific Guidance: Guidance on surfacing assumptions and next steps after drafting the spec.

Quick Start

Draft a complete spec for a new feature given ambiguous requirements.

Frequently Asked Questions about spec-driven-development

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

FAQPage Schema

What is a structured specification and why do I need one before coding?▼

A structured specification makes requirements explicit before coding, serving as a shared source of truth for what you are building, why, and how success is measured. It prevents ambiguity and misalignment across teams.

How do I draft a specification for a new feature with ambiguous requirements?▼

Drafting a specification for ambiguous requirements involves applying a formal template to capture objectives, tech stack, and boundaries, then following a gated SPECIFY, PLAN, TASKS, and IMPLEMENT workflow with human reviews.

What should be included in a software specification template?▼

A software specification template should include the objective, tech stack, commands, project structure, code style, testing strategy, boundaries, success criteria, and open questions to ensure complete clarity before implementation.

When should I use a gated planning process for software engineering?▼

Use a gated planning process for new projects, feature additions, or major changes where requirements are unclear and cross-team collaboration is needed to enforce alignment through explicit verification checklists.

Does spec-driven development work for major changes in existing projects?▼

Spec-driven development works for major changes in existing projects by enforcing a formal spec template and verification checklist to clarify requirements and establish shared success criteria before implementation.