Verified:GitHub

prd

Generate product requirements documents with user stories and acceptance criteria.

Updated May 22, 2026

Search Tags:#acceptance criteria #feature planning #user stories #prd #product requirements #stakeholder alignment #risk analysis

Ready to run

npx skills add https://github.com/Nweremizu/ekklesia --skill prd-nweremizu

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: prd
Source: https://github.com/Nweremizu/ekklesia/tree/main/.junie/skills/prd
Command: npx skills add https://github.com/Nweremizu/ekklesia --skill prd-nweremizu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns vague product ideas into clear, production-ready PRDs so teams can align on scope, requirements, and delivery expectations before implementation starts.

Core Features & Use Cases

Discovery-first workflow that asks clarifying questions before drafting.
Structured PRDs with executive summary, user experience, technical specs, risks, and rollout phases.
Works well for new features, AI product concepts, and cross-functional planning.
Example: Use it to document a search feature, define success metrics, capture acceptance criteria, and outline rollout risks.

Quick Start

Use this skill to interview me about a new product idea and then draft a PRD that follows the required schema.

Frequently Asked Questions about prd

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

FAQPage Schema

How do I turn a vague product idea into a structured PRD?▼

To turn a vague idea into a structured product requirements document, use a discovery-first workflow that asks clarifying questions before drafting user stories, acceptance criteria, and rollout phases.

What should a product requirements document include for AI-powered features?▼

A product requirements document for AI-powered features should include executive summaries, technical architecture, measurable specifications, risk analysis, and explicit testing guidance to ensure stakeholder alignment.

How do you write user stories and acceptance criteria for feature planning?▼

Writing user stories and acceptance criteria requires structured discovery to translate ambiguous ideas into measurable specifications, ensuring clear scope definition and aligning cross-functional stakeholders before implementation.

Can I use this for cross-functional planning and scope definition?▼

Yes, you can use this for cross-functional planning and scope definition because it generates production-ready product requirements documents that capture stakeholder alignment, technical specs, and delivery expectations.

What is the best way to document rollout risks and success metrics?▼

The best way to document rollout risks and success metrics is to follow a structured product requirements document schema that explicitly outlines risk analysis, phased rollout expectations, and testing guidance.