prd

Generate a GitHub issue structured as a Product Requirements Document.

Updated Mar 9, 2026
One-click install
npx skills add https://github.com/MatthieuGagne/gmb-nuke-raider --skill prd-matthieugagne
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prd
Source: https://github.com/MatthieuGagne/gmb-nuke-raider/tree/main/.claude/skills/prd
Command: npx skills add https://github.com/MatthieuGagne/gmb-nuke-raider --skill prd-matthieugagne

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the creation of Product Requirements Documents (PRDs) by directly generating a GitHub issue, ensuring a centralized and actionable record of feature specifications.

Core Features & Use Cases

  • Automated Issue Creation: Generates a GitHub issue with a pre-defined PRD structure.
  • Centralized Documentation: The GitHub issue serves as the single source of truth for the PRD.
  • Use Case: After a product brainstorming session, use this Skill to instantly create a GitHub issue for a new feature, populating it with the agreed-upon goal, requirements, and acceptance criteria.

Quick Start

Use the prd skill to create a new GitHub issue for a feature.

Frequently Asked Questions about prd

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

FAQPage Schema
How do I create a Product Requirements Document directly as a GitHub issue?

To create a Product Requirements Document as a GitHub issue, this Skill automatically structures your feature specifications into goals, requirements, and acceptance criteria, then leverages the GitHub CLI to generate the issue directly in your repository.

What is the best way to structure feature specifications for development tracking?

The best way to structure feature specifications is by generating a standardized GitHub issue that serves as a centralized Product Requirements Document, populating fields like goals, scope, and acceptance criteria to maintain a single source of truth.

Do I need the GitHub CLI installed to generate PRDs as issues?

Yes, you need the GitHub CLI (`gh`) installed and authenticated, because the Skill leverages it directly to create the GitHub issue and link the Product Requirements Document to your development workflow.

Can I use this for centralized feature documentation after a brainstorming session?

Yes, you can use this for centralized feature documentation by instantly creating a GitHub issue after a brainstorming session, populating it with the agreed-upon product requirements and acceptance criteria.

What sections are included in the generated feature specification issue?

The generated feature specification issue includes sections for goals, requirements, acceptance criteria, and scope, ensuring a structured Product Requirements Document for your new feature.

Why use a GitHub issue for a PRD instead of a separate document?

Using a GitHub issue for a PRD ensures a centralized and actionable record of feature specifications, providing a direct link to your development workflow and serving as the single source of truth for product requirements.