cy-create-prd

Guide structured brainstorming and research to draft comprehensive PRDs.

1|1|Updated Apr 18, 2026
One-click install
npx skills add https://github.com/rodrigobranas/formacao_ia_arq_t1_4 --skill cy-create-prd-rodrigobranas
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cy-create-prd
Source: https://github.com/rodrigobranas/formacao_ia_arq_t1_4/tree/main/helpdesk_project/.agents/skills/cy-create-prd
Command: npx skills add https://github.com/rodrigobranas/formacao_ia_arq_t1_4 --skill cy-create-prd-rodrigobranas

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Product teams often struggle to align stakeholders and capture complete requirements before drafting a PRD. This skill guides structured brainstorming, research, and decision documentation to produce a high-quality PRD.

Core Features & Use Cases

  • Guided brainstorming across parallel research tracks (codebase context, market context, and user needs) to surface relevant requirements.
  • An interactive question protocol that elicits WHAT, WHY, and WHO to refine scope and success criteria.
  • Automated ADR creation and a complete PRD draft using canonical templates, with an open review loop for stakeholder alignment.

Quick Start

Initiate a PRD session by providing a feature name, then guide me through questions to outline the PRD draft.

Frequently Asked Questions about cy-create-prd

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

FAQPage Schema
How do I create a PRD that aligns stakeholders and captures complete requirements?

You can create a PRD through guided brainstorming across parallel research tracks covering codebase, market context, and user needs. This structured approach surfaces complete requirements and aligns stakeholders before drafting documentation, ensuring comprehensive scope and cross-functional alignment.

What is the best way to document product decisions and requirement traceability?

Documenting product decisions is best achieved by anchoring your PRD on a defined requirement protocol and generating ADR options. Using canonical templates ensures scope and traceability while capturing the WHAT, WHY, and WHO behind each product decision.

How do I brainstorm product requirements across cross-functional teams?

You can brainstorm product requirements by initiating a session with a feature name and guiding teams through an interactive question protocol. This elicits WHAT, WHY, and WHO from cross-functional teams to refine scope, define success criteria, and align market context with user needs.

Can I draft a PRD automatically without missing market context and user needs?

Yes, you can draft a PRD automatically while capturing market context and user needs through parallel research tracks. An open review loop follows the automated draft using canonical templates, ensuring stakeholders validate that all cross-functional input and requirements are included.

Does generating a PRD require existing codebase context before starting?

Generating a PRD does not strictly require existing codebase context beforehand, as the guided brainstorming process researches parallel tracks simultaneously. Providing a feature name to initiate the session allows the protocol to effectively gather codebase, market, and user inputs.