spec-driven-implementation

Enforce a spec-first workflow requiring PRODUCT.md and TECH.md before implementation.

Updated Apr 30, 2026

Search Tags:#workflow #documentation #spec #spec-first #tech-spec #feature-development #product-spec

Ready to run

npx skills add https://github.com/lalaABC/waprcn --skill spec-driven-implementation-lalaabc

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: spec-driven-implementation
Source: https://github.com/lalaABC/waprcn/tree/main/.agents/skills/spec-driven-implementation
Command: npx skills add https://github.com/lalaABC/waprcn --skill spec-driven-implementation-lalaabc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams establish a spec-first workflow for substantial features to reduce ambiguity and improve cross-functional alignment before implementation.

Core Features & Use Cases

Product and tech specs live under specs/<ticket>/PRODUCT.md and specs/<ticket>/TECH.md to keep decisions versioned.
Guides creation of Linear issues and tracks changes across product and engineering.
Encourages continuous spec alignment during implementation.

Quick Start

Create an initial PRODUCT.md under specs/NEW-TICKET/PRODUCT.md and a corresponding TECH.md, then update both as implementation evolves.

Frequently Asked Questions about spec-driven-implementation

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

FAQPage Schema

How do I manage feature development specs for cross-functional projects?▼

Align product and engineering teams by enforcing a spec-first workflow that requires product and technical specifications before implementation. Specs are stored under specs/<ticket>/PRODUCT.md and TECH.md to keep decisions versioned and coordinated across functions.

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

A spec-first workflow requires writing and updating product and technical specifications before implementation begins. It aligns specs with implementation plans, code reviews, and version control to reduce ambiguity and improve cross-functional coordination.

How do I structure product and tech specs to align with implementation plans?▼

Structure product and tech specs by creating PRODUCT.md and TECH.md files under specs/<ticket>/ for each feature. Update both documents continuously as implementation evolves to maintain alignment with development plans and version control.

When do I need to write and update product and technical specifications?▼

Write and update product and technical specifications when organizing substantial features and cross-functional initiatives requiring product and engineering coordination. Create initial specs before implementation and continuously align them as the work evolves.

Can I use a spec-first approach for small feature tickets?▼

A spec-first approach is designed for large features and cross-functional initiatives where product and engineering coordination is essential. Small feature tickets do not require the enforced product and tech spec workflow.