skills.rest
89jobrien
89jobrienCOMMUNITY
Explore all skills by this author →
GitHub

write-product-spec

Generate a PRODUCT.md specification with Summary and Behavior invariants.

Updated Apr 28, 2026
Search Tags:#specification#requirements#invariants#feature-definition#product-spec#product-documentation#engineering-hand-off
One-click install
npx skills add https://github.com/89jobrien/warpx --skill write-product-spec
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: write-product-spec
Source: https://github.com/89jobrien/warpx/tree/main/.agents/skills/write-product-spec
Command: npx skills add https://github.com/89jobrien/warpx --skill write-product-spec

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps product teams articulate clear, unambiguous product specifications to prevent ambiguity during implementation and reviews.

Core Features & Use Cases

  • Generate a comprehensive PRODUCT.md specification that covers Summary, Behavior (invariants), and optional sections.
  • Enable a smooth handoff to engineering and design by aligning stakeholders on scope and success criteria.
  • Use alongside a companion TECH.md to create a complete spec workflow, including decisions and future enhancements, and to plan validation.

Quick Start

Provide the feature name and a concise context, and this Skill will generate a complete PRODUCT.md spec.

Frequently Asked Questions about write-product-spec

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write a product specification for an ambiguous feature?▼

You write a product specification by generating a comprehensive PRODUCT.md document from your feature concepts. It defines the Summary, Behavior with enumerated invariants, and optional sections to establish unambiguous product requirements before design and implementation.

What should be included in engineering hand-off documentation for product requirements?▼

Engineering hand-off documentation should include a PRODUCT.md file containing a Summary, Behavior section with enumerated invariants, and optional sections. This formal product specification aligns stakeholders on scope and success criteria for smooth implementation.

When do I need to create a formal product spec before starting design and implementation?▼

You need to create a formal product spec when a feature is significant or ambiguous and requires formal requirements before design and implementation. Generating a PRODUCT.md prevents ambiguity during development reviews and engineering handoff.

How do I define invariants and behavior rules for a feature definition?▼

You define invariants and behavior rules by structuring the Behavior section of your PRODUCT.md specification. This workflow translates feature concepts into enumerated invariants to establish unambiguous product requirements for engineering teams.

Can I use this product specification workflow alongside technical documentation?▼

Yes, you can use this product specification workflow alongside a companion TECH.md. The generated PRODUCT.md aligns with the TECH.md workflow and DECISIONS.md to create a complete spec workflow including decisions and future enhancements.

What is the best way to document feature requirements to prevent ambiguity during reviews?▼

The best way to prevent ambiguity during reviews is generating a comprehensive PRODUCT.md specification. This formal product documentation articulates clear requirements covering Summary, Behavior, and optional sections to align stakeholders before implementation.

Related Skills

Explore More Product & Management Skills→
Fr-e-dFr-e-d
157

architecture-extract

Analyze project directory structures to generate architectural summaries.

Community
Basic
89jobrien89jobrien

spec-driven-implementation

Enforces spec-first workflow for Warp features via PRODUCT.md and TECH.md files located in specs/.

Community
Advanced
zhengxuyuzhengxuyu

Prd Development

Guide product managers through structured creation of Product Requirements Documents.

Community
Advanced
EchoNoReturnEchoNoReturn

positioning-statement

Draft Geoffrey Moore-style positioning statements with value proposition and differentiation.

Community
Intermediate