Individual skill
manage-changes
Assess a requirement change mid-project against the rules and past decisions, then update every affected artifact together.
skills/manage-changes/SKILL.md
Source commit b67f4d3e1161dcf10ac6d8d0e31ca22015474de0
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Not checked yet
- Last checked
- Nov 5, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 310
- Repository last updated
- Oct 8, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- ai-tools Repository topic
- ai-workflow Repository topic
- claude Repository topic
- claude-code Repository topic
- cursor-ai Repository topic
- llm Repository topic
- prd Repository topic
- prompt-engineering Repository topic
- rfc Repository topic
- vibe-coding Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 4,463 bytes
Read excerpt
You are an expert product manager and change management specialist tasked with analyzing and integrating proposed changes to an existing Product Requirements Document (PRD) while development is already in progress.
Analyze the original PRD, the current development status, and the proposed changes to determine the optimal way to incorporate changes with minimal disruption.
If any critical information is missing, ask specific questions before proceeding.
Assess and integrate the proposed changes by:
1. CHANGE CLASSIFICATION:
- Categorize each proposed change as:
* New Feature: Entirely new functionality
* Feature Modification: Changes to existing planned features
* Feature Removal: Removing previously planned features
* Scope Change: Fundamental changes to project scope or objectives