oc-modularize-ops
Monolith decomposition operator. Decides whether modularization is even the right call (and is willing to say no), captures golden fixtures from REAL data for every boundary as an equivalence oracle, plans the seams + data ownership, and proves zero functionality/data loss by replaying the fixtures. Supports parallel-copy and strangler-fig strategies. Hands the bulk code-move + live cutover to oc-migration-ops (Structural type) and per-module deployment to oc-fleet-ops. Use for /oc-modularize, "break up the monolith", "extract a service from a live system", "split this codebase safely", "golden fixtures", "no functionality loss". For a behaviour-git-diffable repo/package reorg, use oc-migration-ops Structural instead. Trigger when decomposing a LIVE monolith carrying real traffic.
Target: Cloud, operations & security. Automatically collected · unverified.
Excerpt from the author’s documentation
Extracted from a fixed version of SKILL.md in its original language. This is the author’s documentation; installation, compatibility and runtime results have not been verified by this site.
Read the original English text
Topics in the source
- Modularize Ops
- /oc-modularize — Command Reference
- Boundary vs oc-migration-ops Structural (read this first)
- Operating model — gated ops phases
- Phase 0 — Assess (/oc-modularize assess) — can say "don't"
- Phase 1 — Characterize (/oc-modularize characterize) — the signature move
- Phase 2 — Plan seams (/oc-modularize plan) — strategy gate
- Phase 3 — Extract (/oc-modularize extract [module])
On first invocation, read references/orchestrator.md and follow its welcome protocol. Take a monolith — a codebase, a container, or a large deployment — and decompose it into modules or services without losing functionality or data. The signature commitment of this skill is not "it splits cleanly" but "the split is provably behavior- and data-preserving," verified against real input/output captured at every boundary the split crosses. Anyone can move files. The hard, valuable part — the part this skill owns — is the proof that nothing changed. The second, quieter commitment is that this skill is willing to recommend not doing it. A monolith carrying real traffic with no real coupling pain does not need to become a distributed system, and a premature split trades one well-understood problem for a network tax plus a pile of distributed-systems complexity. Phase 0 is a genuine gate that can return "don't modularize, and here's why." That honesty is the point — it mirrors how oc-migration-ops is willing to say "break this into sequential migrations / don't do this all at once." This is not a code-mover. modularize-ops is the decomposition brain plus the equivalence oracle: it decides w
This is an excerpt. Refer to the complete source and its current requirements.
- Source repository
- asfbay-bit/opchain-skills
- Source file
- plugins/opchain/skills/oc-modularize-ops/SKILL.md
- Fixed revision
- 1c7c7bd69a7d875a5dffb419911c24752ca6c285
Sources and evidence
This record was collected automatically. Its documentation, suitability and runtime behavior have not been manually verified.
Author: asfbay-bit/opchain-skills · original repository metadata. Documentation review: Not reviewed. Last source check: 2026-11-10T17:01:26.950Z.
Categories are inferred from names, descriptions and paths. They do not establish compatibility.
License and attribution
Apache-2.0. Third-party content and copyright remain with their authors. Refer to the original license and terms.
Original license ↗Synchronization, copying and user-reported success do not mark a resource as runtime-tested.
Limitations and notes
- Collecting metadata does not mean this site has installed, adapted, runtime-tested or security-reviewed the resource.