From product-design
Use when organizing PRDs, tracking requirements, managing product specs, updating PRD status, archiving completed docs, or setting up PRD structure. Auto-applies naming conventions and lifecycle management.
npx claudepluginhub jpoutrin/product-forge --plugin product-designThis skill uses the workspace's default tool permissions.
This skill automatically activates when working with Product Requirements Documents (PRDs) or Feature Requirements Documents (FRDs). It ensures proper lifecycle management, organization, and tracking.
Creates structured PRDs via 4-file persistent planning (notes, task-plan, prd, tech-md). Activates on explicit PRD, product requirements document, or 产品需求文档 mentions.
Creates and manages PRDs in agents/prd.json with user stories, acceptance criteria, priorities, progress tracking, and git branch naming for feature planning across schema, backend, and UI.
Generates Chinese PRD documents (full, brief, or one-page) via guided interviews, templates, validation, and AI-agent optimizations. Saves to docs/prd dirs.
Share bugs, ideas, or general feedback.
This skill automatically activates when working with Product Requirements Documents (PRDs) or Feature Requirements Documents (FRDs). It ensures proper lifecycle management, organization, and tracking.
When this skill activates, Claude will automatically:
Apply PRD Naming Conventions
<product-name>-prd.md<feature-name>-frd.md<feature-name>-simple-frd.md<prd-name>-tasks.mdMaintain Directory Structure
product-docs/
├── prds/
│ ├── active/ # Currently being implemented
│ │ ├── product-prds/ # Full product PRDs
│ │ └── feature-prds/ # Feature-specific PRDs
│ ├── review/ # Under review/approval
│ ├── approved/ # Approved, awaiting implementation
│ └── archive/ # Completed/deprecated
├── personas/ # User personas
├── positioning/ # Product positioning docs
└── tasks/ # Generated task lists
Enforce Status Lifecycle
Include Required Metadata
---
status: DRAFT
version: 1.0
created: YYYY-MM-DD
last_updated: YYYY-MM-DD
author:
approved_by:
approved_date:
task_file: ./tasks/<name>-tasks.md
---
When creating or updating PRDs:
In the PRD, add Implementation Tracking section:
## Implementation Tracking
Task List: ./tasks/<filename>-tasks.md
Generated: YYYY-MM-DD
Status: See task file for current progress
In task files, reference source PRD:
Source PRD: ../prds/active/<filename>.md
Generated: YYYY-MM-DD
Total Tasks: X
Completed: 0
Before marking any PRD as APPROVED, verify:
Archive PRDs when:
Add archive metadata:
archive_date: YYYY-MM-DD
archive_reason: Implementation complete
final_task_completion: 100%
implementation_duration: X days