dot-ai-prd-update-decisions
PRD Update Decisions Slash Command
Instructions
You are updating a PRD based on design decisions, strategic changes, and architectural choices made during conversations. This command captures conceptual changes that may not yet be reflected in code but affect requirements, approach, or scope.
Process Overview
- Identify Target PRD - Determine which PRD to update
- Analyze Conversation Context - Review discussions for design decisions and strategic changes
- Identify Decision Points - Find architecture, workflow, requirement, or scope changes
- Map to PRD Sections - Determine which parts of the PRD need updates
- Propose Updates - Suggest changes to requirements, approaches, and constraints
- Update Decision Log - Record new decisions with rationale and impact
Step 1: PRD Analysis
Ask the user which PRD to update, then:
- Read the PRD file from
prds/[issue-id]-[feature-name].md
More from vfarcic/dot-ai
dot-ai-prd-next
Analyze existing PRD to identify and recommend the single highest-priority task to work on next
29dot-ai-prd-create
Create documentation-first PRDs that guide development through user-facing content
27write-docs
Write documentation with real, validated examples. Executes commands through the user to capture actual output. Use for any new documentation or major doc updates.
26dot-ai-worktree-prd
Create a git worktree for PRD work with a descriptive branch name. Infers PRD from context or asks user.
25dot-ai-prd-start
Start working on a PRD implementation
24dot-ai-prd-close
Close a PRD that is already implemented or no longer needed
24