skills.rest
ThorStarlord
ThorStarlordCOMMUNITY
Explore all skills by this author →
GitHub

to-prd

Converts current conversation and repository understanding into a complete PRD and publishes it to the issue tracker with ready-for-agent label.

1|Updated May 6, 2026
Search Tags:#specification#issue tracker#prd#product planning#repo analysis#adr compliance#agent triage
One-click install
npx skills add https://github.com/ThorStarlord/interface-skills --skill to-prd-thorstarlord
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: to-prd
Source: https://github.com/ThorStarlord/interface-skills/tree/main/skills/to-prd
Command: npx skills add https://github.com/ThorStarlord/interface-skills --skill to-prd-thorstarlord

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill reduces unclear product intent by converting the current conversation context and existing repository understanding into a structured PRD that can be reviewed and acted on.

Core Features & Use Cases

  • Synthesizes PRD from existing context: Uses what is already known about the codebase and discussion instead of interviewing the user.
  • Follows project vocabularies and governance: Uses the project's domain glossary and respects area-specific ADRs.
  • Creates a ready-to-review artifact for execution: Publishes the PRD to the project issue tracker with the correct triage label for agent readiness.

Quick Start

Use the to-prd skill in the active workspace so it explores the repository as needed, then publishes a complete PRD to the project issue tracker using the provided triage label.

Frequently Asked Questions about to-prd

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

FAQPage Schema
How do I turn conversation context into a publishable PRD?▼

The Skill generates a PRD by analyzing the current conversation context and existing repository understanding, formatting it into a structured specification, and publishing it to the project issue tracker without requiring further user interviewing.

How does agent triage work for product planning issues?▼

Agent triage for product planning issues is initiated by publishing the PRD to the issue tracker with a ready-for-agent triage label. This creates a shared, testable specification for agents and humans to act on.

Does the PRD generation process require user interviewing?▼

No, the PRD generation process does not require additional user interviewing. It synthesizes the product requirements directly from the current conversation context and existing repository understanding.

Can I use domain glossaries and ADR constraints in specification generation?▼

Yes, specification generation specifically uses the project's domain glossary and respects area-specific ADR constraints to ensure the published PRD follows project vocabularies and governance.

What is the best way to create a testable specification for repo analysis?▼

The best way to create a testable specification for repo analysis is to apply the Skill to your product planning scenario, allowing it to explore the repository and convert context into a structured PRD following your template.

When should I not use automated PRD generation from context?▼

You should avoid automated PRD generation from context when the current conversation lacks sufficient product intent or the repository lacks established domain glossaries and ADR constraints for compliance.

Related Skills

Explore More Product & Management Skills→
JuanMS20JuanMS20
1

to-prd

Generate a Product Requirements Document from conversation context and codebase understanding.

Community
Advanced
SamyakJhaveriSamyakJhaveri

to-issues

Convert plans, specs, or PRDs into tracker issues with vertical slices.

Community
Advanced
lobehublobehub
81.4k

linear

Automate Linear issue status updates and completion comments via MCP tools.

Official
Advanced
doravidandoravidan

ralph-plan

Decompose PRD user stories into structured implementation subtasks with dependencies.

Community
Advanced