to-prd

Convert conversation context into a PRD and submit it as a GitHub issue.

1|Updated May 25, 2026
One-click install
npx skills add https://github.com/chiruu12/nudge --skill to-prd-chiruu12
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: to-prd
Source: https://github.com/chiruu12/nudge/tree/main/.agents/skills/to-prd
Command: npx skills add https://github.com/chiruu12/nudge --skill to-prd-chiruu12

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the process of turning conversation context into a Product Requirements Document (PRD) and submitting it as a GitHub issue, streamlining the documentation and issue tracking process.

Core Features & Use Cases

  • Contextual PRD Generation: Automatically synthesizes a PRD from existing conversation context.
  • GitHub Issue Submission: Files the generated PRD as a GitHub issue.
  • Use Case: Ideal for teams discussing a feature and want to quickly document it without leaving the conversation.

Quick Start

Use the to-prd skill to create a PRD for the current feature discussion.

Frequently Asked Questions about to-prd

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

FAQPage Schema
How do I generate a PRD from conversation context?

To generate a PRD from conversation context, you can use a skill that synthesizes existing discussion details, user stories, and implementation decisions into a structured feature documentation document automatically.

Can I automatically submit a generated PRD as a GitHub issue?

Yes, you can automatically submit a generated PRD as a GitHub issue by using automation scripts that bridge conversation context and issue tracking, streamlining the feature documentation workflow directly into your repository.

What do I need to create effective feature documentation from discussions?

Creating effective feature documentation from discussions requires knowledge of the codebase, specific user stories, and implementation decisions to ensure the generated PRD accurately reflects the technical context and administrative workflows.

What is the best way to track feature discussions as GitHub issues?

The best way to track feature discussions as GitHub issues is to automatically convert the conversation context into a PRD and submit it directly to the repository, ensuring implementation decisions are documented and tracked.

Does automated PRD generation work without codebase analysis?

Automated PRD generation is optimized when codebase analysis is available, as it requires knowledge of the codebase, user stories, and implementation decisions to accurately synthesize administrative workflows and feature documentation.