prd

Generate engineer-focused PRDs from codebase analysis and structured discovery questions.

2|Updated Dec 9, 2025
One-click install
npx skills add https://github.com/signalbeam-io/signalbeam-edge --skill prd-signalbeam-io
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prd
Source: https://github.com/signalbeam-io/signalbeam-edge/tree/main/.claude/skills/prd
Command: npx skills add https://github.com/signalbeam-io/signalbeam-edge --skill prd-signalbeam-io

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generating comprehensive Product Requirements Documents is time-consuming and prone to inconsistencies. This skill automates guided discovery and codebase analysis to produce engineer-ready PRDs that align with existing systems and project goals.

Core Features & Use Cases

  • Guided discovery questions to elicit problem definitions, user roles, success criteria, and scope.
  • Codebase analysis to surface domain entities, services, and architectural constraints that inform PRD content.
  • PRD generation that compiles executive summary, problem statement, goals, success metrics, user stories, functional requirements, technical considerations, dependencies, risks, and open questions.

Quick Start

Provide answers to guided discovery questions and run codebase analysis to generate a PRD.

Frequently Asked Questions about prd

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

FAQPage Schema
How do I generate a Product Requirements Document from an existing codebase?

To generate a Product Requirements Document from a codebase, this Skill analyzes your existing domain entities, commands, and APIs, then combines that with your answers to discovery questions to produce an engineer-ready PRD.

What should a comprehensive PRD include for feature development?

A comprehensive PRD for feature development should include an executive summary, problem statement, goals, success metrics, user stories, functional requirements, technical considerations, dependencies, risks, and open questions.

How does codebase analysis improve PRD generation for engineers?

Codebase analysis improves PRD generation by surfacing existing domain entities, services, and architectural constraints, ensuring the generated product requirements align with your current system patterns and technical limitations.

Can I use guided discovery to define product scope and success criteria before writing documentation?

Yes, you can use guided discovery to define product scope and success criteria before writing documentation. The Skill asks structured questions to elicit problem definitions, user roles, and scope prior to generating the final PRD.

What is the best way to align new feature requirements with existing architectural constraints?

The best way to align new feature requirements with existing architectural constraints is to run a codebase analysis that identifies your current domain entities and services, then use those insights to inform the technical considerations in your generated PRD.

Do I need to manually outline technical considerations and risks when creating product requirements?

No, you do not need to manually outline technical considerations and risks. The Skill automatically compiles these sections into your PRD by analyzing your codebase patterns and applying your discovery answers.