write-product-spec

Generate a PRODUCT.md specification for a Warp feature.

Updated Apr 30, 2026

Search Tags:#planning #documentation #spec #behavior #product #prd #warp

Ready to run

npx skills add https://github.com/lalaABC/waprcn --skill write-product-spec-lalaabc

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: write-product-spec
Source: https://github.com/lalaABC/waprcn/tree/main/.agents/skills/write-product-spec
Command: npx skills add https://github.com/lalaABC/waprcn --skill write-product-spec-lalaabc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generating a precise, user-facing PRODUCT.md specification for a Warp feature to align product, design, and engineering before implementation.

Core Features & Use Cases

Documents the user-facing surface, behavior, invariants, and acceptance criteria in a single artifact.
Enables cross-functional review and sign-off prior to development.
Serves as the single source of truth for feature scope, edge cases, and non-goals.

Quick Start

Provide a complete PRODUCT.md specification for a Warp feature.

Frequently Asked Questions about write-product-spec

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

FAQPage Schema

How do I generate a product spec for a Warp feature?▼

To generate a product spec, provide a feature brief to create a comprehensive PRODUCT.md file. This specification outlines the user-visible surface, behavior, invariants, and edge cases for cross-functional review.

What is the best way to structure a PRD for Warp features?▼

The best way to structure a PRD is using a PRODUCT.md artifact that documents the user-facing surface, behavior, invariants, and acceptance criteria. This serves as the single source of truth for feature scope and non-goals.

How do I document edge cases and invariants in a feature brief?▼

Document edge cases and invariants in a feature brief by generating a comprehensive PRODUCT.md specification. This artifact captures feature scope, user-visible behavior, and acceptance criteria to align product, design, and engineering.

Can I save a generated product spec to a specific Linear ticket or issue ID?▼

Yes, you can save the product spec using a Linear ticket number, gh-issue ID, or kebab-case feature name. The specification is saved to the specs/<id>/PRODUCT.md directory path for organized retrieval.

Does the product spec generation include technical implementation details?▼

Yes, a companion TECH.md file for implementation details can be provided upon request. The primary PRODUCT.md focuses on user-facing behavior and scope, while TECH.md handles the downstream technical implementation.

When do I need a separate product specification before starting development?▼

You need a separate product specification when aligning product, design, and engineering teams prior to implementation. Generating a precise PRD ensures cross-functional review and sign-off on feature scope and edge cases.