spec-core

Guide spec-driven development workflows with structured research, design, and verification stages.

9|Updated May 27, 2026

Search Tags:#planning #documentation #development workflow #software development #spec-driven development

Ready to run

npx skills add https://github.com/kamioj/spec-workflow --skill spec-core

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: spec-core
Source: https://github.com/kamioj/spec-workflow/tree/main/codex/skills/spec-core
Command: npx skills add https://github.com/kamioj/spec-workflow --skill spec-core

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a comprehensive overview and guidance for spec-driven development, breaking down the workflow into manageable stages and ensuring disciplined planning before execution.

Core Features & Use Cases

Workflow Overview: Summarizes the spec-driven development workflow, including research, design, proposal, implementation, verification, and archiving.
Command Index: Lists all available commands with their responsibilities, including entry, gather, design & propose, execute & verify, and wrap up.
Artifact Map: Describes the organization of files and directories involved in the workflow, including knowledge, changes, and archive directories.
Phase Responsibility Matrix: Defines the role of each artifact in the workflow, ensuring clear accountability and reducing document bloat.
Shared Principles: Outlines the core principles guiding the spec-driven development process, including HARD GATE flow, interrogation rules, stuck protection, anti-cheating measures, and halt on infeasible tasks.
Hook Mechanism: Explains the use of hooks for enforcing constraints and ensuring the workflow is followed correctly.
References Loading Strategy: Describes the strategy for loading reference materials on demand, avoiding unnecessary overhead.
Interaction with the Global Protocol: Defines how the Skill interacts with the global protocol, including language, subagent delegation, and concurrency.

Quick Start

Run the $spec-workflow command to start the full spec-driven development flow.

Frequently Asked Questions about spec-core

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

FAQPage Schema

What is spec-driven development and how does it structure software workflows?▼

Spec-driven development organizes software projects into research, design, proposal, implementation, verification, and archiving stages, enforcing structured planning and documentation before execution to manage complex changes.

How do I start a spec-driven development workflow for a large software change?▼

Start a spec-driven development workflow by running the `$spec-workflow` command, which guides you sequentially through research, design, proposal, implementation, verification, and archiving phases.

Can I use spec-driven development for projects involving multiple stakeholders?▼

Yes, spec-driven development suits large changes involving multiple stakeholders and stages, using a phase responsibility matrix to define artifact roles, ensure accountability, and reduce document bloat.

What file formats and tools are used to manage spec-driven development artifacts?▼

Spec-driven development uses Markdown, YAML, and command-line interfaces to organize artifacts across knowledge, changes, and archive directories, ensuring structured workflow control and document accountability.

How does spec-driven development handle infeasible tasks or workflow violations?▼

Spec-driven development enforces shared principles including a HARD GATE flow, stuck protection, anti-cheating measures, and hook mechanisms to halt the workflow automatically upon encountering infeasible tasks or constraint violations.