skills.rest
rnaarla
rnaarlaCOMMUNITY
Explore all skills by this author →
GitHub

to-prd

Generate a PRD from conversation context and publish it to the issue tracker.

Updated Apr 28, 2026
Search Tags:#planning#documentation#requirements#prd#product-management#user-stories#issue-tracker
One-click install
npx skills add https://github.com/rnaarla/agent_skills --skill to-prd-rnaarla
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: to-prd
Source: https://github.com/rnaarla/agent_skills/tree/main/skills/engineering/to-prd
Command: npx skills add https://github.com/rnaarla/agent_skills --skill to-prd-rnaarla

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Turn raw conversation context and codebase understanding into a structured PRD without interviewing the user, saving time and reducing misalignment.

Core Features & Use Cases

  • Synthesize problem statements, goals, and success criteria from current context.
  • Generate user stories and an implementation plan suitable for an issue tracker.
  • Publish PRD to the project's issue tracker using provided vocab and ADRs.

Quick Start

Provide the current project context and let the agent generate and publish a PRD to the project tracker.

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 existing conversation context without conducting user interviews?▼

Generate a PRD from context by letting the agent synthesize problem statements and goals from the current conversation. It produces user stories and acceptance criteria ready for publication without requiring further user interviews.

Can I automatically publish user stories and acceptance criteria directly to a project issue tracker?▼

You can publish user stories and acceptance criteria to an issue tracker. The agent generates the PRD and publishes it directly to the project tracker using the provided vocabulary and architecture decision records.

What is the best way to turn raw codebase understanding into structured product management documentation?▼

Turn raw context into product management documentation by synthesizing problem statements, goals, and success criteria. This approach extracts domain terms and outlines modules to create a comprehensive ready-to-publish PRD.

Does generating a PRD this way require any external dependencies or components?▼

Generating a PRD this way requires no external dependencies or components. The agent operates independently to translate the current project context into a structured PRD ready for the issue tracker.

What should be included in a PRD to guide design and implementation across multiple modules?▼

A PRD guiding design across modules should include extracted domain terms, user stories, defined acceptance criteria, and outlined modules. The agent synthesizes these elements from available context to ensure comprehensive coverage.

Related Skills

Explore More Product & Management Skills→
MomoDavilukeMomoDaviluke
2

to-prd

Generate a structured PRD from conversation context and repository insights.

Community
Advanced
malinskibeniaminmalinskibeniamin
3

to-prd

Generate a formal PRD from project context and publish it to the issue tracker.

Community
Intermediate
anonymousminatianonymousminati

to-issues

Break plans into dependency-ordered tracer-bullet issues with acceptance criteria.

Community
Intermediate
asalhamedasalhamed

business-analyst

Decompose PRDs into INVEST-aligned user stories and business rules.

Community
Advanced