dsivov/change-request-analysis
.claude/skills/change-request-analysis/SKILL.md
Use when the Manager is creating, evaluating, or scoping change requests. Activates when writing CRs, assessing feature requests, estimating effort, analyzing impact, or deciding whether to approve a proposed change.
testing
Updated Apr 16, 2026
$ install --global
skillsauthnpx skillsauth add dsivov/ai_development_team change-request-analysisInstall 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, 2:51 PM4.6s1 file scanned
SKILL.md
- name:
- change-request-analysis
- description:
- Use when the Manager is creating, evaluating, or scoping change requests. Activates when writing CRs, assessing feature requests, estimating effort, analyzing impact, or deciding whether to approve a proposed change.
- version:
- 1.0.0
Change Request Analysis Expertise
When This Applies
Apply this guidance when:
- Creating a new Change Request (CR)
- Evaluating the feasibility of a proposed change
- Estimating scope and effort
- Assessing risk and impact of changes
CR Quality Checklist
Every Change Request should include:
- Clear Problem Statement — What problem does this solve? Why now?
- Specific Requirements — Measurable, testable acceptance criteria
- Scope Boundaries — What is explicitly out of scope
- Impact Assessment — Which components, APIs, or data are affected
- Priority Justification — Why this priority level
Scope Estimation
Sizing Guide
| Scope | Description | Typical Tasks | Typical Duration | |-------|-------------|---------------|------------------| | Small | Single component change, no new APIs | 1-2 tasks | 1-2 sessions | | Medium | Multiple components, possible new API | 3-5 tasks | 2-4 sessions | | Large | System-wide change, new architecture | 6+ tasks | 5+ sessions |
Scope Red Flags
Watch for CRs that should be broken down further:
- Touches more than 3 project directories
- Requires changes to both frontend and backend
- Needs database schema changes alongside feature work
- Has more than 5 distinct requirements
- Affects authentication or authorization flows
Impact Analysis
Before finalizing a CR, assess:
- Breaking Changes — Will this break existing functionality or APIs?
- Data Impact — Are database migrations needed? Is data at risk?
- Dependency Impact — Will other in-progress CRs be affected?
- Test Impact — Do existing tests need updating?
- Infrastructure Impact — Are deployment or config changes needed?
CR Workflow
- Draft the CR with all required fields
- Set priority based on impact and urgency
- Assign to Architect for technical design
- Track through:
open→in_progress→completed→closed - Don't create implementation tasks until Architect has designed the solution
Related Skills
dsivov/test-engineering
development
VerifiedTrustedCommunity
Use when the Integrator is writing unit tests, e2e tests, designing test strategies, improving test coverage, creating test fixtures, or mocking dependencies. Activates for any testing-related work including TDD, test refactoring, or test debugging.
SKILL.mdUpdated Apr 16, 2026
dsivov/task-decomposition
development
VerifiedTrustedCommunity
Use when the Architect is breaking down change requests into implementable tasks, defining acceptance criteria, estimating task size, mapping dependencies, or creating technical sub-tasks for Developer and Integrator.
SKILL.mdUpdated Apr 16, 2026
dsivov/system-design
development
VerifiedTrustedCommunity
Use when the Architect is designing system architecture, choosing technology stacks, defining data models, designing APIs, making scalability decisions, or updating ARCHITECTURE.md. Activates for any architecture design, technology evaluation, or system structure discussion.
SKILL.mdUpdated Apr 16, 2026
dsivov/stakeholder-communication
documentation
VerifiedTrustedCommunity
Use when the Manager is writing status updates, daily reports, queue messages to team members, escalation notices, or cross-role coordination messages. Activates when composing any team communication, reports, or documentation updates.
SKILL.mdUpdated Apr 16, 2026