Synthesize a comprehensive PRD from project context and ADRs into docs/specs.
npx skills add https://github.com/evanklem/evanflow --skill evanflow-prd
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
Synthesize a comprehensive PRD for a big feature using existing project context and explicit ADRs, enabling stakeholders to align before planning.
Provide the project context and ADRs; the skill will generate a PRD draft in docs/specs/.
High-intent search queries and answers about installing and using this skill.
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.
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.
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.
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.
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.
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.
Davie521Synthesize a structured PRD from conversation context and project files.
semicolon-devteamCreate a GitHub Project Sprint Issue with iteration details and goals.
bmsull560Validate architectural coherence across code, tests, and documentation before merge.
ncptuanCreate product requirements documents through structured requirement discovery and user-centered questioning.
