evanflow-prd

Synthesize a comprehensive PRD from project context and ADRs into docs/specs.

417|18|Updated Apr 27, 2026

Search Tags:#planning #architecture #documentation #requirements #prd #product-management #stakeholders

Ready to run

npx skills add https://github.com/evanklem/evanflow --skill evanflow-prd

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: evanflow-prd
Source: https://github.com/evanklem/evanflow/tree/main/skills/evanflow-prd
Command: npx skills add https://github.com/evanklem/evanflow --skill evanflow-prd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Synthesize a comprehensive PRD for a big feature using existing project context and explicit ADRs, enabling stakeholders to align before planning.

Core Features & Use Cases

Reads project context from CLAUDE.md, CONTEXT.md, docs/adr/, recent commits, and stakeholder notes.
Identifies major modules and validates architecture to surface a coherent feature scope.
Writes a PRD in a structured format with sections for problem, solution, user stories, architecture, testing strategy, scope, and open questions; optionally suggests creating a GitHub issue after approval.

Quick Start

Provide the project context and ADRs; the skill will generate a PRD draft in docs/specs/.

Frequently Asked Questions about evanflow-prd

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

FAQPage Schema

How do I generate a PRD from existing project context and ADRs?▼

Generate a PRD by reading CLAUDE.md, CONTEXT.md, docs/adr/, recent commits, and stakeholder notes to synthesize a comprehensive product requirements document in docs/specs with sections for problem, solution, user stories, architecture, testing strategy, scope, and open questions.

What should a product requirements document include for aligning stakeholders before a sprint?▼

A PRD for stakeholder alignment should include sections for the problem statement, proposed solution, user stories, architecture validation, testing strategy, defined scope, and open questions to ensure comprehensive pre-sprint planning.

Can I automatically create a GitHub issue from a generated PRD?▼

Yes, after generating the PRD draft and obtaining user approval, the skill can optionally suggest creating a GitHub issue to track the substantial feature directly from the synthesized documentation.

How do I scope substantial features using architecture decisions and stakeholder notes?▼

Scope substantial features by analyzing existing ADRs, recent commits, and stakeholder documents to identify major modules, validate architecture, and surface a coherent feature scope within the generated PRD.

Does this PRD generation approach work without predefined project documentation files?▼

No, this approach relies on reading existing project context files such as CLAUDE.md, CONTEXT.md, and docs/adr/ to synthesize a polished PRD, requiring these inputs to accurately reflect the project's current architectural state.

What is the best way to write structured product specs for pre-sprint planning?▼

The best way to write structured product specs is to synthesize project context and ADRs into a standardized PRD format in docs/specs/, covering problem, solution, user stories, architecture, testing strategy, scope, and open questions.