Automatic PRD lifecycle management, organization, and status tracking. Use when working with Product Requirements Documents (PRDs) or Feature Requirements Documents (FRDs) for proper naming, directory structure, and status transitions.
Automatically organizes PRDs/FRDs with proper naming, directory structure, and status lifecycle tracking (DRAFT→REVIEW→APPROVED→ACTIVE→COMPLETE→ARCHIVED). Activates when you create or modify product requirements documents, enforcing metadata standards and linking PRDs to task files for implementation tracking.
/plugin marketplace add jpoutrin/product-forge/plugin install product-design@product-forge-marketplaceThis skill inherits all available tools. When active, it can use any tool Claude has access to.
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
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.