Loading...
Loading...
Found 322 Skills
Generate comprehensive Product Requirements Documents (PRD) from idea validation files. Use when users ask to "create a PRD", "generate product requirements", "write a PRD", or want to turn validated ideas into actionable product specs. Works with idea.md and validate.md files from the idea-validator skill.
The user will invoke this skill to help them write a PRD (Product Requirement Document).
Expand a problem statement into a Product Requirements Document (PRD). Use when the user has a PROBLEM.md and wants to create a fuller PRD.md with technical approach, dependencies, affected systems, and open questions. Also use when the user says "/prd", "create a PRD", "expand to PRD", or "product requirements document".
Generate comprehensive product requirements documents. Use when starting a new feature or product initiative and need structured documentation.
Analyzes PRD documents, concept briefs, or feature specs and creates structured implementation plans with visual kanban tracking. Breaks requirements into epics, stories, and tasks with dependencies and estimates. Outputs to `.claude/` folder for integration with project-harness and other skills. Generates PROJECT.md for shared project context.
Create Product Requirements Documents (PRD) following SDD methodology - Layer 2 artifact defining product features and user needs
Creates a new Product Requirements Document (PRD) with auto-numbered filenames in the project's PRD directory. Gathers business context, defines the problem, and produces a structured PRD.
Guide for authoring comprehensive PRDs with parallel planning support. Use for drafting technical specifications, defining requirements, and synthesizing planner outputs. Use proactively when creating PRDs, architecture designs, or implementation plans. Examples: - user: "Draft a PRD for user auth" → create PRD with purpose, requirements, and scenarios - user: "Analyze these PRD requirements" → verify SHALL/MUST usage and scenario structure - user: "Synthesize planner outputs" → merge the strongest parts of multiple generated PRDs - user: "Create a PRD template" → setup standard sections and placeholder content
Create a Product Requirements Document (PRD) for your MVP. Use when the user wants to define product requirements, create a PRD, or says "help me write requirements", "create PRD", or "define my product".
PRD 초안을 작성하고 형식을 검증한 뒤 GitHub PR 제출을 안내한다. "PRD 작성", "PRD 검증", "Day 6", "6일차", "PR 제출", "prd submit" 요청에 사용.
Create documentation-first PRDs that guide development through user-facing content
Prompt for creating Product Requirements Documents (PRDs) for new features, based on an Epic.