Can it handle complex business logic?

Yes, it incorporates Mermaid flowcharts, state diagrams, and sequence diagrams to map out intricate logic, state transitions, edge cases, and error handling paths.

How does the staged confirmation process work?

The skill uses a three-step method: first aligning on the macro journey map, then confirming individual user stories with their specific logic, and finally requesting explicit user permission before generating the full PRD.

Does it create actual UI designs?

It uses ASCII wireframes to establish layout, hierarchy, and component placement, ensuring visual alignment between stakeholders and developers without needing external design files.

Where are the PRDs stored?

The skill suggests a standard repository structure (e.g., docs/prd/) and maintains a PRD_REGISTRY.md file to track all versions and document links within your project.

Why use a story-driven structure for a PRD?

By treating requirements as self-contained stories, it ensures every feature is tied to a specific user goal and includes all necessary implementation details and acceptance criteria in one place.

PRD Doc Writer & Story Architect

Name: PRD Doc Writer & Story Architect
Author: xiaxingxiaowei1983

byxiaxingxiaowei1983

0•

학습 및 문서화

Collaboratively crafts detailed, story-driven PRDs using ASCII wireframes, Mermaid diagrams, and strict stage-based confirmations.

This skill transforms Claude into a partner-level Product Manager that guides users through a structured three-step process to build comprehensive Product Requirement Documents (PRDs). It emphasizes a story-driven approach where every feature is treated as a self-contained user story, reinforced by visual aids like ASCII wireframes for UI and Mermaid diagrams for business logic. By enforcing strict confirmation gates at the journey mapping, story detailing, and final generation stages, it ensures total alignment between the user's vision and the technical documentation, eliminating ambiguity before development begins.

주요 기능

01Interactive Story-Driven Structure: Organizes requirements into logical user journeys and self-contained story cards.

02Strict Confirmation Gates: Implements a three-step protocol to prevent unauthorized assumptions or hallucinated features.

030 GitHub stars

04Visual Alignment Tools: Generates ASCII wireframes for UI layouts and Mermaid diagrams for process flows and state machines.

05PRD Registry Management: Maintains a documentation index within the project repository for professional version tracking.

06Comprehensive Acceptance Criteria: Defines edge cases, failure paths, and specific business logic for every story.

사용 사례

01UI/UX Layout Planning: Aligning on interface structure and component hierarchy using ASCII wireframes before coding.

02Initial Product Scoping: Brainstorming and defining high-level user journeys and core feature sets for new applications.

03Refining Vague Requirements: Transforming loose ideas into detailed, developer-ready technical specifications.

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add xiaxingxiaowei1983/openclaw yunshu_skillshub-master

For use in Claude.ai and ChatGPT

주요 기능

01Interactive Story-Driven Structure: Organizes requirements into logical user journeys and self-contained story cards.

02Strict Confirmation Gates: Implements a three-step protocol to prevent unauthorized assumptions or hallucinated features.

030 GitHub stars

04Visual Alignment Tools: Generates ASCII wireframes for UI layouts and Mermaid diagrams for process flows and state machines.

05PRD Registry Management: Maintains a documentation index within the project repository for professional version tracking.

06Comprehensive Acceptance Criteria: Defines edge cases, failure paths, and specific business logic for every story.

사용 사례

01UI/UX Layout Planning: Aligning on interface structure and component hierarchy using ASCII wireframes before coding.

02Initial Product Scoping: Brainstorming and defining high-level user journeys and core feature sets for new applications.

03Refining Vague Requirements: Transforming loose ideas into detailed, developer-ready technical specifications.