Generates structured Product Requirements Documents from requirements or conversation context.
npx skills add https://github.com/asarchami/dotfiles --skill to-prd-asarchami
Please help me install this Agent Skill. Skill: to-prd Source: https://github.com/asarchami/dotfiles/tree/main/dot_claude/skills/to-prd Command: npx skills add https://github.com/asarchami/dotfiles --skill to-prd-asarchami
High-intent search queries and answers about installing and using this skill.
Provide your feature idea or conversation context and the Skill interviews you one question at a time, starting with foundational topics. It then produces a structured PRD covering user stories, acceptance criteria, testing, edge cases, and open questions.
This framework uses 12 dimensions: stakeholder, problem statement, user stories, acceptance criteria, module design, testing strategy, non-functional requirements, edge cases, out of scope, priority, dependencies, and open questions.
The Skill interviews you only about the specific dimensions that need updating in impacted sections, rather than re-interviewing the entire document. It can also explore the codebase to answer questions itself when possible.
Deep module design means encapsulating significant complexity behind a narrow, stable interface with few exported symbols. The Skill distinguishes deep modules from shallow ones and thin binaries when sketching the technical architecture.
A full 12-dimension PRD may be excessive for trivial changes, quick prototypes, or spike experiments where speed matters more than documentation. Use it when requirements need stakeholder alignment and testable acceptance criteria.
openyakConsolidate user research into themes, prioritized findings, and roadmap recommendations.
TimothyNguyen04Generate engineering tickets from PRDs with acceptance criteria and estimates.
csackriderAnalyze feature specs against codebase constraints and categorize grounding issues by severity.
KeimoshiGenerates a one-page product spec or PRD as a styled HTML artifact.
