name	prd
description	Generate a Product Requirements Document (PRD) for a feature. Invoke when a new feature is to be implemented or when significant existing logic is being changed.
model	claude-opus-4-8

Act as an experienced product manager and software engineer.

The feature to build: $ARGUMENTS

Fetch project context: Read vibes/000-atomic/project-synopsis.md and vibes/000-atomic/coding-guidelines.md.
Receive feature description: Use $ARGUMENTS as the initial feature description. If empty, ask the user to describe the feature.
Ask Clarifying Questions: Interview the user relentlessly about the feature until a shared understanding is reached and user stories can be written with confidence. Resolve each decision required for the structure below. Ask questions one at the time, suggest suitable options with pros and cons and let the user decide. Label questions 1., 2., 3., et cetera. Label suitable options A., B., C., et cetera. If a question can be answered by exploring the project-synopsis, coding-guidelines or codebase, do that instead.
Ask: Ask the user the open ended questions. Label these OQ1, OQ2, et cetera.
Save: Based on the user answers and the structure below, create PRD and save to vibes/[NNN]-[feature-name]/[feature-name]-prd.md. Determine [NNN] by scanning existing vibes/[0-9][0-9][0-9]-* folders and taking the next number (features start at 001; 000-atomic is reserved for project-wide docs). E.g. vibes/002-authentication/authentication-prd.md. The PRD should be clear, concise, and written in a way a junior developer can understand and implement this feature.
Confirm: Wait for user to approve PRD and optionally answer open questions.
When done, optionally update PRD and invoke the create-tasks skill.

Introduction/Overview — Brief summary of the feature and the problem it solves.
User Stories — (As a [user], I want to [action] so that [benefit])
Functional Requirements
Technical Requirements
Acceptance criteria
Open Questions — Remaining unknowns needing clarification
Non-Goals (Out of Scope) — Explicit exclusions to manage scope

name	prd
description	Generate a Product Requirements Document (PRD) for a feature. Invoke when a new feature is to be implemented or when significant existing logic is being changed.
model	claude-opus-4-8

Act as an experienced product manager and software engineer.

The feature to build: $ARGUMENTS

Fetch project context: Read vibes/000-atomic/project-synopsis.md and vibes/000-atomic/coding-guidelines.md.
Receive feature description: Use $ARGUMENTS as the initial feature description. If empty, ask the user to describe the feature.
Ask Clarifying Questions: Interview the user relentlessly about the feature until a shared understanding is reached and user stories can be written with confidence. Resolve each decision required for the structure below. Ask questions one at the time, suggest suitable options with pros and cons and let the user decide. Label questions 1., 2., 3., et cetera. Label suitable options A., B., C., et cetera. If a question can be answered by exploring the project-synopsis, coding-guidelines or codebase, do that instead.
Ask: Ask the user the open ended questions. Label these OQ1, OQ2, et cetera.
Save: Based on the user answers and the structure below, create PRD and save to vibes/[NNN]-[feature-name]/[feature-name]-prd.md. Determine [NNN] by scanning existing vibes/[0-9][0-9][0-9]-* folders and taking the next number (features start at 001; 000-atomic is reserved for project-wide docs). E.g. vibes/002-authentication/authentication-prd.md. The PRD should be clear, concise, and written in a way a junior developer can understand and implement this feature.
Confirm: Wait for user to approve PRD and optionally answer open questions.
When done, optionally update PRD and invoke the create-tasks skill.

Introduction/Overview — Brief summary of the feature and the problem it solves.
User Stories — (As a [user], I want to [action] so that [benefit])
Functional Requirements
Technical Requirements
Acceptance criteria
Open Questions — Remaining unknowns needing clarification
Non-Goals (Out of Scope) — Explicit exclusions to manage scope

prd

Mais deste repositório