to-prd

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

Updated Jun 8, 2026
One-click install
npx skills add https://github.com/Avistian/nba --skill to-prd-avistian
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: to-prd
Source: https://github.com/Avistian/nba/tree/main/.agents/skills/to-prd
Command: npx skills add https://github.com/Avistian/nba --skill to-prd-avistian

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a long design conversation into a structured Product Requirements Document is tedious and error-prone. This Skill converts the discussion you have already had into a complete PRD and publishes it to your issue tracker, without re-interviewing you. ## Core Features & Use Cases - Conversation-to-PRD Synthesis: Generates a full PRD (problem statement, solution, user stories, implementation and testing decisions, scope) purely from existing conversation context and codebase exploration. - Test Seam Planning: Identifies the highest-level testing seams in the codebase and confirms them with you before writing the PRD. - Issue Tracker Publishing: Publishes the finished PRD to the project issue tracker and applies the ready-for-agent triage label. - Use Case: After discussing a new feature with your AI assistant, invoke this Skill to produce a ready-to-implement PRD ticket without writing any documentation yourself. ## Quick Start Ask the assistant to turn our 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 this Skill after discussing the feature with your AI assistant. It synthesizes the existing conversation and codebase context into a full PRD with problem statement, user stories, and implementation decisions, then publishes it to your issue tracker.

Does this PRD generator interview the user for requirements?▼

No. The Skill explicitly avoids interviewing and instead synthesizes what has already been discussed in the conversation, combined with exploration of the repository's current state, glossary, and ADRs.

What sections does the generated PRD template include?▼

The PRD includes a problem statement, solution, an extensive numbered list of user stories, implementation decisions, testing decisions, out-of-scope items, and further notes. File paths and code snippets are excluded except for decision-rich prototype fragments.

What setup is required before publishing PRDs to the issue tracker?▼

The issue tracker and triage label vocabulary must be configured beforehand, via the /setup-matt-pocock-skills command. After publishing, the Skill applies the ready-for-agent triage label with no additional triage needed.

When should I not use conversation-to-PRD synthesis?▼

Avoid it when requirements have not yet been discussed, since the Skill only synthesizes existing context. It also requires user confirmation of proposed testing seams before writing, so it is not a fully unattended pipeline.