skills.rest
warpdotdev
warpdotdevOFFICIAL
Explore all skills by this author →
WebsiteGitHub

create-product-spec

Convert GitHub issues into structured product spec artifacts.

292|39|Updated Mar 17, 2026
Search Tags:#automation#workflow#documentation#specification#github-issues#product-spec
One-click install
npx skills add https://github.com/warpdotdev/oz-for-oss --skill create-product-spec
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: create-product-spec
Source: https://github.com/warpdotdev/oz-for-oss/tree/main/.agents/skills/create-product-spec
Command: npx skills add https://github.com/warpdotdev/oz-for-oss --skill create-product-spec

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts a GitHub issue into a structured product spec artifact to enable product documentation workflows without applying code changes.

Core Features & Use Cases

  • Wrapper around the local shared write-product-spec workflow to generate specs from issue data.
  • Outputs specs at specs/GH<issue-number>/product.md and may produce pr-metadata.json when requested by a workflow.
  • Supports optional issue_comments.txt and triggering-comment context as inputs; does not modify production code or create commits by default.

Quick Start

Provide the GitHub issue details to generate a product spec at specs/GH<issue-number>/product.md; the wrapper will not create commits or PRs unless a cloud workflow requests it.

Frequently Asked Questions about create-product-spec

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

FAQPage Schema
How do I generate a product spec from a GitHub issue?▼

Generate a product spec from a GitHub issue by providing the issue details to the workflow, which outputs a structured artifact at specs/GH<issue-number>/product.md without creating commits or PRs.

Can I include issue comments when converting an issue into a product specification?▼

Include issue comments when converting an issue into a product specification by supplying an optional issue_comments.txt file as input alongside the triggering comment context to enrich the generated spec.

Does creating a product spec from GitHub issues automatically commit changes to my repository?▼

Creating a product spec from GitHub issues does not automatically commit changes or create PRs; it only generates the spec artifact files locally unless a cloud workflow explicitly requests it.

What is the output file path for a generated product specification?▼

The output file path for a generated product specification is specs/GH<issue-number>/product.md, and it may optionally produce a pr-metadata.json file when requested by a workflow.

What's the best way to document product requirements from GitHub issues without modifying code?▼

Document product requirements from GitHub issues without modifying code by using this wrapper around the shared write-product-spec workflow, which consumes issue data to produce specification artifacts only.

Why use a product spec workflow instead of directly coding from GitHub issues?▼

Use a product spec workflow instead of directly coding to establish structured documentation from issue data, enabling clearer product requirements tracking before development begins without applying code changes.

Related Skills

Explore More Product & Management Skills→
warpdotdevwarpdotdev
292

implement-issue

Orchestrate issue-to-diff translation using local shared implementation skills.

Official
Intermediate
warpdotdevwarpdotdev
292

create-tech-spec

Generate a structured tech spec from a GitHub issue into specs/GH<issue-number>/tech.md.

Official
Intermediate
dgethingsdgethings

atlassian-itsm

Automate Jira and Confluence ITSM workflows with human-in-the-loop governance.

Community
Advanced
AcendWayAcendWay

to-prd

Convert conversation context into a structured PRD for GitHub issue submission.

Community
Basic