to-prd

Synthesizes conversation context into a PRD and publishes it to the project issue tracker.

1|Updated Mar 2, 2026
One-click install
npx skills add https://github.com/mst-software-vn/mst-checkscam --skill to-prd-mst-software-vn
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: to-prd
Source: https://github.com/mst-software-vn/mst-checkscam/tree/main/.claude/skills/to-prd
Command: npx skills add https://github.com/mst-software-vn/mst-checkscam --skill to-prd-mst-software-vn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a long design discussion into a formal Product Requirements Document is tedious and often loses context. This Skill converts the current conversation and codebase understanding directly into a structured PRD without re-interviewing the user. ## Core Features & Use Cases - Context Synthesis: Explores the repository, respects existing ADRs and domain glossary vocabulary, and synthesizes what has already been discussed rather than asking new questions. - Test Seam Planning: Identifies the highest-level testing seams for the feature and confirms them with the user before writing. - Structured PRD Publishing: Generates a PRD with problem statement, solution, extensive user stories, implementation and testing decisions, then publishes it to the project issue tracker with the ready-for-agent triage label. - Use Case: After discussing a new feature with your AI assistant, invoke this Skill to produce a complete PRD issue ready for an implementation agent to pick up. ## Quick Start Ask the assistant to turn the current conversation into a PRD and publish it to the 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 turn a conversation into a PRD?▼

Invoke the to-prd skill after discussing the feature. It synthesizes the existing conversation and codebase context into a structured PRD with problem statement, user stories, and implementation decisions, then publishes it to the issue tracker.

Does the PRD skill ask interview questions before writing?▼

No. The skill explicitly avoids interviewing the user and instead synthesizes what has already been discussed. It only checks with the user to confirm the proposed testing seams match expectations.

What sections does the generated PRD template include?▼

The template includes Problem Statement, Solution, an extensive numbered list of User Stories, Implementation Decisions, Testing Decisions, Out of Scope, and Further Notes. Code snippets are excluded except for decision-rich prototype fragments.

How does the skill choose testing seams for a feature?▼

It prefers existing seams over new ones and selects the highest seam possible, aiming for as few seams as possible across the codebase. Proposed seams are confirmed with the user before the PRD is written.

What happens after the PRD is published to the issue tracker?▼

The published issue receives the ready-for-agent triage label, signaling it is prepared for an implementation agent to pick up without additional triage steps.