Implement Specs

This takes you from approved PRODUCT.md and TECH.md specs to shipped code, all in one PR. You read the specs, implement against them, then update the specs as reality shifts during development. The idea is to keep everything in sync so reviewers see the feature that actually ships, not just the original design. It'll optionally suggest a PROJECT_LOG.md or DECISIONS.md for complex features, but mostly it's just building against specs and making sure nothing drifts. Works best when your team already lives in a specs directory structure and wants implementation changes and spec tweaks committed together instead of letting docs rot.

skills.sh installs: 28.7K
GitHub stars: 684
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add warpdotdev/common-skills --skill implement-specs --agent claude-code

Installs into .claude/skills of the current project.

Files

implement-specs

Implement an approved feature from PRODUCT.md and TECH.md.

Overview

Use this skill after the product and tech specs are approved. The goal is to build the feature described by the specs while keeping the checked-in specs and the implementation aligned as the work evolves.

Approved specs should live directly under a ticket-named directory in specs/, for example specs/APP-1234/PRODUCT.md and specs/APP-1234/TECH.md.

In many cases, the implementation should be pushed in the same PR as the product and tech specs. As the engineer iterates, changes to PRODUCT.md, TECH.md, and the code should all be pushed in that same PR so review stays anchored to the feature that will actually ship.

Prerequisites

Before using this skill:

confirm that PRODUCT.md exists
confirm that TECH.md exists when the feature warranted one
confirm that the relevant specs have been reviewed and approved enough to start implementation