From prd-builder
Add a new feature to an existing PRD — creates a feature document or updates the parent in-place
How this skill is triggered — by the user, by Claude, or both
Slash command
/prd-builder:prd-add-featureThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
```text
$ARGUMENTS
You MUST consider the user input before proceeding (if not empty).
Add a new feature to an existing PRD following the hub-and-spoke model. Read the parent PRD to understand current scope, run a scoped discovery for the new feature, then either create a separate feature document or update the parent PRD in-place. Maintain version history and bidirectional linking.
${CLAUDE_PLUGIN_ROOT}/templates/prd-feature-template.md${CLAUDE_PLUGIN_ROOT}/templates/prd-template.md$ARGUMENTS is empty, abort with: "Please provide the parent PRD path and optionally a feature name. Example: /prd-add-feature prd/my-product/prd.md notifications"Ask the user the following questions (batch where possible using AskUserQuestion). Do not proceed until you have substantive answers for at least questions 1–2.
Follow up on vague or incomplete answers. Reference the parent PRD's existing content to ask informed questions (e.g., "The parent PRD lists personas X, Y, Z — which are affected?").
Ask the user which approach to take, with a recommendation:
Recommend separate feature document when:
Recommend in-place update when:
If the user chose a separate document:
${CLAUDE_PLUGIN_ROOT}/templates/prd-feature-template.md.prd/<parent-folder>/prd-<feature-name>.md (kebab-case).## Feature Index section (place it after the Scope & Prioritization section if creating new).
b. Add a row: | <Feature Name> | Draft | [prd-<feature-name>.md](prd-<feature-name>.md) | <one-line summary> |
c. Add a revision history entry: | <next-version> | <today's date> | Added feature document: <feature-name> |
d. Bump the version number (minor increment: v1.0 → v1.1).If the user chose an in-place update:
| <next-version> | <today's date> | Added <feature-name>: <one-line summary> |[Added v<new-version>].[Updated v<new-version>].Tell the user what was created or modified:
/prd-validate <path> to check structural integrity/prd-analyze <path> to check quality/prd-refine <path> to improve the feature document or updated PRDnpx claudepluginhub sinositato/tato-claude-plugins --plugin prd-builderExtends existing PRDs with new requirements via interactive clarification, generates sequential tasks, processes file paths and URLs as context. For iterative feature planning.
Synthesizes a PRD for big features from project context and ADRs. Asks before creating a GitHub issue. Use when scoping a substantial new feature.
Generates complete PRDs via guided feature discovery, product context integration, clarifying questions, and optional codebase analysis. Outputs user stories, Gherkin criteria, metrics, and launch plans.