implement-specs

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.

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/implement-specs/SKILL.md

Quality

Content

71%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, self-contained process guide with a clear sequenced workflow and clean sectioning. Its weakness is actionability: the actual implementation and testing guidance is abstract rather than concrete and executable.

Suggestions

Add concrete, executable specifics for the implementation and verification steps — e.g., example test commands, a concrete diff/PR checklist, or a minimal template for PROJECT_LOG.md and DECISIONS.md — to lift actionability above the abstract "implement the feature" level.

Tighten the repeated "same PR" / "keep specs and code aligned" guidance so it is stated once authoritatively and referenced rather than restated across Overview, Workflow, and Best Practices.

Strengthen the step-5 verify checkpoint into an explicit feedback loop (run tests → if failing, fix and re-run → only mark complete when passing) to reach the workflow-clarity 5 anchor.

Dimension	Reasoning	Score
Conciseness	The body is lean and avoids explaining concepts Claude already knows, but the "same PR" and "keep specs/code aligned" guidance recurs across Overview, Workflow steps 3–4, and Best Practices, so it is not fully tight at the 5 anchor.	4 / 5
Actionability	Concrete artifacts and locations are named (specs/APP-1234/, PRODUCT.md, TECH.md, PROJECT_LOG.md, DECISIONS.md), but the core execution guidance — "Break the work into concrete implementation steps, then implement the feature" and "add or update tests" — stays abstract with no executable specifics.	3 / 5
Workflow Clarity	A clear 5-step sequence (read → offer aids → implement → update specs → verify) with a Prerequisites section and a verify checkpoint in step 5; the verification is light with no explicit fix→re-verify loop, so it falls short of the 5 anchor.	4 / 5
Progressive Disclosure	No bundle files exist and none are needed; the self-contained ~85-line body is well-organized into Overview, Prerequisites, Workflow, Best Practices, and Related Skills with zero nested references, satisfying the simple-skill exception.	5 / 5
	Total	16 / 20 Passed

Description

83%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A clear, third-person description that concretely states what the skill does and when to use it, with strong trigger phrasing. Its main limitation is modest overlap with sibling spec-implementation skills rather than any vagueness.

Dimension	Reasoning	Score
Specificity	Names the domain (spec-driven implementation) and several concrete actions — "Implement an approved feature from PRODUCT.md and TECH.md, keeping specs and code aligned in the same PR" — but stops short of comprehensive coverage of distinct actions, so it sits below the 5 anchor.	4 / 5
Completeness	Explicitly answers both what ("Implement an approved feature…keeping specs and code aligned in the same PR") and when ("Use after the product and tech specs are approved and the next step is building the feature") with a concrete trigger phrase.	5 / 5
Trigger Term Quality	Natural terms like "approved feature", "PRODUCT.md", "TECH.md", "specs are approved", and "building the feature" give good keyword coverage; a few common synonyms a user might say are absent, keeping it just below 5.	4 / 5
Distinctiveness Conflict Risk	The post-approval/pre-build phase carve-out gives a distinct niche, but overlap risk remains with the related `spec-driven-implementation` skill, so it does not fully reach the minimal-conflict 5 anchor.	4 / 5
	Total	17 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: warpdotdev/common-skills
Path: .agents/skills/implement-specs/SKILL.md
Commit: 69b4753

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.