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

prd-update-decisions

Analyze conversation context to update PRD sections and decision logs.

Updated Aug 27, 2026
Search Tags:#decision making#documentation#requirements#product management#strategy#prd
One-click install
npx skills add https://github.com/jeremysball/alfred --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/alfred/tree/main/skills/prd-update-decisions
Command: npx skills add https://github.com/jeremysball/alfred --skill prd-update-decisions-jeremysball

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps keep Product Requirement Documents (PRDs) accurate and up-to-date by systematically incorporating design decisions and strategic changes made during project conversations.

Core Features & Use Cases

  • Decision Capture: Identifies and logs key design decisions made during discussions.
  • PRD Section Mapping: Determines which parts of a PRD need modification based on new decisions.
  • Update Proposal: Suggests specific changes to requirements, approaches, and constraints within the PRD.
  • Use Case: After a meeting where the team decides to simplify a user workflow and defer a specific feature, this Skill can analyze the conversation, identify these changes, and propose updates to the relevant sections of the PRD, including the decision log and scope management.

Quick Start

Use the prd-update-decisions skill to update the PRD based on the latest conversation about the user authentication module.

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 context?▼

To update a PRD, this skill analyzes conversation context for design decisions and strategic changes, mapping them to relevant PRD sections to propose updates for requirements, approaches, and constraints while maintaining a decision log.

What is the best way to document design decisions in product management?▼

Documenting design decisions involves identifying strategic changes during project discussions and systematically capturing them in a decision log within the PRD to maintain accurate product requirements.

How do I map scope changes to requirements and constraints?▼

Mapping scope changes involves analyzing conversation context to identify technical architecture or user experience shifts, then proposing specific updates to the relevant requirements and constraints sections in your PRD.

Can I use this to track implementation strategy changes?▼

Yes, you can track implementation strategy changes. The skill addresses modifications in technical architecture, user experience, and implementation strategy by proposing targeted updates to your product requirement documents.

Does this skill automatically generate product requirements?▼

No, it does not automatically generate requirements from scratch. It updates existing Product Requirement Documents by proposing modifications to current requirements, approaches, and constraints based on newly identified design decisions.

What are the limitations of using prd-update-decisions?▼

The skill is limited to analyzing provided conversation context for decision making. It requires existing PRD references to map updates and cannot independently initiate product strategy or invent undocumented technical architecture changes.

Related Skills

Explore More Product & Management Skills→
rnaarlarnaarla

to-prd

Generate a PRD from conversation context and publish it to the issue tracker.

Community
Advanced
vfarcicvfarcic
2

dot-ai-prd-update-decisions

Updates PRDs by integrating design decisions and strategic changes from discussions.

Community
Intermediate
jayteealaojayteealao

documentation-sync

Synchronize version numbers across project files and documentation references.

Community
Advanced
MarcoAntoliniMarcoAntolini
1

to-prd

Convert conversation context into a Product Requirements Document and integrate it into an issue tracker.

Community
Advanced