implement-specs

Implement features from approved PRODUCT.md and TECH.md specs in a single Pull Request.

30|4|Updated May 3, 2026
One-click install
npx skills add https://github.com/OniroHuaver/openwarp --skill implement-specs-onirohuaver
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: implement-specs
Source: https://github.com/OniroHuaver/openwarp/tree/main/.agents/skills/implement-specs
Command: npx skills add https://github.com/OniroHuaver/openwarp --skill implement-specs-onirohuaver

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures that the code implementation is aligned with approved product and technical specifications throughout the development process.

Core Features & Use Cases

  • Spec Alignment: Keeps code in sync with approved PRODUCT.md and TECH.md specifications.
  • Single PR Implementation: Allows for updating specs and implementing changes in the same Pull Request.
  • Use Case: After specs are approved, use this skill to implement the feature, making sure to push any updates to the specs and code within the same PR.

Quick Start

Implement the feature defined in specs/APP-1234/PRODUCT.md and specs/APP-1234/TECH.md by pushing the code and spec updates to 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 code implementation aligned with approved product and tech specs?

To keep code implementation aligned with approved product and tech specs, you push spec updates and code changes together in a single Pull Request. This ensures user-facing behavior and implementation details stay synchronized throughout the development workflow.

What is the best way to update specifications during feature development?

The best way to update specifications during feature development is to include the spec modifications in the same Pull Request as the code implementation. This single PR approach keeps your PRODUCT.md and TECH.md files in sync with the actual feature changes.

Can I implement features from PRODUCT.md and TECH.md specifications in one PR?

Yes, you can implement features from PRODUCT.md and TECH.md specifications in one PR. The process requires you to push both the code implementation and any necessary updates to the approved specifications to the same Pull Request.

Why should spec updates and code changes be in the same Pull Request?

Spec updates and code changes should be in the same Pull Request to maintain specification alignment. Combining them ensures that any modifications to user-facing behavior or implementation details are reviewed alongside the corresponding code changes.

When do I need to sync code with approved specifications?

You need to sync code with approved specifications after the initial spec review and during feature implementation. This ensures that any deviations or refinements made during code implementation are reflected back into the specification documents.

Does this development workflow support updating approved specs during code implementation?

Yes, this development workflow supports updating approved specs during code implementation. You can modify the specifications as needed while implementing the feature, provided both the spec updates and code changes are pushed to the same Pull Request.