skills.rest
terzigolu
terzigoluCOMMUNITY
Explore all skills by this author →
GitHub

spec-driven-implementation

Plan feature work by writing and maintaining PRODUCT.md and TECH.md specs.

37|1|Updated Apr 28, 2026
Search Tags:#documentation#linear#project-planning#spec-first#product-specs#tech-specs#specs-management
One-click install
npx skills add https://github.com/terzigolu/warp-lite --skill spec-driven-implementation-terzigolu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec-driven-implementation
Source: https://github.com/terzigolu/warp-lite/tree/main/.agents/skills/spec-driven-implementation
Command: npx skills add https://github.com/terzigolu/warp-lite --skill spec-driven-implementation-terzigolu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Drive a spec-first workflow for substantial features by writing PRODUCT.md before implementation, writing TECH.md when warranted, and keeping both specs updated as implementation evolves. Use when starting a significant feature, planning agent-driven implementation, or when the user wants product and tech specs checked into source control.

Core Features & Use Cases

  • Guides teams to adopt a spec-first workflow by placing PRODUCT.md and TECH.md under specs/ and ensuring specs stay versioned and up-to-date.
  • Encourages creating Linear issues before writing specs and using MCP tools to manage tickets and labels.
  • Improves clarity, review efficiency, and alignment for large features; specs live with code and evolve with implementation.

Quick Start

Create a PRODUCT.md describing the desired user-facing behavior under specs/<ticket>/PRODUCT.md, optionally add TECH.md, and commit both to source control before implementation.

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 product and tech specs within my codebase?▼

Manage product and tech specs by storing them as versioned PRODUCT.md and TECH.md files under specs/<ticket>/ directories, keeping them updated alongside your code as implementation evolves.

When should I use a spec-first workflow for feature development?▼

Use a spec-first workflow for projects with cross-cutting architecture, high risk, or unclear requirements to improve clarity, reviewability, and alignment with business goals before coding begins.

How do I write product specs before starting feature implementation?▼

Write product specs by creating a PRODUCT.md file describing desired user-facing behavior under specs/<ticket>/, optionally adding a TECH.md, and committing both to source control before implementation begins.

Can I integrate Linear issues with my specs management process?▼

Yes, the specs management workflow encourages creating Linear issues before writing specs and using MCP tools to manage tickets and labels, ensuring traceability between documentation and project planning.

Does a spec-first approach work for agent-driven development?▼

Yes, spec-first workflows are ideal for planning agent-driven implementation, providing structured product and technical specifications that guide coding agents through substantial feature work.

What are the limitations of keeping specs in source control?▼

Keeping specs in source control requires manually updating PRODUCT.md and TECH.md as implementation evolves, adding overhead for small features and demanding strict team discipline to stay relevant.

Related Skills

Explore More Product & Management Skills→
semanticpixelsemanticpixel

scaffold-sub-issues

Convert PLAN-*.md files into Linear parent issues and ordered sub-issues with dependency relations.

Community
Advanced
lalaABClalaABC

implement-specs

Align code changes with approved PRODUCT.md and TECH.md specs.

Community
Advanced
Luney-IndustriesLuney-Industries
4

ship-task

Merge GitHub pull requests and transition Linear or Jira tickets to Done.

Official
Advanced
pecorapromotionsllc-cellpecorapromotionsllc-cell

spec-driven-development

Define a formal spec and adopt a four-phase Specify, Plan, Tasks, Implement workflow.

Community
Advanced