skills.rest
terzigolu
terzigoluCOMMUNITY
Explore all skills by this author →
GitHub

implement-specs

Implement features from PRODUCT.md and TECH.md specs with synchronized code and tests.

37|1|Updated Apr 28, 2026
Search Tags:#spec-driven#implementation#software-development#pull-request#tech-spec#product-spec
One-click install
npx skills add https://github.com/terzigolu/warp-lite --skill implement-specs-terzigolu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: implement-specs
Source: https://github.com/terzigolu/warp-lite/tree/main/.agents/skills/implement-specs
Command: npx skills add https://github.com/terzigolu/warp-lite --skill implement-specs-terzigolu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill guides teams to implement a feature by aligning product and technical specifications with code in the same PR, ensuring traceability and aligned delivery.

Core Features & Use Cases

  • Read approved specs first: Product and Tech as truth, and ensure understanding of expected behavior, constraints, risks, and validation plan before coding.
  • Offer optional implementation aids for large features: PROJECT_LOG.md and DECISIONS.md to capture checkpoints and concrete decisions.
  • Plan and implement against the specs: Break work into concrete steps, implement against approved specs, keep behavior aligned with PRODUCT.md and architecture aligned with TECH.md, and add tests and verification artifacts.
  • Update specs as the implementation evolves: Update PRODUCT.md and TECH.md when changes occur; keep updates in the same PR.
  • Verify against the specs: Use rust-unit-tests, integration or end-to-end tests for important user flows.
  • Best Practices: Keep specs and code synchronized throughout implementation; update decisions; maintain coherent PR narrative.

Quick Start

Review the approved PRODUCT.md and TECH.md, then implement the feature in the same PR while keeping specs and code synchronized.

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 and technical specs synchronized with code in the same pull request?▼

Spec-driven implementation keeps specifications synchronized by treating PRODUCT.md and TECH.md as the source of truth, updating them alongside code within the same pull request to ensure traceability and aligned feature delivery.

What is the best way to plan feature development from approved technical specifications?▼

Planning feature development from technical specifications involves reading approved PRODUCT.md and TECH.md files first, breaking work into concrete steps, and implementing against the defined behavior, constraints, and architecture to maintain specification adherence.

How do I track implementation decisions and checkpoints for large feature development?▼

To track implementation decisions and checkpoints for large feature development, you can use optional PROJECT_LOG.md and DECISIONS.md files to capture concrete decisions and milestones, ensuring a coherent PR narrative throughout the workflow.

Do I need approved product specs and tech specs before starting implementation?▼

Yes, you need approved PRODUCT.md and TECH.md specifications before coding. Reading these specs first ensures you understand expected behavior, constraints, risks, and the validation plan before implementing the feature.

How do I verify implemented features against product and technical specifications?▼

To verify implemented features against product and technical specifications, you use integration or end-to-end tests for important user flows, ensuring the code behavior aligns with PRODUCT.md and the architecture matches TECH.md.

When should I update specifications during spec-driven feature implementation?▼

You should update specifications during spec-driven feature implementation whenever changes occur during development. Keeping PRODUCT.md and TECH.md updates in the same PR as code changes maintains synchronization and coherent review-ready artifacts.

Related Skills

Explore More Software Engineering Skills→
89jobrien89jobrien

implement-specs

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

Community
Advanced
goffitygoffity

pr

Run tests, build, review code, and create a pull request with issue tracking.

Community
Advanced
terzigoluterzigolu
37

write-tech-spec

Draft a TECH.md specification for a Warp feature from codebase research.

Community
Advanced
SjdjdiejdrirhdkjejSjdjdiejdrirhdkjej

task-status-sync

Synchronize tasks.md and NOTES.md via task-tracker commands.

Community
Advanced