write-product-spec 是做什麼的？
為 Warp 中重要的使用者面向功能撰寫一份 PRODUCT.md 規格，重點在於詳細的行為與驗證。當使用者要求產品規格、期望行為文件或 PRD，想要在實作前定義功能行為，或當功能規模龐大或行為模糊，需要書面規格以利實作與審查時使用。
為 Warp 中重要的使用者面向功能撰寫 PRODUCT.md 規格，重點在於詳細的行為與驗證。當使用者要求產品規格、期望行為文件或 PRD，想要在實作前定義功能行為，或當功能規模龐大或行為模糊需要書面規格以利實作與審查時使用。
這個技能旨在為 Warp 終端機中的使用者面向功能生成一份嚴謹的 PRODUCT.md 規格文件。它被設計用於當開發者需要清晰定義一個功能在實作前的預期行為，特別是針對那些規模較大或行為較複雜、需要詳細文件來確保實作與審查順利的場景。此技能支援直接在 Warp 環境中使用，並透過分析使用者提示來產出包含詳細行為描述、驗證準則和邊界情況的結構化規格。其核心運作方式是根據使用者的簡短描述或需求，自動擴展成一份完整的產品需求文件，涵蓋功能概述、詳細行為、驗證清單與邊界情況等重要部分，從而減少溝通成本與實作歧異。
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.