Create business-focused PRDs via codebase exploration and market research.
npx skills add https://github.com/rhuangabrielsantos/skills --skill cy-create-prd
Please help me install this Agent Skill. Skill: cy-create-prd Source: https://github.com/rhuangabrielsantos/skills/tree/main/skills/cy-create-prd Command: npx skills add https://github.com/rhuangabrielsantos/skills --skill cy-create-prd
New features and product ideas often lack a structured, business-focused Product Requirements Document (PRD) that integrates codebase reality and market context, causing misalignment between product goals and engineering effort. This Skill enforces a repeatable, collaborative process that combines parallel codebase exploration, web research, structured clarifying questions, and documented decisions to produce a complete PRD ready for handoff.
_prd.md into .compozy/tasks/<slug>/, preserving update mode when an existing PRD or _issue.md is present.Create a PRD for "smart search" using any existing _issue.md, include codebase exploration and market research, then present approaches for selection.
High-intent search queries and answers about installing and using this skill.
To create a product requirements document (PRD) with full context, this Skill runs parallel codebase exploration and web research, summarizes findings, and asks structured clarifying questions before generating the final draft. It ensures your PRD aligns product goals with engineering reality by integrating both technical and market data.
Turning an issue file into a canonical PRD involves detecting an existing _issue.md, preserving its update mode, gathering code and market context, running targeted clarifying questions, presenting approaches, and saving the final _prd.md into a designated task directory.
Yes, you can document architectural decisions during PRD creation. The structured brainstorming process presents 2-3 approaches for selection and produces Architecture Decision Records (ADRs) to trace and justify the chosen approach for your new feature.
The clarifying question protocol enforces a one-question-at-a-time multiple-choice format. It collects user approvals at defined gates during product requirements generation, ensuring structured, focused collaboration before finalizing the PRD draft.
No, you do not need an existing issue file to start guided PRD creation. You can initiate a new feature idea directly, derive a slug, and the system will gather the necessary codebase and market context before asking targeted clarifying questions.
The generated PRD and ADR files are saved under the .compozy/tasks/<slug>/ directory. The system automatically derives the slug from your feature name and writes the final _prd.md file there for review and handoff.
rhuangabrielsantosExpand raw feature ideas into research-backed specifications in issue files.
shalevaminEstimate team capacity, select stories, map dependencies, and identify risks for sprint planning.
sameer-thakkarAutomate implementation plan creation through interactive research and iterative development.
ederfmatosTranslate PRD business requirements into technical specifications with ADR documentation.