skills.rest
jeremysball
jeremysballCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

prd-update-decisions

Updates PRD documents with design decisions and strategic changes captured from conversations.

Updated Nov 7, 2024
Search Tags:#documentation#requirements#product management#update#prd#decision log#scope management
One-click install
npx skills add https://github.com/jeremysball/dotfiles --skill prd-update-decisions-jeremysball
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: prd-update-decisions
Source: https://github.com/jeremysball/dotfiles/tree/main/.pi/skills-archive/prd-update-decisions
Command: npx skills add https://github.com/jeremysball/dotfiles --skill prd-update-decisions-jeremysball

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Design decisions made during conversations often never make it into the PRD, leaving requirements, scope, and architecture sections stale and misaligned with the team's actual direction. ## Core Features & Use Cases - Decision Detection: Scans conversation context for workflow changes, architecture choices, requirement modifications, and scope adjustments. - Structured Decision Logging: Records each decision with date, rationale, impact, code impact, and owner in the PRD's decision log. - PRD Section Updates: Modifies requirements, implementation phases, risks, dependencies, and flags outdated code examples for verification. - Use Case: After a planning discussion where the team decides to defer a feature and switch frameworks, run this command to update the target PRD's scope, architecture, and decision log in one pass. ## Quick Start Ask the assistant to update the PRD for your feature based on the design decisions made in this conversation.

Frequently Asked Questions about prd-update-decisions

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I update a PRD based on conversation decisions?▼

Specify which PRD to update, then the skill reads the file from prds/[issue-id]-[feature-name].md, scans the conversation for design decisions, and proposes updates to requirements, scope, and the decision log.

What types of design decisions does PRD updating capture?▼

It captures technical architecture choices, user experience workflow changes, requirement additions or removals, scope adjustments like deferred features, and implementation strategy changes such as phasing or priority shifts.

Where should PRD files be located for this to work?▼

PRDs must be stored as Markdown files following the naming convention prds/[issue-id]-[feature-name].md so the skill can locate and read the correct document for updating.

Does updating a PRD also update code examples in the document?▼

It identifies code snippets affected by interface, API, or workflow changes and updates or flags them for manual verification, but it does not execute or test the examples itself.

What information is recorded for each decision in the log?▼

Each decision entry records what was decided, the date, the rationale, the impact on requirements and scope, which code examples are affected, and who made or approved the decision.

Related Skills

Explore More Product & Management Skills→
supermalangsupermalang

discovery

Clarify product requirements and generate a structured PRD.

Community
Advanced
mol4mol4
1

bmad-correct-course

Analyze sprint changes and generate a Sprint Change Proposal with implementation handoff.

Community
Advanced
richkuorichkuo
45

prd-questions

Scan PRD files for open questions and update document structure with confirmed answers.

Community
Advanced
foomakersfoomakers
6

pair-capability-record-decision

Record technical decisions as ADRs or ADLs and update adoption files.

Official
Advanced