From hone
Generates a structured Product Requirements Document (PRD) from feature descriptions. Analyzes codebase (package.json, configs, README), processes references, asks clarifying questions, saves to .plans/. Use for new feature planning.
How this skill is triggered — by the user, by Claude, or both
Slash command
/hone:prdThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Generate a PRD for the feature described in `$ARGUMENTS`.
Generate a PRD for the feature described in $ARGUMENTS.
Create .plans/ directory if it doesn't exist.
Read and analyze:
package.json (project name, description, dependencies, scripts, devDependencies)src/, lib/, components/, utils/, test/, __tests__/tsconfig.json, Makefile, vitest.config.*, .eslintrc*, next.config.*, vite.config.*, docker-compose.yml, Dockerfile, pyproject.tomlREADME.md for project contextAGENTS.md if it exists (for project conventions and patterns).plans/ for context on ongoing workSummarize findings concisely (languages, frameworks, testing, build tools, project patterns).
If $ARGUMENTS contains file paths (e.g., ./docs/spec.md, src/component.js):
If $ARGUMENTS contains URLs (e.g., https://example.com/api-docs):
If any reference fails to load, note it and ask the user about it.
Ask up to 5 clarifying questions, one at a time. Each question should:
After each question, wait for the user's response. If the user says "done", stop asking and proceed.
When you have enough information (or after 5 questions), proceed to generation.
Write a comprehensive PRD following this exact template:
# PRD: <Feature Name>
## Overview
Brief description of the feature and its purpose.
## Goals
What this feature aims to achieve.
## Non-Goals
What is explicitly out of scope.
## Requirements
### Functional Requirements
- REQ-F-001: <requirement>
- REQ-F-002: <requirement>
### Non-Functional Requirements
- REQ-NF-001: <requirement>
## Technical Considerations
Architecture decisions, integration points, potential challenges.
## Acceptance Criteria
- [ ] Criterion 1
- [ ] Criterion 2
## Out of Scope
Items explicitly not included in this feature.
## Open Questions
Any unresolved questions.
Use the codebase analysis and Q&A answers to make the PRD specific and actionable. Reference existing patterns, frameworks, and conventions from the project.
Slugify the feature name:
Write to .plans/prd-<slug>.md.
Tell the user:
Saved to .plans/prd-<slug>.md
Review and edit the PRD, then run:
/hone:prd-to-tasks .plans/prd-<slug>.md
npx claudepluginhub oskarhane/hone-ai --plugin honeGenerates complete PRDs via guided feature discovery, product context integration, clarifying questions, and optional codebase analysis. Outputs user stories, Gherkin criteria, metrics, and launch plans.
Generates Product Requirement Plans (PRPs) for feature implementation via systematic codebase analysis and external research. Use when requesting PRP, PRD, or detailed implementation plans.
Generates Product Requirements Documents (PRDs) for new features via phased approach: discovery, codebase exploration with agents, clarifying questions. Useful for feature planning or project starts.