implement-specs

Align PRODUCT.md and TECH.md with code changes in a single PR.

Updated Apr 28, 2026
One-click install
npx skills add https://github.com/89jobrien/warpx --skill implement-specs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: implement-specs
Source: https://github.com/89jobrien/warpx/tree/main/.agents/skills/implement-specs
Command: npx skills add https://github.com/89jobrien/warpx --skill implement-specs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill coordinates the alignment of product and technical specs with implementation work, ensuring specs and code stay in sync within the same PR and reducing drift.

Core Features & Use Cases

  • Spec-driven workflow: use approved PRODUCT.md and TECH.md to drive implementation steps and keep documentation aligned.
  • PR-cohesion: ensure all specs and related code changes are included in a single pull request for traceability.
  • Quality assurance: maintain verifiable checkpoints by updating specs as implementation evolves and validating against tests.

Quick Start

Create a spec-driven feature in the repository by updating PRODUCT.md and TECH.md in the same PR as you implement the feature.

Frequently Asked Questions about implement-specs

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

FAQPage Schema
How do I keep product specs and code synchronized in a single pull request?

To keep specs and code synchronized in a single pull request, you update PRODUCT.md and TECH.md alongside the implementation changes. This ensures specifications remain the single source of truth and prevents documentation drift within the same PR workflow.

What is a spec-driven workflow for software engineering?

A spec-driven workflow uses approved specifications like PRODUCT.md and TECH.md to guide implementation steps. It treats documentation as the single source of truth, ensuring feature development is driven by specs and that code changes reflect those exact requirements.

How to align technical documentation with code changes during feature development?

You align technical documentation with code changes by enforcing a workflow where specs are updated in the same PR as the implementation. This coordinates PRODUCT.md and TECH.md updates directly with code evolution, maintaining verifiable traceability and reducing drift.

Why does specification drift happen in software engineering pull requests?

Specification drift happens when implementation code evolves independently of documentation. Without enforcing spec-driven workflows that update PRODUCT.md and TECH.md in the same PR, technical specs lose synchronization with the actual codebase over time.

When do I need to update PRODUCT.md and TECH.md files?

You need to update PRODUCT.md and TECH.md files whenever you implement feature changes in a pull request. Updating these specs during the same workflow ensures documentation stays current, applies quality assurance checkpoints, and maintains verifiable traceability.