skills.rest
jupes
jupesCOMMUNITY
Explore all skills by this author →
GitHub

to-prd

Create a Product Requirements Document from context and file it as a Beads issue.

2|Updated Apr 11, 2026
Search Tags:#issue tracking#PRD#Beads#requirements management#context synthesis
One-click install
npx skills add https://github.com/jupes/agent-forge-harness --skill to-prd-jupes
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: to-prd
Source: https://github.com/jupes/agent-forge-harness/tree/main/.claude/skills/to-prd
Command: npx skills add https://github.com/jupes/agent-forge-harness --skill to-prd-jupes

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill facilitates the creation of a Product Requirements Document (PRD) by synthesizing context from conversations, codebase, and existing files, and then files it as a Beads feature/epic issue.

Core Features & Use Cases

  • Context Synthesis: Gathers information from conversations, existing issues, code context, and knowledge files to create a PRD.
  • PRD Template Application: Uses a structured template to define problem statements, solutions, user stories, and implementation decisions.
  • Beads Issue Creation: Files the PRD as a feature or epic issue in Beads for further development tracking.
  • Follow-up Work Linking: Optionally creates child tasks in Beads linked to the PRD issue for follow-up implementation tasks.

Quick Start

Use the to-prd skill to generate a PRD for the new feature discussion in the current conversation and codebase context.

Frequently Asked Questions about to-prd

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

FAQPage Schema
How do I create a PRD from existing conversations and codebase context?▼

You can create a PRD by synthesizing information from conversations, existing issues, codebase context, and knowledge files. The skill applies a structured template to define problem statements, solutions, user stories, and implementation decisions from your gathered context.

How do I file a Product Requirements Document as a feature issue in Beads?▼

To file a PRD in Beads, the skill generates the document from your context and submits it directly as a feature or epic issue. You need access to Beads for issue creation to complete this filing process.

Can I link follow-up child tasks to a Beads epic issue?▼

Yes, you can optionally create child tasks in Beads linked to the PRD issue. This links follow-up implementation tasks directly to the parent feature or epic issue for tracking.

What is the best way to manage requirements for a new feature discussion?▼

The best way to manage requirements is synthesizing context from current discussions and existing files into a structured PRD. This defines problem statements, solutions, and user stories before filing the requirements as an issue.

Do I need a Beads account to generate and track Product Requirements Documents?▼

Yes, you need access to Beads because the skill files the generated PRD as a feature or epic issue directly into the platform. This access is required for issue creation and follow-up task linking.

Related Skills

Explore More Product & Management Skills→
hgxszhjhgxszhj

to-prd

Generate a production-ready PRD from conversation context and codebase understanding.

Community
Advanced
decebaldecebal

ralph-tui-create-beads-rust

Convert a Markdown PRD into epic and child beads with dependencies for ralph-tui.

Community
Advanced
GGPromptsGGPrompts
147

brainstorming

Convert vague ideas into structured beads workflows with epics and dependencies.

Community
Basic
sdebaunsdebaun

prd

Generate structured Product Requirements Documents with problem statements, success criteria, and risks.

Community
Advanced