spec-driven-implementation
Plan Features With Living Specs
Substantial feature work can become ambiguous when product intent, technical decisions, and implementation drift apart. This skill guides agents through practical product and technical specifications that stay aligned with shipped work.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "spec-driven-implementation" from https://skillstore.io/skills/warpdotdev-spec-driven-implementation.md and its manifest at https://skillstore.io/api/skills/warpdotdev-spec-driven-implementation/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "spec-driven-implementation". We need a new workspace invitation flow with several permission states and an uncertain rollout.
Expected outcome:
Recommendation: write PRODUCT.md first and TECH.md after the permission model is settled. The request has user-facing edge cases, cross-cutting behavior, and rollout risk.
Using "spec-driven-implementation". The implementation now supports invitation expiration, but PRODUCT.md does not mention it.
Expected outcome:
- Update PRODUCT.md with expiration behavior and recovery rules.
- Add success criteria for expired invitations.
- Add tests that cover expiration and re-invitation.
Using "spec-driven-implementation". The feature spans API, persistence, background jobs, and the client.
Expected outcome:
TECH.md should document boundaries, data flow, failure handling, dependencies, rollout sequencing, and the test strategy before implementation begins.
Security Audit
SafeAll 23 static findings are false positives: the detector matched Markdown inline-code spans in SKILL.md, not executable Ruby or shell commands. The reviewed skill describes a specification workflow and contains no evidence of prompt injection, network activity, credential access, or data exfiltration.
Risk Factors
⚙️ External commands (23)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/warpdotdev-spec-driven-implementation/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/warpdotdev-spec-driven-implementation?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/warpdotdev-spec-driven-implementation?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/warpdotdev-spec-driven-implementation/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/warpdotdev-spec-driven-implementation.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
warpdotdev. (2026). spec-driven-implementation security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/warpdotdev-spec-driven-implementation/audits/1BibTeX citation
@techreport{warpdotdev-warpdotdev-spec-driven-implementation-2026,
author = {warpdotdev},
title = {spec-driven-implementation security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/warpdotdev-spec-driven-implementation/audits/1},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "spec-driven-implementation security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
- name: "warpdotdev"
date-released: "2026-09-18"
url: "https://skillstore.io/skills/warpdotdev-spec-driven-implementation/audits/1"
identifiers:
- type: other
value: "skillstore:warpdotdev-spec-driven-implementation:audit:1"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: MediumWhat You Can Build
Plan a Large Feature
Turn an ambiguous feature request into a product spec, a technical plan when needed, and clear validation criteria.
Coordinate Agent Implementation
Give coding agents stable behavioral and technical context before they implement a cross-cutting change.
Keep Documentation Current
Review implementation changes and update the relevant specifications so the repository describes the behavior that actually ships.
Try These Prompts
Assess this feature request for size, ambiguity, and risk. Recommend whether to write PRODUCT.md, TECH.md, both, or neither. Explain the decision briefly.
Write a PRODUCT.md for this feature. Cover the user problem, intended behavior, invariants, edge cases, success criteria, and validation approach. Keep implementation details separate.
Using the approved product behavior and repository context, draft a TECH.md for this feature. Document architecture, interfaces, tradeoffs, risks, dependencies, rollout, and testing.
Compare PRODUCT.md and TECH.md with the current implementation and tests. List behavior or architecture drift, then propose precise spec updates and missing verification.
Best Practices
- Write product behavior before choosing implementation details.
- Use a technical specification when boundaries, tradeoffs, or risks are meaningful.
- Update specifications whenever shipped behavior or architecture changes.
Avoid
- Do not write specifications for routine changes that gain no clarity from them.
- Do not let technical details replace user-facing behavior and success criteria.
- Do not leave specifications unchanged after implementation diverges from the plan.
Frequently Asked Questions
When should I use this skill?
Is a technical specification always required?
What belongs in PRODUCT.md?
What belongs in TECH.md?
Can this skill implement the feature?
How do I keep specifications accurate?
Developer Details
Author
warpdotdevLicense
MIT
Skillstore revision
r1
Version notice
The author did not declare a version.
Ref
eb894b254e754cba4a46d73e6e8e54cfe1e3316b
Maintenance freshness
9/18/2026
Usage
0 downloads · 0 views
File structure
📄 SKILL.md