技能 write-product-spec

📦

write-product-spec

Name: write-product-spec
Author: warpdotdev

内容修订 r1 安全 ⚙️ 外部命令

Write Clear Product Specifications

Turn ambiguous feature requests into structured product specifications that align design, engineering, and review. This skill defines user-visible behavior, scope, references, open questions, and handoff details in a consistent PRODUCT.md format.

支持: Claude Codex Code(CC)

🥉 78 青铜

使用我的智能体安装

将此请求复制给你的智能体，其中包含权威 Skill 页面和清单。

智能体请求

Review the Skillstore skill "write-product-spec" from https://skillstore.io/skills/warpdotdev-write-product-spec.md and its manifest at https://skillstore.io/api/skills/warpdotdev-write-product-spec/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

你的智能体仍应展示其计划，并按安全策略请求必要确认。

Agent 可读资源

当 AI Agent、爬虫或脚本需要干净上下文，而不是读取完整页面时，请使用这些链接。

Markdown 详情 GET /skills/warpdotdev-write-product-spec.md 已签名 manifest GET /api/skills/warpdotdev-write-product-spec/manifest 已签名 lockfile GET /api/skills/warpdotdev-write-product-spec/lockfile

测试它

正在使用“write-product-spec”。 Add a command palette that opens with a keyboard shortcut and supports recent commands.

预期结果:

A PRODUCT.md outline covering the user problem, invocation behavior, search states, empty results, keyboard navigation, scope exclusions, and open questions.

正在使用“write-product-spec”。 Feature request with a Linear ticket and Figma link.

预期结果:

A review-ready specification that places the ticket and design reference in the appropriate context, separates confirmed behavior from open questions, and avoids invented requirements.

正在使用“write-product-spec”。 Ambiguous request to improve tab management.

预期结果:

A focused behavior section for tab actions and states.
Explicit scope boundaries and unresolved product decisions.
A concise handoff suitable for design and engineering review.

安全审计

安全

v1 • 2026/9/18 打开版本化报告

All 29 static findings are false positives. The external-command detections identify Markdown inline-code delimiters in SKILL.md, while the system-reconnaissance detections identify ordinary product-planning prose; no executable commands, network activity, or prompt-injection text is evidenced by the supplied findings.

已扫描文件

165

分析行数

复核项

已忽略误报

最新一次完成的静态与语义审计未检测到已确认的安全发现。这并不能证明该 Skill 没有副作用。

审计者: claude

分享与引用此报告

分享版本化评估报告、中性徽章、嵌入卡片和引用。Skillstore 只报告证据，不判断该 Skill 是否安全。

打开版本化报告

复制报告链接

https://skillstore.io/skills/warpdotdev-write-product-spec/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown 徽章

[![Skillstore security assessment](https://skillstore.io/badges/skills/warpdotdev-write-product-spec/security.svg)](https://skillstore.io/skills/warpdotdev-write-product-spec?utm_source=security_passport_badge)

HTML 徽章

<a href="https://skillstore.io/skills/warpdotdev-write-product-spec?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/warpdotdev-write-product-spec/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

嵌入卡片

<iframe src="https://skillstore.io/embed/skills/warpdotdev-write-product-spec.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). write-product-spec security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/warpdotdev-write-product-spec/audits/1

BibTeX 引用

@techreport{warpdotdev-warpdotdev-write-product-spec-2026,
  author = {warpdotdev},
  title = {write-product-spec security audit report (audit version 1)},
  institution = {Skillstore},
  year = {2026},
  number = {1},
  url = {https://skillstore.io/skills/warpdotdev-write-product-spec/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: "write-product-spec security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
  - name: "warpdotdev"
date-released: "2026-09-18"
url: "https://skillstore.io/skills/warpdotdev-write-product-spec/audits/1"
identifiers:
  - type: other
    value: "skillstore:warpdotdev-write-product-spec:audit:1"
    description: "Skillstore immutable audit report identifier"

Skillstore 评分

评分依据证据置信度: 中

架构

可维护性

内容

社区

规范符合性

你能构建什么

Product discovery brief

Convert an early feature idea into a focused behavior specification with explicit scope and unresolved decisions.

Design handoff

Record user flows, states, and Figma references so designers and engineers share the same expected behavior.

Engineering planning

Give implementers a review-ready PRODUCT.md that clarifies edge cases without prescribing unnecessary implementation details.

试试这些提示

Start a product spec

Create a PRODUCT.md for this feature: [feature idea]. Ask only for missing context that blocks a useful specification.

Clarify feature behavior

Rewrite this feature request as a PRODUCT.md. Define the user problem, expected behavior, scope boundaries, states, and open questions: [request].

Use project references

Create a PRODUCT.md for [feature]. Use this ticket or issue: [link]. Include this design reference if relevant: [Figma link]. Preserve only confirmed context and list unresolved decisions.

Review a specification

Audit this PRODUCT.md for ambiguous behavior, missing edge cases, scope creep, and unsupported assumptions. Return a revised specification plus a concise list of open questions: [specification].

最佳实践

Provide the user problem, feature context, and known constraints before drafting.
Separate confirmed behavior from open questions and assumptions.
Review the specification with product, design, and engineering stakeholders before implementation.

避免

Do not invent ticket details, design decisions, metrics, or requirements.
Do not hide unresolved behavior inside vague implementation language.
Do not use the product specification as a substitute for technical design or test planning.

常见问题

What does this skill produce?

It produces a structured PRODUCT.md specification for a substantial user-facing feature.

Does it implement the feature?

No. It documents expected behavior and scope for later design and engineering work.

Can it use Linear or GitHub references?

Yes. It can include ticket or issue identifiers and links when the user provides them.

Can it use Figma designs?

Yes. It can include a provided Figma link and clearly note when no mock exists.

Will it invent missing requirements?

It should identify missing information as open questions instead of presenting assumptions as facts.

Who benefits most from the output?

Product managers, designers, and engineers who need a shared description of feature behavior.

开发者详情

作者

warpdotdev

许可证

MIT

Skillstore 修订

版本提示

作者未声明版本。

仓库

https://github.com/warpdotdev/common-skills/tree/69b4753651ab7fab518c82be087b9f1d5b966631/.agents/skills/write-product-spec

引用

1268405082c919a1cfb42ed8014623035bf354b3

维护新鲜度

2026/9/18

使用量

0 次下载 · 0 次浏览

文件结构

📄 SKILL.md

write-product-spec

使用我的智能体安装

Agent 可读资源

测试它

安全审计

风险因素

复制报告链接

Markdown 徽章

HTML 徽章

嵌入卡片

APA 引用

BibTeX 引用

CITATION.cff

Skillstore 评分

你能构建什么

Product discovery brief

Design handoff

Engineering planning

试试这些提示

最佳实践

避免

常见问题

开发者详情