spec-driven-implementation

Enforces spec-first workflow for Warp features via PRODUCT.md and TECH.md files located in specs/.

Updated Apr 28, 2026

Search Tags:#workflow #spec-first #tech-spec #feature-development #product-spec #warp #specs-in-repo

Ready to run

npx skills add https://github.com/89jobrien/warpx --skill spec-driven-implementation-89jobrien

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enforces a spec-first workflow for substantial Warp features, reducing ambiguity and improving review quality.

Core Features & Use Cases

Create and maintain PRODUCT.md before implementation to describe user-facing behavior.
Create and maintain TECH.md when warranted to document architecture and tradeoffs.
Keep specs in specs/<linear-ticket-number>/PRODUCT.md and specs/<linear-ticket-number>/TECH.md to ensure traceability and reviewability.

Quick Start

Create a PRODUCT.md describing the feature and context, and when needed, a TECH.md outlining the implementation plan.

Frequently Asked Questions about spec-driven-implementation

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

FAQPage Schema

How do I enforce a spec-first workflow for major feature development?▼

To enforce a spec-first workflow, you must create formal PRODUCT.md and TECH.md files under a specs/ directory before implementation. This ensures requirements are validated and governed across product and engineering teams.

What is the purpose of keeping PRODUCT.md and TECH.md specs in the repository?▼

Keeping PRODUCT.md and TECH.md specs in the repository provides formal specification and validation for substantial features. This practice ensures traceability and improves review quality by aligning implementation with documented standards.

How do I structure spec files to ensure traceability for a feature ticket?▼

To ensure traceability, structure spec files by placing them under specs/<linear-ticket-number>/PRODUCT.md and specs/<linear-ticket-number>/TECH.md. This directory mapping directly links repository specs to their corresponding feature tickets.

When do I need to write a TECH.md file for a new feature?▼

You need to write a TECH.md file when warranted for substantial feature work. It is used to document architecture and tradeoffs alongside the user-facing behavior described in your PRODUCT.md.

How do I align implementation with documented product specifications?▼

To align implementation with documented product specifications, use the implement-specs flow. This process enforces that development strictly follows the validated standards defined in your PRODUCT.md and TECH.md files.

Does this spec-first workflow apply to minor bug fixes and small updates?▼

This spec-first workflow does not apply to minor updates. It is designed specifically for substantial feature work where ambiguity is high and formal governance across product and engineering teams is required.