skills.rest
LerianStudio
LerianStudioOFFICIAL
Explore all skills by this author →
Website𝕏@lerianstudioGitHub

ring:pre-dev-prd-creation

Create PRDs by codifying business requirements before technical design.

4|Updated Jan 10, 2026
Search Tags:#scoping#requirements#prd#product-management#user-stories#stakeholders
One-click install
npx skills add https://github.com/LerianStudio/ring-for-opencode --skill ring-pre-dev-prd-creation
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ring:pre-dev-prd-creation
Source: https://github.com/LerianStudio/ring-for-opencode/tree/main/assets/skill/pre-dev-prd-creation
Command: npx skills add https://github.com/LerianStudio/ring-for-opencode --skill ring-pre-dev-prd-creation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps product teams create clear, stakeholder-aligned PRDs by capturing the problem, user personas, acceptance criteria, and success metrics before any technical design begins.

Core Features & Use Cases

  • Gate-based PRD workflow that separates business requirements from technical design.
  • Templates and prompts for problem discovery, user stories, scope, and success metrics.
  • Use Case: when planning a major feature, generate a ready-to-review PRD that can feed TRD later.

Quick Start

Describe a new feature and its target users to trigger Gate 1 PRD creation and draft the initial PRD.

Frequently Asked Questions about ring:pre-dev-prd-creation

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

FAQPage Schema
How do I define product requirements before technical design begins?▼

To define product requirements before technical design, use a gate-based PRD workflow to capture the problem, user personas, acceptance criteria, and success metrics, ensuring business clarity separates from technical implementation.

What is the best way to create user stories and scope boundaries for a new feature?▼

The best way to create user stories and scope boundaries is using structured PRD templates that guide problem discovery and establish measurable outcomes, ensuring alignment among stakeholders before development starts.

How do I generate a PRD ready for stakeholder review when planning a major feature?▼

You generate a ready-to-review PRD by describing a new feature and its target users to trigger the initial draft, which codifies business requirements, user personas, and success metrics into a structured document.

Can I feed a completed PRD into a technical design document later?▼

Yes, you can feed a completed PRD into technical design steps later. The PRD output is suitable for escalation into further TRD processes once the initial business requirements gate is cleared.

What success metrics and problem definition should a PRD include for new products?▼

A PRD for new products should include a clear problem definition and measurable success metrics. It must cover user personas, acceptance criteria, and scope boundaries to complete the initial planning gate.

Related Skills

Explore More Product & Management Skills→
LerianStudioLerianStudio
205

pre-dev-prd-creation

Generate a complete PRD with problem discovery, user stories, and success metrics.

Official
Basic
jinglemansweepjinglemansweep

jp-prd-review

Review PRD documents against source prompts for gaps and feasibility issues.

Community
Advanced
hanzlahabibhanzlahabib
2

rcode-hussain-pm

Define product requirements and scope for ambiguous feature ideas.

Community
Advanced
elsolalelsolal
1

pm-prd

Convert brainstorm outputs into structured PRDs with problem, users, features, and metrics sections.

Community
Intermediate