create-product-spec

Create product specifications from GitHub issues using a predefined template.

2|2|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/codysumpter-cloud/buddy-brain --skill create-product-spec-codysumpter-cloud
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-product-spec
Source: https://github.com/codysumpter-cloud/buddy-brain/tree/main/.agents/skills/create-product-spec
Command: npx skills add https://github.com/codysumpter-cloud/buddy-brain --skill create-product-spec-codysumpter-cloud

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the creation of product specifications from GitHub issues or operator requests, streamlining the process of defining user-facing intent artifacts before implementation.

Core Features & Use Cases

  • Issue Analysis: Extracts information from GitHub issues to form the basis of a product spec.
  • Template-Based Creation: Utilizes a template to ensure all necessary components of a product spec are included.
  • Use Case: When a new feature is requested, this Skill can be used to quickly generate a product spec that outlines the intended functionality and user experience.

Quick Start

Generate a product spec for the issue #123 by running the command: create-product-spec issue #123.

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 automatically?

You can automate product spec creation from GitHub issues by running a command like `create-product-spec issue #123`. This Skill analyzes the issue text and applies a predefined template to output a structured product specification document ready for review.

What is the best way to define user-facing intent artifacts before implementation planning?

Automating product spec creation from GitHub issues streamlines the definition of user-facing intent artifacts before implementation. It extracts information from the issue text and applies a predefined template to generate the product spec document.

Does this automated specification approach work with operator requests as well as GitHub issues?

Yes, this automated specification approach supports both GitHub issues and operator requests. It extracts information from the request text and applies a predefined template to generate a structured product spec document for implementation planning.

How do I ensure all necessary components are included when creating a product spec from a feature request?

You ensure all necessary components are included by using a template-based creation process. This Skill extracts information from the feature request and applies a predefined template to consistently generate a complete product spec document for review.

What are the limitations of using a template for product spec generation from issue text?

A limitation of template-based product spec generation is that the output structure is fixed by the predefined template. The resulting document relies entirely on the information successfully extracted from the issue text, so incomplete requests will yield incomplete specifications.