Schematic
blader/schematic
Reverse engineer a detailed product and technical specification document from a git branch's implementation.
Update PRD based on design decisions and strategic changes made during conversations
Install Prd Update Decisions
$ npx skills add vfarcic/dot-agent-deck --skill prd-update-decisions -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install vfarcic/dot-agent-deck prd-update-decisions --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/vfarcic/dot-agent-deck.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/prd-update-decisions .claude/skills/prd-update-decisions && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "prd-update-decisions" agent skill from https://github.com/vfarcic/dot-agent-deck/tree/main/.claude/skills/prd-update-decisions into .claude/skills/prd-update-decisions/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prd-update-decisions", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/vfarcic/dot-agent-deck/tree/main/.claude/skills/prd-update-decisionsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add vfarcic/dot-agent-deck --skill prd-update-decisions -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install vfarcic/dot-agent-deck prd-update-decisions --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vfarcic/dot-agent-deck.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/prd-update-decisions .agents/skills/prd-update-decisions && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "prd-update-decisions" agent skill from https://github.com/vfarcic/dot-agent-deck/tree/main/.claude/skills/prd-update-decisions into .agents/skills/prd-update-decisions/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prd-update-decisions", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add vfarcic/dot-agent-deck --skill prd-update-decisions -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install vfarcic/dot-agent-deck prd-update-decisions --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vfarcic/dot-agent-deck.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/prd-update-decisions .cursor/skills/prd-update-decisions && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "prd-update-decisions" agent skill from https://github.com/vfarcic/dot-agent-deck/tree/main/.claude/skills/prd-update-decisions into .cursor/skills/prd-update-decisions/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prd-update-decisions", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/vfarcic/dot-agent-deck.git --path .claude/skills/prd-update-decisions--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add vfarcic/dot-agent-deck --skill prd-update-decisions -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install vfarcic/dot-agent-deck prd-update-decisions --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vfarcic/dot-agent-deck.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/prd-update-decisions .gemini/skills/prd-update-decisions && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "prd-update-decisions" agent skill from https://github.com/vfarcic/dot-agent-deck/tree/main/.claude/skills/prd-update-decisions into .gemini/skills/prd-update-decisions/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prd-update-decisions", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install vfarcic/dot-agent-deck prd-update-decisionsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add vfarcic/dot-agent-deck --skill prd-update-decisions -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/vfarcic/dot-agent-deck.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/prd-update-decisions .github/skills/prd-update-decisions && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "prd-update-decisions" agent skill from https://github.com/vfarcic/dot-agent-deck/tree/main/.claude/skills/prd-update-decisions into .github/skills/prd-update-decisions/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prd-update-decisions", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add vfarcic/dot-agent-deck --skill prd-update-decisions -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install vfarcic/dot-agent-deck prd-update-decisions --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vfarcic/dot-agent-deck.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/prd-update-decisions .opencode/skills/prd-update-decisions && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "prd-update-decisions" agent skill from https://github.com/vfarcic/dot-agent-deck/tree/main/.claude/skills/prd-update-decisions into .opencode/skills/prd-update-decisions/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prd-update-decisions", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
prd-update-decisions- GitHub stars
- 109
- Token cost
- ~1.7k tokens
- SKILL.md length
- 886 words
- Files
- 1
- Skills in repo
- 23
- Repo updated
- First seen
- Licence
- MIT
At a glance
Update PRD based on design decisions and strategic changes made during conversations
- Works in 4 steps: PRD Analysis → Conversation Analysis → Decision Impact Assessment → …
- Tasks that involve PRD writing
- SKILL.md covers Instructions, Process Overview, Step 1: PRD Analysis and Step 2: Conversation Analysis, plus 2 more sections
- Calls bash
What it does
Prd Update Decisions is an agent skill from vfarcic/dot-agent-deck. Update PRD based on design decisions and strategic changes made during conversations
Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Product & Project Management, covering PRD writing and Architecture decision records. The repository describes itself as: A rich terminal dashboard for monitoring and controlling multiple AI coding agent sessions. The licence is MIT.
When your agent uses it
- Tasks that involve PRD writing
- Tasks that involve Architecture decision records
Example prompts
- “/prd-update-decisions”
Workflow steps
4 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 9cc3e60. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
bash
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Prd Update Decisions loads about 1.7k tokens when it runs. Until then it costs about 26 tokens; SKILL.md has 886 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from vfarcic/dot-agent-deck at commit 9cc3e60, republished under its MIT licence (© vfarcic). 886 words, ~1,747 tokens.
Download SKILL.mdSave it as
.claude/skills/prd-update-decisions/SKILL.md (or your agent's skills folder).- name
- prd-update-decisions
- description
- Update PRD based on design decisions and strategic changes made during conversations
- user-invocable
- true
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.
Where the PRD lives. Since issue #1591 a new PRD is its GitHub issue — the body is the PRD, the comments are its record — and an older PRD keeps its prds/<n>-*.md file. bash .claude/skills/prd-start/prd-source.sh <n> says which, and ../prd-start/issue-prd.md is how to read and write the issue case. For an issue PRD, recording a decision needs no commit.
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 locate it with bash .claude/skills/prd-start/prd-source.sh [issue-id]:
SOURCE=file: read the PRD file it names (FILE=prds/[issue-id]-[feature-name].md)SOURCE=issue: read the issue body and its collaborator comments, as../prd-start/issue-prd.mdshowsSOURCE=none: there is no PRD to update — say why (REASON=) and suggest/prd-create [issue-id]- 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
Show full SKILL.md (409 more words)Show less
Step 4: PRD Updates
Update the appropriate PRD sections.
For a file PRD (SOURCE=file), edit the file as below; the change is committed with the branch's work.
For an issue PRD (SOURCE=issue), a decision is written in two places, in this order, following ../prd-start/issue-prd.md:
- The record, as a comment — one
### PRD decision — YYYY-MM-DDcomment per decision, carrying the full Decision Documentation Format above. Comments are append-only, so two agents recording decisions at once cannot overwrite each other. - The plan, in the body — add the decision's one-line summary, linking its comment, to
## Decisions, and change the sections it changes (requirements, scope, milestones, risks) as below. Fetch the body immediately before editing it and change only those sections ("Editing the body").
Nothing is committed for an issue PRD.
Decision Log Updates
- Add new resolved decisions with date and rationale (for an issue PRD: the comment, plus its one-line summary in the body's
## Decisions) - 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
© vfarcic, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .claude/skills/prd-update-decisions of vfarcic/dot-agent-deck.
Open the folder on GitHubat commit 9cc3e60
Compare with similar skills
Prd Update Decisions next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Prd Update Decisions this skillvfarcic/dot-agent-deck | 109 | — | ~1.7k | Automated safety check: Pass | MIT | |
| Schematicblader/schematic | 241 | — | ~2.2k | Automated safety check: Pass | MIT | |
| Shep Workstreamsshep-ai/shep | 264 | — | ~2.5k | Automated safety check: Pass | MIT | |
| Write Update Tidb Docspingcap/docs | 616 | — | ~2.3k | Automated safety check: Pass | Custom licence | |
| App Spec Packagerinstructa/agent-skills | 139 | — | ~1.5k | Automated safety check: Pass | None | |
| Bmad Helpaj-geddes/claude-code-bmad-skills | 488 | — | ~1.7k | Automated safety check: Notes | Custom licence |
Similar skills
Shep Workstreams
shep-ai/shep
A skill your agent uses when a large body of work (a version milestone, an epic, a roadmap, a set of PRDs/design docs) needs to be broken into parallel workstreams and executed with the shep CLI.
Write Update Tidb Docs
pingcap/docs
Write new TiDB documentation or update existing TiDB documentation from code changes, PRs, issues, design docs, product specs, rough drafts, existing docs, or short feature descriptions.
App Spec Packager
instructa/agent-skills
A skill your agent uses when the user wants to turn an application, product, startup idea, SaaS, mobile app, web app, API, AI product, or internal tool into a production-ready Markdown specification…
Bmad Help
aj-geddes/claude-code-bmad-skills
Orchestration spine and "what do I do next?" router for the BMAD Planning & Orchestrator plugin.
Bmad Init
aj-geddes/claude-code-bmad-skills
Initialize a BMAD planning workspace: pick a scale-adaptive TRACK (Quick Flow / BMad Method / Enterprise) interactively, then scaffold the output folder, a config file, an empty decision-log.md, and…
More from vfarcic/dot-agent-deck
All 23 skills in this repoDispatch Shape
vfarcic/dot-agent-deck
Choose the shape of a unit you are about to dispatch in this repo — one agent (--single) or a team (--orchestration '<name') — from divisibility criteria instead of asking, and report the shape you…
Docs Screenshots Review
vfarcic/dot-agent-deck
Check that a change to the user-facing docs covers both clients (the TUI and the desktop app) unless the feature exists in only one, and decide whether it needs a new or updated screenshot, then…
Dot AI Request Dot AI Feature
vfarcic/dot-agent-deck
Generate a feature request prompt for another dot-ai project.
PR Create
vfarcic/dot-agent-deck
Take committed work from a branch to a verified pull request — push, open the PR, settle CI and the automated review, answer and resolve every finding, and hand off.
Publish Docs
vfarcic/dot-agent-deck
Publish the docs site to GHCR with a main-<sha tag and bump site/helm/values.yaml so Argo CD picks it up — without cutting a SemVer release.
Run Dot Agent Deck
vfarcic/dot-agent-deck
Run, build, smoke-test, and screenshot the dot-agent-deck binary against an isolated sandbox.
Related
Categories
Questions about Prd Update Decisions
What does Prd Update Decisions do?
Update PRD based on design decisions and strategic changes made during conversations. Prd Update Decisions is an agent skill from vfarcic/dot-agent-deck.
When should I use Prd Update Decisions?
Prd Update Decisions fits situations like: tasks that involve PRD writing; tasks that involve Architecture decision records.
How do I install Prd Update Decisions in Claude Code?
Run `npx skills add vfarcic/dot-agent-deck --skill prd-update-decisions -a claude-code`. Or copy the skill folder (.claude/skills/prd-update-decisions in vfarcic/dot-agent-deck) into .claude/skills/prd-update-decisions in your project. Claude Code loads it when a task matches its description.
How do I install Prd Update Decisions in Codex?
Run `npx skills add vfarcic/dot-agent-deck --skill prd-update-decisions -a codex`. Or copy the skill folder (.claude/skills/prd-update-decisions in vfarcic/dot-agent-deck) into .agents/skills/prd-update-decisions in your project. Codex loads it when a task matches its description.
Can I use Prd Update Decisions in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add vfarcic/dot-agent-deck --skill prd-update-decisions -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/prd-update-decisions, .gemini/skills/prd-update-decisions, .github/skills/prd-update-decisions and .opencode/skills/prd-update-decisions in your project.
What does Prd Update Decisions need to run?
Going by SKILL.md and its folder, Prd Update Decisions needs the command-line tools its instructions call (bash).
Does Prd Update Decisions access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Prd Update Decisions safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Prd Update Decisions use?
Prd Update Decisions is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Prd Update Decisions use?
About 1.7k tokens (SKILL.md is roughly 7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Prd Update Decisions?
Skills that share tags, products or a category with Prd Update Decisions: Schematic (blader/schematic, 241 stars), Shep Workstreams (shep-ai/shep, 264 stars), Write Update Tidb Docs (pingcap/docs, 616 stars) and App Spec Packager (instructa/agent-skills, 139 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Prd Update Decisions?
vfarcic (a GitHub user) maintains it in vfarcic/dot-agent-deck, which has 109 GitHub stars. The repository holds 23 skills in this directory. The repository was last updated on October 10, 2026.
Source: vfarcic/dot-agent-deck on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.