Where are the generated PRD files stored?

All PRD files are automatically saved to the 'docs/reference/pm/versions/' directory, ensuring a consistent and version-controlled documentation structure.

Does this skill include technical implementation details?

No, this skill follows a strict rule of focusing on 'what' to build and 'why', specifically excluding implementation details to keep the focus on product requirements.

Can I generate PRDs in languages other than English?

Yes, the skill checks the 'aico.json' file in your project root for a 'language' field. If specified, it will output the PRD in that language.

What is required before the skill generates a PRD?

According to the 'Iron Law', you must have validated requirements, including documented user pain points, defined success metrics, and an explicitly approved scope.

AI Product Manager PRD Writer

Name: AI Product Manager PRD Writer
Author: yellinzero

byyellinzero

Collaboration Tools

Generates comprehensive Product Requirements Documents (PRDs) focusing on goals, user stories, and success criteria without implementation details.

About

This skill transforms Claude into a strategic product manager, facilitating the creation of structured PRDs that bridge the gap between initial ideas and technical execution. It enforces a rigorous standard of documenting functional requirements, defining clear success metrics, and establishing non-goals to prevent scope creep. By automating the boilerplate and ensuring all necessary components—like user pain points and market context—are addressed, it helps development teams maintain a clear source of truth for every feature or initiative within the docs/reference/pm/ directory.

Key Features

Automated documentation versioning saved to project-specific directories
Strict scope management through explicit definition of Goals and Non-Goals
Multi-language support via project-level configuration (aico.json)
Standardized PRD template generation with standardized FR-XXX requirement formatting
Requirement validation checks to ensure metrics and pain points are defined
0 GitHub stars

Use Cases

Executing version planning and roadmap alignment using the /pm.plan command
Starting a new product or major feature that requires formal requirement documentation
Defining measurable success criteria and user stories before starting technical implementation

About

Key Features

Automated documentation versioning saved to project-specific directories
Strict scope management through explicit definition of Goals and Non-Goals
Multi-language support via project-level configuration (aico.json)
Standardized PRD template generation with standardized FR-XXX requirement formatting
Requirement validation checks to ensure metrics and pain points are defined
0 GitHub stars

Use Cases

Executing version planning and roadmap alignment using the /pm.plan command
Starting a new product or major feature that requires formal requirement documentation
Defining measurable success criteria and user stories before starting technical implementation