skills.rest
truongnat
truongnatCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

to-prd-pro

Create a PRD from conversation and codebase context and submit it as a GitHub issue.

Updated Jun 27, 2026
Search Tags:#software development#prd#github issue#feature spec#product documentation
One-click install
npx skills add https://github.com/truongnat/aix --skill to-prd-pro
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: to-prd-pro
Source: https://github.com/truongnat/aix/tree/main/content/skills/to-prd-pro
Command: npx skills add https://github.com/truongnat/aix --skill to-prd-pro

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill transforms the conversation context and codebase understanding into a structured Product Requirements Document (PRD) and submits it as a GitHub issue, streamlining the process of documenting and tracking feature specifications.

Core Features & Use Cases

  • PRD Synthesis: Creates a PRD by synthesizing known information from the conversation context and codebase without interviewing the user.
  • GitHub Issue Creation: Submits the PRD as a GitHub issue, facilitating feature specification and tracking.
  • Use Case: Ideal for users who want to produce a PRD, write a feature spec, or capture product decisions without re-interviewing the user.

Quick Start

Use the to-prd-pro skill to create a PRD for the current feature discussion and submit it as a GitHub issue.

Frequently Asked Questions about to-prd-pro

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

FAQPage Schema
How do I convert a conversation context into a structured PRD?▼

To convert conversation context into a structured PRD, you can synthesize the existing discussion and codebase context directly into a Product Requirements Document without needing additional user interviews.

How to create a GitHub issue from a feature spec automatically?▼

You can create a GitHub issue from a feature spec automatically by synthesizing the product requirements document from your conversation context and submitting it directly through the GitHub CLI.

Do I need the GitHub CLI to generate product documentation for issues?▼

Yes, you need the GitHub CLI installed and configured, as it is a required dependency for submitting the generated product documentation as a GitHub issue.

What is the best way to capture product decisions without re-interviewing the user?▼

The best way to capture product decisions without re-interviewing is to synthesize known information from the conversation context and codebase directly into a structured feature specification.

Does this PRD generation approach work with existing codebase context?▼

Yes, this PRD generation approach works by extracting and synthesizing existing codebase context alongside conversation history to build a complete product requirements document.

Why does PRD generation from conversation context skip the interview process?▼

PRD generation skips the interview process to streamline software development workflows, capturing product decisions immediately from available conversation and codebase context without interrupting the user.

Related Skills

Explore More Product & Management Skills→
gqf2008gqf2008

github-auth

Authenticate Hermes Agent with GitHub via gh CLI or git tokens and SSH keys.

Community
Intermediate
SebastienDegodezSebastienDegodez
8

sprint-planning

Manage sprint planning with MoSCoW prioritization and GitHub milestones.

Community
Advanced
anonymousminatianonymousminati

improve-codebase-architecture

Analyze codebases to identify architectural friction and refactoring opportunities.

Community
Advanced
cuongtl1992cuongtl1992
10

spec-writer

Generate structured PRDs with Problem Statement, User Stories, MoSCoW, and Success Metrics.

Community
Advanced