编写产品规格 是做什么的？
为Warp中的重大用户功能编写一份PRODUCT.md规格说明，重点描述详细行为和验证方法。当用户要求提供产品规格、期望行为文档或PRD，希望在进行开发前定义功能行为，或者该功能足够重要或行为上存在歧义，以至于书面的规格说明能改善实现或审查时使用。
为Warp中的重大用户功能编写一份PRODUCT.md规格说明，重点描述详细行为和验证方法。当用户要求提供产品规格、期望行为文档或PRD，希望在进行开发前定义功能行为，或者该功能足够重要或行为上存在歧义，以至于书面的规格说明能改善实现或审查时使用。
该技能旨在帮助开发者或AI代理在Warp项目设计中，为重大用户功能创建一份详细的PRODUCT.md规格说明。其核心价值在于通过结构化的文档，明确功能的行为、边界条件和验证方法，从而提升实现效率和代码审查质量。它特别适用于功能行为复杂、定义模糊或需要多方协作的场景。通过自动生成一个包含背景、目标、用户故事、技术约束和验收标准等节标题的框架，该技能降低了从零开始撰写产品需求文档的门槛，并确保规格的完整性和一致性。支持的平台包括Warp等基于终端的开发环境，工作流程基于读取用户输入的需求后，以Markdown格式输出规范的规格说明。
npx skills add https://github.com/warpdotdev/common-skills/tree/main/skills/write-product-specInstalled? Explore more 编程与开发 skills: steipete/bluebubbles, steipete/eightctl, steipete/blucli · View all 6 →
为Warp中的重大用户功能编写一份PRODUCT.md规格说明，重点描述详细行为和验证方法。当用户要求提供产品规格、期望行为文档或PRD，希望在进行开发前定义功能行为，或者该功能足够重要或行为上存在歧义，以至于书面的规格说明能改善实现或审查时使用。
This repo contains 16 individual skills — each has its own dedicated page.
Guides creation, revision, and review of Warp- or Oz-branded assets. Use when working on launch pages, docs, HTML/CSS components, UI mockups, prompts, social assets, copy, presentations, or any other branded deliverable that should look and sound unmistakably Warp or Oz.
Compare a pull request's implementation against spec context in spec_context.md and feed any material mismatches into review.json. Use during PR review when approved or repository spec context is available.
Run a model-diverse subagent council to investigate the same problem from multiple perspectives, compare findings, and produce a final recommendation. Use this skill whenever the user asks for a council, second opinions, multiple agents/models to evaluate one question, parallel investigation, red-team/blue-team comparison, or help deciding between competing technical approaches.
Create a pull request in the warp repository for the current branch. Use when the user mentions opening a PR, creating a pull request, submitting changes for review, or preparing code for merge.
Diagnose CI failures for a PR using the GitHub CLI, extract error logs, and generate a plan to fix them. Use when the user asks to check CI status, pull CI issues, triage test failures, or investigate PR build failures.
Fix compilation errors, linting issues, and test failures in the warp Rust codebase. Covers presubmit checks, WASM-specific errors, and running specific tests. Use when the user hits build errors, clippy or fmt failures, test failures, or needs to run or interpret presubmit before a PR.
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.
Generate a static interactive D3 walkthrough of a pull request. Use when the user wants a zoomable PR map, graph/canvas PR orientation, or alternate visualization of PR system components, data flow, code dependencies, and user actions.
Launch Oz cloud agents with computer use to reproduce UI-focused bug reports, capture visual evidence, and report reproduction findings. Use when investigating a specific interactive or visual bug from an issue, ticket, support report, or prompt.
Resolve Git merge conflicts by extracting only unresolved paths, conflict hunks, and compact diffs instead of loading whole files into context. Use when a merge, rebase, cherry-pick, or stash pop stops on conflicts, when `git status` shows unmerged paths, or when files contain conflict markers.
Walk users through PR review comments, fetching and displaying them first when needed, collect per-comment response decisions, apply requested fixes, and preview GitHub replies and resolutions before posting. Use when responding to PR review comments on the current branch.
Review a pull request diff and write structured feedback to review.json for the workflow to publish. Use when reviewing a checked-out PR from local artifacts like pr_diff.txt and pr_description.txt and producing machine-readable review output instead of posting directly to GitHub.
Drive a spec-first workflow for substantial features by writing PRODUCT.md before implementation, writing TECH.md when warranted, and keeping both specs updated as implementation evolves. Use when starting a significant feature, planning agent-driven implementation, or when the user wants product and tech specs checked into source control.
Create or update skills by generating, editing, or refining SKILL.md files in this repository. Use when authoring new skills or revising the structure, frontmatter, or guidance for existing ones.
Validate that a branch or pull request implementation matches introduced product, technical, security, and related specs. Use when reviewing or finishing a spec-driven change and resolving mismatches between checked-in specs and implementation.
Write a TECH.md spec for a significant Warp feature after researching the current codebase and implementation constraints. Use when the user asks for a technical spec, implementation plan, or architecture doc tied to a product spec.
Send and manage iMessages via BlueBubbles, including attachments, tapbacks, edits, replies, and groups.
Control Eight Sleep pods (status, temperature, alarms, schedules).
BluOS CLI (blu) for discovery, playback, grouping, and volume.
Create, search, and manage Bear notes via grizzly CLI.
Capture frames or clips from RTSP/ONVIF cameras.
Search GIF providers with CLI/TUI, download results, and extract stills/sheets.