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.
使用我的智能体安装
将此请求复制给你的智能体，其中包含权威 Skill 页面和清单。
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.你的智能体仍应展示其计划，并按安全策略请求必要确认。
Agent 可读资源
当 AI Agent、爬虫或脚本需要干净上下文，而不是读取完整页面时，请使用这些链接。
测试它
正在使用“spec-driven-implementation”。 We need a new workspace invitation flow with several permission states and an uncertain rollout.
预期结果:
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.
正在使用“spec-driven-implementation”。 The implementation now supports invitation expiration, but PRODUCT.md does not mention it.
预期结果:
- Update PRODUCT.md with expiration behavior and recovery rules.
- Add success criteria for expired invitations.
- Add tests that cover expiration and re-invitation.
正在使用“spec-driven-implementation”。 The feature spans API, persistence, background jobs, and the client.
预期结果:
TECH.md should document boundaries, data flow, failure handling, dependencies, rollout sequencing, and the test strategy before implementation begins.
安全审计
安全All 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.
风险因素
分享与引用此报告
分享版本化评估报告、中性徽章、嵌入卡片和引用。Skillstore 只报告证据，不判断该 Skill 是否安全。
复制报告链接
https://skillstore.io/skills/warpdotdev-spec-driven-implementation/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown 徽章
[](https://skillstore.io/skills/warpdotdev-spec-driven-implementation?utm_source=security_passport_badge)HTML 徽章
<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>嵌入卡片
<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>学术引用 (APA · BibTeX · CFF)
APA 引用
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 引用
@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 评分
评分依据 证据置信度: 中你能构建什么
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.
试试这些提示
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.
最佳实践
- 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.
避免
- 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.
常见问题
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?
开发者详情
作者
warpdotdev许可证
MIT
Skillstore 修订
r1
版本提示
作者未声明版本。
引用
eb894b254e754cba4a46d73e6e8e54cfe1e3316b
维护新鲜度
2026/9/18
使用量
0 次下载 · 0 次浏览
文件结构
📄 SKILL.md