- Home
- Skills
- Agents & Orchestration
- Technical Change Impact Review
More screenshots
Works with the AI tools you already use
Technical Change Impact Review
Technical Change Impact Review is a bounded ToolForge Labs workflow.
$8.99
Technical Change Impact Review
Example session with this skill installed
Review the impact of migrating the 'user-profile' service from Postgres to MongoDB based on the attached RFC and the 'profile-api' diff. Focus on data contracts and consumer impact.
- Read your context and instructions
- Compiled the technical change impact
I have reviewed the RFC for the 'user-profile' migration and the current 'profile-api' diff. The review focuses on contract integrity and downstream consumer risk.
Technical Change Impact Review: User-Profile Migration
| Impact Area | Evidence Source | Status | Finding/Gap |
|---|---|---|---|
| Data Contract | profile-api diff | Conflict | Diff shows removal of billing_address field, but RFC states "no schema deletions". |
| Consumers | RFC Section 4.2 | Verified | Identified order-service and auth-gateway as direct consumers via gRPC. |
| Persistence | RFC Section 2.1 | Inference | Assumes MongoDB Atlas handles retry logic; no driver config evidence in diff. |
| Rollback | Not found | GAP | No evidence of a data synchronization or reverse-migration plan. |
| Monitoring | RFC Section 6.0 | Verified | New Datadog dashboard user-prof-mongo-metrics is defined. |
Source Register
RFC-204: Service Migration Strategy (v2.1)PR-452: profile-api schema changesdeps.json: Service dependency map
Reviewer Questions
- Why is
billing_addressbeing dropped in the implementation when the RFC promises backward compatibility? - Where is the rollback script stored? The RFC mentions a "migration tool" but no code exists in the current workspace.
- Has the
order-serviceteam signed off on the gRPC interface change identified in line 44 of the diff?
Next steps
- Reconcile the
billing_addressdiscrepancy between the RFC and the diff. - Document the data rollback strategy for the cutover window.
- Request explicit sign-off from the
order-serviceteam regarding the interface change.
Connects securely to your tools. The creator never sees your data.
What you get
About this skill
Technical Change Impact Review is a bounded ToolForge Labs workflow. Review technical change impact across dependencies, consumers, data/contracts, tests, rollout/rollback, ownership, and unresolved evidence. Works from supplied files, logs, tickets, reports, configuration, or architecture notes. Produces a traceable evidence review with explicit gaps and assumptions without inventing unavailable facts. It works from a full repository or partial evidence such as snippets, logs, configuration, traces, tickets, and architecture notes. The skill preserves existing product and security policy, separates verified facts from assumptions, avoids invented execution claims, and produces concrete repair or review steps with focused deterministic validation or traceable evidence.
How to install
Works the same in every agent - Claude, Cursor, Codex, Copilot and 20+ more.
- 1
Download the ZIP
Free skills download straight away. Paid skills unlock right after purchase.
- 2
Unzip into your skills folder
Every agent reads skills from one folder on your machine. Drop the unzipped folder in there.
- 3
Ask your agent to use it
Restart the agent if it was already running. It picks the skill up automatically - no config needed.
Skills folder by agent
Click the path to copy it. Create the folder if it does not exist yet.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill passes our trust checks below.
Security scanned
Passed our 8-point scan before listing
Fresh listing
Recently published to Agensi
30-day refund
Not a fit? Get your money back
Trust & safety
Security scanned
Verified clean 7 days ago
- Passed all security checks, Safe to install