From prd-manager
This skill should be used when the project contains a "docs/prds/" directory or when the user mentions "update the PRD", "check PRD status", "PRD progress", "track implementation progress", "which PRDs does this affect", "feature requirements", or "update implementation status". Tracks PRD status during feature development, updates implementation progress, and ensures PRDs stay in sync with development work. Also triggers when plan generation, implementation work, or feature completion relates to an existing PRD.
How this skill is triggered — by the user, by Claude, or both
Slash command
/prd-manager:prd-trackerThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Track Product Requirements Documents during feature development. When a `docs/prds/` folder exists in the project, maintain awareness of existing PRDs and keep their implementation status current as development progresses.
Track Product Requirements Documents during feature development. When a docs/prds/ folder exists in the project, maintain awareness of existing PRDs and keep their implementation status current as development progresses.
docs/prds/INDEX.md to understand existing PRDs and their statuses.approved or in-progress — these are active features.When working on code changes, check if the current work relates to an existing PRD by comparing:
If a connection is detected:
/prd-update to apply changes. Invoke automatically for routine updates (status transitions, implementation table updates). Prompt the user before changing requirements or acceptance criteria.When a plan is created for work that maps to an existing PRD:
in-progress if currently approved.updated date in frontmatter.When implementation work related to a PRD is complete:
implemented.Before making changes that could affect multiple features:
approved, in-progress, or implemented.For the PRD document template and format details, consult ${CLAUDE_PLUGIN_ROOT}/skills/prd-tracker/references/prd-template.md.
This plugin provides three commands for explicit PRD management (see ${CLAUDE_PLUGIN_ROOT}/commands/ for full definitions):
/prd — Create a new PRD interactively/prd-list — List all PRDs and statuses/prd-update — Update an existing PRDUse these commands when the user explicitly requests PRD operations. Use this skill's automatic behavior for passive tracking during development.
npx claudepluginhub benbentwo/benbentwos-claude-marketplace --plugin prd-managerManages PRD lifecycle: applies naming conventions, maintains directory structure, enforces status transitions, links PRDs to tasks, runs quality checks, and automates archiving.
Generates a PRD from the current conversation context and codebase understanding, then publishes it to the project's issue tracker (GitHub, GitLab, or local) after user confirmation.
Audits PRD blueprints against implementation evidence in archives, features directories, and codebase. Classifies phases as Complete/Partial/Not Started and guides disposition decisions like archive, add/remove scope, defer, or continue.