planning-prd-agent 1.0.0 Immutable snapshotLatest
Pinned to commit 5bd4f168edf7c18a8303cbfde20708ff62aabc4d, captured .
Download 1.0.0 source archive Choose something to compare with View commit on GitHub
More actions and subscriptions
Current package description (not historical)
'MUST BE USED PROACTIVELY when user mentions: planning, PRD, product requirements document, project plan, roadmap, specification, requirements analysis, feature breakdown, technical spec, project estimation, milestone planning, or task decomposition. Use IMMEDIATELY when user says "create a PRD", "plan this feature", "document requirements", "break down this project", "estimate this work", "create a roadmap", "write specifications", or references planning/documentation needs. Expert Technical Project Manager that creates comprehensive PRDs with user stories, acceptance criteria, technical architecture, task breakdowns, and separate task assignment files for sub-agent delegation.'
Install
This version is listed in the verified marketplace awesome-claude-code-plugins (repository ccplugins/awesome-claude-code-plugins). Run these in Claude Code, in order:
- Add the marketplace
/plugin marketplace add ccplugins/awesome-claude-code-plugins - Install the plugin
/plugin install planning-prd-agent@awesome-claude-code-plugins
These commands install the marketplace's current upstream state, not the pinned commit snapshot on this page; the two can differ.
Contents 1
Agent1
-
planning-prd-agent
plugins/planning-prd-agent/agents/planning-prd-agent.mdPermalink
Nothing matches.
Dependencies, compatibility and skill declarations
Recorded dependencies 0
No dependency requirements were recorded from plugin.json or marketplace entries. Only manifest fields saved with the snapshot are shown here; dependency declarations in other files are outside the current collection scope.
Recorded compatibility
No compatibility requirement was recorded for this snapshot from plugin.json or a marketplace entry. Only manifest fields saved with the snapshot are shown here. Declarations in a skill's SKILL.md header are collected separately and, when present, shown on their own under “Skill file declarations”; they never overwrite or fill in this value.