peintangos/req-update
.claude/skills/req-update/SKILL.md
Analyze the impact of requirements changes/additions and report update proposals for all documents. Only a summary is returned to the main context.
documentation
Updated Apr 17, 2026
$ install --global
skillsauthnpx skillsauth add peintangos/langgraph-tutorial-ts req-updateInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 16, 2026, 4:29 PM7.1s1 file scanned
SKILL.md
- name:
- req-update
- description:
- Analyze the impact of requirements changes/additions and report update proposals for all documents. Only a summary is returned to the main context.
- argument-hint:
- [PRD slug] [Description of changes/additions]
- user-invocable:
- true
- context:
- fork
- allowed-tools:
- Read, Glob, Grep
Requirements Change Impact Analysis
Analyze the impact of requirements changes/additions based on $ARGUMENTS and report update proposals for all documents.
Identify Target PRD
- If a PRD slug is specified in
$ARGUMENTS, use it - If not specified, search for
docs/prds/*/prd.mdusing Glob- If only one is found: use that PRD
- If multiple are found: analyze impact across all PRDs
The target PRD path is docs/prds/prd-{slug}/ below.
1. Read All Documents
Read all of the following:
docs/prds/prd-{slug}/prd.mddocs/prds/prd-{slug}/specifications/spec-*.md(search with Glob)docs/prds/prd-{slug}/progress.mddocs/prds/prd-{slug}/todo.md(if exists)docs/prds/prd-{slug}/dependencies.md(if exists)docs/roadmap.mddocs/architecture.mddocs/ubiquitous/glossary.md(if exists)docs/references/(if exists)
2. Codebase Investigation
Investigate code related to keywords in $ARGUMENTS:
- Search for related code using Grep
- Identify related files using Glob
- List affected implementation files
3. Impact Analysis
Interpret the content of $ARGUMENTS and determine:
- Change type: Requirement change / Requirement addition / Both
- Affected documents: Which of PRD / specifications / progress / roadmap / todo / architecture / dependencies
- Affected code: Whether existing implementation is impacted
4. Draft Update Proposals for Each Document
For each affected document, describe specific update content:
- PRD: Row additions/changes in the functional requirements table, scope updates, etc.
- Specifications: Scenario additions/changes, acceptance criteria updates, implementation step additions/changes
- Progress: New spec row additions, status changes
- Roadmap: Milestone content updates, dependency changes
- TODO: Task additions/changes/deletions
- Architecture: Data model changes, etc. (when applicable)
- Dependencies: Specification dependency relationship changes
Update proposals should clearly state "what existing text to change to what" or "what to append."
5. Report Output
Output in the following structured format. This becomes the summary returned to the main context.
## Requirements Update Impact Analysis Report
### Change Summary
- Type: Requirement Change / Requirement Addition
- Content: [Summary]
### Impact Scope Summary
| Document | Impact | Change Summary |
|----------|--------|----------------|
| PRD | Changed / Added / None | [Summary] |
| Specification | ... | ... |
| Progress | ... | ... |
| Roadmap | ... | ... |
| TODO | ... | ... |
| Architecture | ... | ... |
| Dependencies | ... | ... |
### Code Impact
- [file path]: [Impact summary]
(If unimplemented: "No relevant code")
### Update Proposals for Each Document
#### PRD (`docs/prds/prd-{slug}/prd.md`)
[Specific update content. What existing text changes to what, or content to append]
#### Specification (`docs/prds/prd-{slug}/specifications/spec-NNN-slug.md`)
[Specific update content]
...(listed for each affected document)
### TODO Impact
- [Tasks to add/change/delete]
### Notes
- [Points to note during updates, consistency considerations, etc.]
Notes
- Don't create update proposals based on speculation; cite existing document text accurately before presenting change proposals
- For documents with no impact, explicitly state "No impact" rather than forcing update proposals
- Update proposals are just proposals; they are applied after user approval in the main context
- This skill only updates documents. No source code implementation or changes
Related Skills
peintangos/test
testing
VerifiedTrustedCommunity
Run tests and return a summary. Test logs are contained within the forked context; only the summary is returned to the main context.
SKILL.mdUpdated Apr 17, 2026
peintangos/test-guidelines
testing
VerifiedTrustedCommunity
Review testing strategy and guidelines
SKILL.mdUpdated Apr 17, 2026
peintangos/spec-create
testing
VerifiedTrustedCommunity
Create a new feature specification and update progress.md and roadmap.md
SKILL.mdUpdated Apr 17, 2026
peintangos/setup-ralph-matsuo
documentation
VerifiedTrustedCommunity
Interactively adapt the Ralph Matsuo template to the current repository by filling project docs, rules, roadmap, and ralph.toml in one setup pass
SKILL.mdUpdated Apr 17, 2026