spec-driven-implementation

Creates product and tech specs before implementing large features.

144|16|Updated May 3, 2026

Search Tags:#feature development #tech spec #spec-first #codebase integration #product spec

Ready to run

npx skills add https://github.com/Terry-Mao/AICodingFlow --skill spec-driven-implementation-terry-mao

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: spec-driven-implementation
Source: https://github.com/Terry-Mao/AICodingFlow/tree/main/.agents/skills/spec-driven-implementation
Command: npx skills add https://github.com/Terry-Mao/AICodingFlow --skill spec-driven-implementation-terry-mao

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill ensures a clear and documented process for developing substantial features, reducing ambiguity and improving review quality by writing product and tech specs upfront.

Core Features & Use Cases

Spec-First Workflow: Encourage the creation of detailed product and tech specs for large features before implementation.
Codebase Integration: Integrates with existing repositories, allowing specs to be versioned and reviewed alongside code.
Use Case: Before implementing a new feature, create a product spec to define the desired behavior and a tech spec to outline the implementation plan.

Quick Start

Run the spec-driven-implementation skill to begin the spec-first workflow for your new feature.

Frequently Asked Questions about spec-driven-implementation

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

FAQPage Schema

What is a spec-first workflow for feature development?▼

A spec-first workflow requires creating detailed product and tech specs to define desired behavior and implementation plans before coding. This approach reduces ambiguity and improves review quality for large or complex features.

How do I write product and tech specs before implementing a new feature?▼

To write product and tech specs for a new feature, define the desired behavior in a product spec and outline the implementation plan in a tech spec. Running the spec-driven workflow initiates this documented development process.

Can I version my feature specifications alongside my existing codebase?▼

Yes, you can version your feature specifications alongside your existing codebase. This codebase integration allows specs to be reviewed with the code, ensuring clear requirements are maintained throughout the development process.

When do I need to use a spec-first workflow for software features?▼

You need a spec-first workflow when developing substantial software features where clear requirements and a documented development process are essential. It is typically applied to large or complex features to reduce ambiguity.

Does a spec-first approach work for small codebase integrations?▼

A spec-first approach is designed for substantial software features where clear requirements are essential. It may introduce unnecessary overhead for small codebase integrations that do not require a heavily documented development process.