dot-ai-prd-update-decisions
Skill336 starsChanged 10 months agoMITView on GitHub
Update PRD based on design decisions and strategic changes made during conversations
In this repository33 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- docs/CLAUDE.mdCLAUDE.md
- dot-ai-changelog-fragmentSkill
- dot-ai-generate-cicdSkill
- dot-ai-generate-dockerfileSkill
- dot-ai-impact_analysisSkill
- dot-ai-manageKnowledgeSkill
- dot-ai-manageOrgDataSkill
- dot-ai-operateSkill
- dot-ai-prd-closeSkill
- dot-ai-prd-createSkill
- dot-ai-prd-doneSkill
- dot-ai-prd-fullSkill
- dot-ai-prd-nextSkill
- dot-ai-prds-getSkill
- dot-ai-prd-startSkill
- dot-ai-prd-update-progressSkill
- dot-ai-process-feature-requestSkill
- dot-ai-projectSetupSkill
- dot-ai-query-dot-aiSkill
- dot-ai-querySkill
- dot-ai-recommendSkill
- dot-ai-remediateSkill
- dot-ai-request-dot-ai-featureSkill
- dot-aiSkill
- dot-ai-tag-releaseSkill
- dot-ai-usersSkill
- dot-ai-versionSkill
- dot-ai-worktree-prdSkill
- dot-ai-write-docsSkill
- infographic-generatorSkill
- publish-mock-serverSkill
- write-docsSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
17 rules. About 0 are common, 16 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈16
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 24
Ask the user which PRD to update, then:
- Very specific: line 25
Read the PRD file from prds/[issue-id]-[feature-name].md
- Distinctive: line 34
Look for conversation elements that suggest strategic changes:
- Distinctive: line 63
Date: When the decision was made
- Distinctive: line 71
Update the appropriate PRD sections:
- Distinctive: line 74
Add new resolved decisions with date and rationale
- Distinctive: line 76
Update decision impact on requirements and scope
- Distinctive: line 80
Update non-functional requirements if performance/quality criteria changed
- Distinctive: line 84
Update phases if sequencing or priorities changed
- Distinctive: line 90
Interface Changes: Update examples when function signatures, parameter types, or return values change
- Distinctive: line 92
Workflow Updates: Update process examples when user interaction patterns or step sequences change
- Distinctive: line 96
Create new tasks: when decisions introduce work not covered by existing tasks (e.g., a new integration, migration step, or validation …
- Distinctive: line 97
Add new milestones: when decisions significantly change project scope or phasing (e.g., a new phase for a deferred feature, or an …
- Distinctive: line 98
Update existing tasks: when decisions change what a task requires or how it should be implemented
- Distinctive: line 100
Reorder priorities: when decisions shift what should be delivered first
- Distinctive: line 103
Add new risks introduced by design decisions
- Distinctive: line 104
Update mitigation strategies if approach changed
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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 - Understand current requirements, approach, and constraints
- Identify areas most likely to be affected by design decisions
Step 2: Conversation Analysis
Review the conversation context for decision-making patterns:
Design Decision Indicators
Look for conversation elements that suggest strategic changes:
- Workflow changes: "Let's simplify this to..." "What if we instead..."
- Architecture decisions: "I think we should use..." "The better approach would be..."
- Requirement modifications: "Actually, we don't need..." "We should also include..."
- Scope adjustments: "Let's defer this..." "This is more complex than we thought..."
- User experience pivots: "Users would prefer..." "This workflow makes more sense..."
Specific Decision Types
- Technical Architecture: Framework choices, design patterns, data structures
- User Experience: Workflow changes, interface decisions, interaction models
- Requirements: New requirements, modified requirements, removed requirements
- Scope Management: Features added, deferred, or eliminated
- Implementation Strategy: Phasing changes, priority adjustments, approach modifications
Step 3: Decision Impact Assessment
For each identified decision, assess:
Impact Categories
- Requirements Impact: What requirements need to be added, modified, or removed?
- Scope Impact: Does this expand or contract the project scope?
- Timeline Impact: Does this affect project phases or delivery dates?
- Architecture Impact: Does this change technical constraints or approaches?
- Code Example Impact: Which examples, interfaces, or snippets become outdated?
- Risk Impact: Does this introduce new risks or mitigate existing ones?
Decision Documentation Format
For each decision, record:
- Decision: What was decided
- Date: When the decision was made
- Rationale: Why this approach was chosen
- Impact: How this affects the PRD requirements, scope, or approach
- Code Impact: Which code examples, interfaces, or snippets need updating
- Owner: Who made or approved the decision
Step 4: PRD Updates
Update the appropriate PRD sections:
Decision Log Updates
- Add new resolved decisions with date and rationale
- Mark open questions as resolved if decisions were made
- Update decision impact on requirements and scope
Requirements Updates
- Modify functional requirements based on design changes
- Update non-functional requirements if performance/quality criteria changed
- Adjust success criteria if measurements or targets changed
Implementation Approach Updates
- Update phases if sequencing or priorities changed
- Modify architecture decisions if technical approach evolved
- Adjust scope management if features were added, deferred, or removed
Code Example Validation and Updates
- Identify Outdated Examples: Scan PRD for code snippets that may be affected by design decisions
- Interface Changes: Update examples when function signatures, parameter types, or return values change
- API Modifications: Revise examples when method names, class structures, or data formats evolve
- Workflow Updates: Update process examples when user interaction patterns or step sequences change
- Mark for Verification: Flag code examples that need manual testing to ensure they still work
Task and Milestone Updates
- Create new tasks when decisions introduce work not covered by existing tasks (e.g., a new integration, migration step, or validation requirement)
- Add new milestones when decisions significantly change project scope or phasing (e.g., a new phase for a deferred feature, or an additional delivery checkpoint)
- Update existing tasks when decisions change what a task requires or how it should be implemented
- Remove or defer tasks that are no longer relevant due to scope changes or eliminated requirements
- Reorder priorities when decisions shift what should be delivered first
Risk and Dependency Updates
- Add new risks introduced by design decisions
- Update mitigation strategies if approach changed
- Modify dependencies if architectural changes affect integrations
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

