to-prd

Name: to-prd
Availability: InStock
Author: Switchback

Synthesize a PRD from conversation context and repository glossary.

228|68|Updated Sep 27, 2023

Search Tags:#requirements #adr #synthesis #prd #product-management #issue-tracker #domain-glossary

Ready to run

npx skills add https://github.com/SwitchbackTech/compass-calendar --skill to-prd-switchbacktech

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: to-prd
Source: https://github.com/SwitchbackTech/compass-calendar/tree/main/.agents/skills/to-prd
Command: npx skills add https://github.com/SwitchbackTech/compass-calendar --skill to-prd-switchbacktech

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Turn the current conversation context into a PRD and publish it to the project issue tracker, enabling teams to translate discussions into concrete, trackable requirements.

Core Features & Use Cases

Synthesizes a complete PRD from ongoing dialogue and repository context using the project's domain glossary and ADRs.
Generates structured sections (Problem Statement, Solution, User Stories, Implementation Decisions, Testing Decisions, Out of Scope, Further Notes) ready for issue-tracker publishing.
Publishes or exports the PRD to the project issue tracker and provides a summary for stakeholders.

Quick Start

Turn the current project context into a complete PRD and publish it to the project issue 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 an existing conversation context?▼

To generate a PRD from conversation context, synthesize the dialogue using the repository's domain glossary and ADRs. This captures user constraints and produces a structured document covering problem statements, user stories, and testing decisions ready for issue-tracker publishing.

What sections should a standard product requirements document include for issue trackers?▼

A standard product requirements document for issue trackers should include Problem Statement, Solution, User Stories, Implementation Decisions, Testing Decisions, Out of Scope, and Further Notes. This structure captures essential context and tracks implementation constraints directly from project vocabulary and ADRs.

Can I create a PRD without interviewing stakeholders or gathering additional requirements?▼

Yes, you can create a PRD without interviewing stakeholders by synthesizing the current conversation context and repository domain glossary. It applies existing project ADRs and vocabulary to identify modules, risks, and acceptance criteria without prompting the user for further input.

How do I apply architecture decision records when drafting product requirements?▼

Apply architecture decision records when drafting product requirements by integrating them into the Implementation Decisions section. This ensures the synthesized PRD aligns with established technical constraints, vocabulary, and module definitions already agreed upon within the repository domain glossary.

What is the best way to turn project discussions into trackable issue tracker tickets?▼

The best way to turn project discussions into trackable issue tracker tickets is synthesizing the conversation context into a structured PRD. It automatically identifies modules, risks, and acceptance criteria, outputting a formatted document ready for issue-tracker publishing.

Does generating a PRD from repository context require external dependencies?▼

Generating a PRD from repository context requires no external dependencies. It relies solely on the existing conversation context, domain glossary, and project ADRs to synthesize user needs and constraints into a structured document suitable for publishing.