What is the 'Hard-Gate' mentioned in the process?

The Hard-Gate is a safety mechanism that prevents the skill from considering a PRD finished until the user has explicitly reviewed and approved the draft, ensuring no requirements are assumed.

Can I use my own company PRD template?

Yes, the skill is designed to search for a 'templates/prd.md' file in your repository and will use it as the base structure to maintain consistency with your team's standards.

Does this skill write technical implementation code?

No, this skill focuses specifically on the 'what' and 'why' of a feature. It describes the product value and functional requirements without dictating technical implementation details.

How are the acceptance criteria formatted?

The skill generates acceptance criteria in the 'Given/When/Then' format, making them easy to translate into automated tests or manual QA scripts.

Where are the final documents saved?

Approved PRDs are automatically saved to the 'docs/prd/' directory with a descriptive filename and timestamp for easy version control and discovery.

Product Requirements Architect

Name: Product Requirements Architect
Author: 686f6c61

by686f6c61

•

Herramientas de Colaboración

Generates comprehensive Product Requirements Documents (PRDs) with user stories, acceptance criteria, and success metrics through an iterative process.

This skill empowers teams to bridge the gap between product vision and technical execution by creating structured, high-quality PRDs that serve as a single source of truth. It guides users through an iterative questioning process to define the problem space, proposes user-centric solutions, and drafts detailed user stories with Given/When/Then acceptance criteria. By enforcing a mandatory approval gate and integrating with existing project documentation, it ensures that development only begins on validated requirements, significantly reducing scope creep and team misalignment.

Características Principales

01Automatic analysis of existing project docs and issues to ensure architectural consistency.

02Gherkin-style (Given/When/Then) acceptance criteria for clear QA and dev alignment.

0337 GitHub stars

04Mandatory approval workflow to validate requirements before document finalization.

05Step-by-step interactive context gathering to capture product vision and constraints.

06Standardized PRD structure including problem definition, metrics, and risk mitigation.

Casos de Uso

01Refining project scope by defining clear 'Out of Reach' boundaries for new iterations.

02Translating high-level feature ideas into actionable developer specifications.

03Standardizing documentation across a multi-disciplinary team of designers and engineers.

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add 686f6c61/alfred-dev producto

For use in Claude.ai and ChatGPT

Download Skill