shadow-modernize
Skill1 starsChanged yesterdayMITView on GitHub
Technical Due Diligence & Legacy Modernization. Use when auditing inherited/legacy systems, performing business-rule archaeology, scoring multi-dimensional risk vectors, or comparing Strangler Fig Refactor vs Full Rewrite TCO including coexistence costs.
In this repository51 other files it gives its agents.
- antislop-codeSkill
- antislop-copywritingSkill
- antislop-humanSkill
- antislop-layoutmobileSkill
- antislopSkill
- antislop-uiSkill
- context7Skill
- handoffSkill
- shadow-accessibilitySkill
- shadow-apiSkill
- shadow-architectSkill
- shadow-authSkill
- shadow-bootstrapSkill
- shadow-browserSkill
- shadow-cacheSkill
- shadow-compatSkill
- shadow-concurrencySkill
- shadow-dataSkill
- shadow-dbSkill
- shadow-debugSkill
- shadow-designSkill
- shadow-discoverySkill
- shadow-docSkill
- shadow-domainSkill
- shadow-eaSkill
- shadow-evalSkill
- shadow-finopsSkill
- shadow-gitSkill
- shadow-grcSkill
- shadow-handoverSkill
- shadow-integrateSkill
- shadow-maintainSkill
- shadow-mobileSkill
- shadow-monarchSkill
- shadow-observeSkill
- shadow-opsSkill
- shadow-perfSkill
- shadow-planSkill
- shadow-pmoSkill
- shadow-presalesSkill
- shadow-privacySkill
- shadow-qualitySkill
- shadow-realtimeSkill
- shadow-refactorSkill
- shadow-releaseSkill
- shadow-resilienceSkill
- shadow-searchSkill
- shadow-secSkill
- shadow-supplychainSkill
- shadow-testSkill
- shadow-uatSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Use this skill whenever the Monarch invokes /shadow-modernize, audits an inherited/legacy codebase or vendor system, performs M&A/handover …
- Very specific: line 23
Before proposing migration cuts, cross-reference database triggers/constraints/stored procedures, API validators, batch cron jobs, and …
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
/shadow-modernize — Technical Due Diligence & Migration Intelligence
Use this skill whenever the Monarch invokes /shadow-modernize, audits an inherited/legacy codebase or vendor system, performs M&A/handover technical due diligence, or evaluates Strangler Fig Refactor vs Rewrite modernization economics.
Integrates with shadow-monarch/reference/CONSULTING-INTELLIGENCE-CORE.md and deep methodologies:
methodologies/TECHNICAL-FORENSICS-AND-MIGRATION-ECONOMICS.md— 8-Area Technical Due Diligence, Multi-Dimensional Risk Vectors with Evidence Confidence, Business-Rule Archaeology, and Migration Economics (coexistence & transition cost).playbooks/DUE-DILIGENCE-AND-CUTOVER-TEMPLATES.md— System Archaeology Report, Technical Risk Register, Migration Dependency Map, Modernization Business Case, Cutover Plan, and Rollback Playbook.
1. Execution Contract (Never Produce Opaque Single Tech-Debt Scores)
- Read-Only Forensics by Default: Inspect repositories, schemas, dependency lockfiles, CI/CD, and operational telemetry read-only, recording
SHA-256evidence digests and explicit access limitations (e.g., no prod telemetry or DB access). - Multi-Dimensional Risk Vector (Not One Black-Box Score):
- Score 8 dimensions separately (
code_dependencies,architecture_coupling,data_integrity,operations_slo,security_supply_chain,business_criticality) with configurable weights and explicitevidence_confidence(HIGH/MEDIUM/LOW). - Critical Rule: Absence of automated tests does NOT automatically mandate a
FULL_REWRITE. A stable core system carrying complex undocumented business rules and high downtime cost is frequently safer to preserve via Characterization Tests + Strangler Fig / Branch by Abstraction.
- Score 8 dimensions separately (
- Business-Rule Archaeology:
- Before proposing migration cuts, cross-reference database triggers/constraints/stored procedures, API validators, batch cron jobs, and historical incident workarounds to surface hidden domain invariants.
- Migration Economics (Refactor vs Rewrite TCO):
- Model
build_transition_cost + dual_run_coexistence_cost + data_reconciliation_cost + risk_adjusted_delay_costacross 3–5 years forSTRANGLER_FIG_REFACTOR,PHASED_MODULARIZATION,ENCAPSULATE_RETAIN, andFULL_REWRITE.
- Model
2. Deterministic Forensics & Economics Engine
python "shadow-modernize/scripts/modernize_forensics_engine.py" --self-test
python "shadow-modernize/scripts/modernize_forensics_engine.py" --scan-repo path/to/legacy_repo
python "shadow-modernize/scripts/modernize_forensics_engine.py" --evaluate-options path/to/system_profile.jsonDoes it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

