implement-specs

Name: implement-specs
Availability: InStock
Author: Warp

Plan and execute feature implementations while keeping specs aligned with code changes.

292|39|Updated Mar 17, 2026

Search Tags:#workflow #spec-driven #implementation #pull-request #tech-spec #product-spec #code-alignment

Ready to run

npx skills add https://github.com/warpdotdev/oz-for-oss --skill implement-specs-warpdotdev

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: implement-specs
Source: https://github.com/warpdotdev/oz-for-oss/tree/main/.agents/skills/implement-specs
Command: npx skills add https://github.com/warpdotdev/oz-for-oss --skill implement-specs-warpdotdev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Implementing features often drifts from approved product and tech specs, leading to wasted cycles and misaligned changes. This skill provides a disciplined, spec-driven workflow to keep specs and code in sync throughout the implementation lifecycle. It ensures that specs, implementation, and reviews evolve together in a single coherent change.

Core Features & Use Cases

Spec-driven implementation workflow that aligns product and tech specs with code changes.
Keeps specs up to date as the feature evolves, ensuring review clarity and traceability.
Use case: start a feature by updating both specs and code in the same PR to ship a verified implementation.

Quick Start

Create a feature branch that implements the approved spec and updates both the product and tech specs in the same PR.

Frequently Asked Questions about implement-specs

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

FAQPage Schema

How do I keep tech specs aligned with code changes during feature implementation?▼

Spec-driven implementation workflows keep tech specs aligned with code changes by requiring both to be updated in the same pull request, ensuring review clarity and traceability. This prevents implementation drift from approved product and tech specs.

What is a spec-driven implementation workflow for shipping features?▼

A spec-driven implementation workflow is a process where approved product and tech specs dictate the code changes, requiring both specs and implementation to evolve together in a single coherent commit within the same branch or pull request.

How do I start a feature branch that implements an approved spec?▼

To start a feature branch implementing an approved spec, create a branch that executes the feature implementation while updating both the product and tech specs in the same pull request to ship a verified implementation.

Do I need approved specs to ship a feature in a spec-driven workflow?▼

Yes, spec-driven workflows require approved product and tech specs to ship features, ensuring that implementation changes are committed together with spec updates in the same pull request to maintain code alignment.

What's the best way to prevent implementation drift from product specs?▼

The best way to prevent implementation drift is using a disciplined spec-driven workflow that keeps product and tech specs up to date as the feature evolves, ensuring specs drive implementation and changes are committed together.

Why does my feature implementation drift from the approved tech spec?▼

Implementation drifts from approved tech specs when code changes evolve separately from documentation, a problem solved by committing spec updates and code changes together in the same pull request to maintain alignment.