implement-specs
implement specs
What it does
- 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
- PRODUCT.md as the source of truth for user-facing behavior
- TECH.md as the source of truth for architecture, sequencing, and implementation shape
- PROJECTLOG.md to track checkpoints, explored paths, partial findings, and current implementation state
- DECISIONS.md to capture concrete product and technical decisions made during the PRD and tech design process
Requirements & configuration
Configuration: PRODUCTTECHPROJECT_LOGDECISIONS
Derived from the skill's own SKILL.md documentation · extracted 2026-07-23
implement-specs FAQ
What does the implement-specs skill do?
Implement an approved feature from PRODUCT.md and TECH.md, keeping specs and code aligned in the same PR as implementation evolves. Use after the product and tech specs are approved and the next step is building the feature. confirm that PRODUCT.md exists confirm that TECH.md exists when the feature warranted one
What does implement-specs require?
Configuration keys: PRODUCT, TECH, PROJECT_LOG, DECISIONS.
How do I install implement-specs?
Run: npx -y skills add https://github.com/warpdotdev/common-skills --skill implement-specs --agent claude-code — the source lives at github.com/warpdotdev/common-skills.
Maintain implement-specs?
Let people know it's listed here — add the badge (live metrics, light/dark aware) or a plain link to your README or docs.
[](https://getagentictools.com/skills/warpdotdev-common-skills-implement-specs?ref=badge) npx agentictools info skills/warpdotdev-common-skills-implement-specs The second line is the CLI lookup for this page — handy in READMEs and docs.