菜单
The anti-legacy pipeline internals SME, and the home of the shared antilegacy_core Python library. Use when: understanding or operating the pipeline core, diagnosing a core module (estate seam, requirements-graph builder, coverage, manifest state machine, validator), checking pipeline readiness, or extending antilegacy_core.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Validates the requirements graph against the wicked-estate code graph before the blueprint phase. Checks every requirement's legacy field resolves to a real program node in the graph (not a JCL step), finds uncaptured behavior-bearing nodes with business logic that need requirements, and flags duplicate program references. Blocks if errors are found; warns and requires human review if only gaps remain. Run after extraction/graph-translator, before blueprint. Use when: "validate requirements graph", "audit the graph", "check graph accuracy", "are we missing any programs", "graph audit before dev", "validate before blueprint".
Apply structural lenses to the legacy code graph to identify entry points, domain boundaries, shared data coupling, operational modes (batch vs online), and risk hotspots. Queries the wicked-estate code graph via the helper (never raw SQLite, never legacy_graph.json). Produces an analysis report. Use when: "analyze the legacy code", "identify entry points", "find domain boundaries", "what are the hotspots", "classify the programs".
Pre-build threat modeler — the adversarial half of the Phase Execution Protocol (PEP, AGENTS.md §10). Given a phase plan and its threat surface, generates a structured threat list BEFORE the producer runs so the producer can address each threat in its output rather than discovering the gap post-build. CRITICAL threats block the phase from advancing until the producer acknowledges them (fix or documented waiver). MEDIUM/MINOR are advisory. Distinct from anti-legacy:adversarial-review (which reviews rendered output AFTER production) — the antagonist attacks the plan BEFORE production, while it is still cheap to change. Use when: any phase producer is about to run; "antagonist check"; "threat model this phase"; "what could go wrong"; PEP step 3 in orchestrate.
Map the Requirements Graph to a target state architecture blueprint. Defines the modern package structure, API surface (REST/gRPC), database schemas, class boundaries, and repository patterns for the target stack. Produces blueprint.json + blueprint.md. Use when: "design the target architecture", "create the blueprint", "map requirements to target stack", "design the Spring Boot structure", "what does the modern version look like".
Render the full stakeholder DELIVERABLES package once the requirements graph is ready — product requirements (PRD), architecture diagrams, detailed test strategy, functional test scripts, end-to-end migration plan, and the living risk / decisions / evidence logs — into .anti-legacy/deliverables/, then compile an index. Register-only; does not advance the pipeline. Use when: "produce the deliverables", "generate all the deliverables", "the deliverables package", "PRD + diagrams + plan + risk/decision logs".
Package and deploy the modernized application to the configured deployment target. Supports GCP Cloud Run, AWS ECS/Fargate, Azure AKS, and generic Kubernetes. Generates Dockerfile, CI/CD pipeline config, and deployment manifests. Requires GATE_4_UAT to be cleared. Use when: "deploy the app", "generate the Dockerfile", "create CI/CD config", "package for Cloud Run", "generate Kubernetes manifests", "deployment".
| name | anti-legacy:expert |
| description | The anti-legacy pipeline internals SME, and the home of the shared antilegacy_core Python library. Use when: understanding or operating the pipeline core, diagnosing a core module (estate seam, requirements-graph builder, coverage, manifest state machine, validator), checking pipeline readiness, or extending antilegacy_core. |
This skill is the subject-matter reference for the anti-legacy pipeline's shared
Python core, and it physically hosts that core at scripts/antilegacy_core/. The
library ships with the portable bundle because the skills standard delivers a
skill's entire directory subtree (symlink or --copy).
antilegacy_core)All cross-cutting pipeline logic lives in one namespaced, collision-proof package
(no more bare import coverage shadowing stdlib / pytest-cov):
| Module | Responsibility |
|---|---|
estate | The wicked-estate engine seam — resolve binary, index/query/source/annotate the code graph. |
coverage | Resolved-or-flagged coverage over the graph + annotations.jsonl. |
extract | Business-rule extraction from source slices. |
vocabulary | Glossary / domain-term mining + curation. |
domain_graph | The requirements-graph builder (§I5). |
normalizer | Code-graph → draft requirements scaffold. |
comparator | Graph diff / round-trip comparison. |
manifest | The pipeline state machine — phases, gates, audit. |
validator | The build / semantic / UAT evidence verifier. |
planner | Task-list planning helpers. |
preflight() (in __init__) | Host-agnostic readiness check (engine, deps, workspace). |
The pipeline JSON schemas ship as package data under antilegacy_core/schemas/
and are read via importlib.resources — one source of truth, versioned with the
code.
Skills never import the core directly. They dispatch through the workspace seam:
python3 .anti-legacy/run.py <stem> <args...>
run.py resolves <stem> to a library module and runs
python -m antilegacy_core.<stem>, with the package on PYTHONPATH. Workspace
state (config, annotations, graphs) is anchored on the current working directory —
never on the package's __file__ — so the core behaves identically whether the
bundle was installed as a plugin (whole repo) or via the skills standard (flat
per-skill dirs).
python3 .anti-legacy/run.py preflight
Reports the engine (wicked-estate ≥ 0.5.1), Python deps, and workspace state, with the exact remediation for anything missing. Fails fast — never silently degrades.
Add a module under scripts/antilegacy_core/. If it imports another core module,
it belongs here (the cross-importing core stays together). Single-consumer leaf
logic belongs in its owning phase skill's scripts/, not here.