菜单
Guide the agent in modifying the plugin's code, templates, or skills to address learnings and gaps found in UAT/semantic validation. Use when: "update the plugin", "fix parsing bug", "modify translation rule", "develop the plugin", "self-correct code translator based on learning".
用 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.
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.
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".
| name | anti-legacy:develop-plugin |
| description | Guide the agent in modifying the plugin's code, templates, or skills to address learnings and gaps found in UAT/semantic validation. Use when: "update the plugin", "fix parsing bug", "modify translation rule", "develop the plugin", "self-correct code translator based on learning". |
This skill guides the agent in modifying the anti-legacy plugin itself — its code, templates, and skills — to address learnings and gaps surfaced in UAT verdicts, semantic validation findings, or production modernization runs.
Identify which plugin component requires modification:
wicked-estate (indexed by survey),
not a local parser. There is no graph_builder.py. Structural gaps in the graph
are wicked-estate concerns; surface them via the engine, not by editing a parser.scripts/wicked_estate.py (the integration helper — binary resolution,
index/query/blast_radius/stats/cross_graph, and the
resolve_symbol_id/annotate/read_semantics/by_requirement annotation path).skills/extraction/SKILL.md (the adaptive ring-expansion crawl recipe that
replaces the old graph-translator enrich flow).scripts/coverage.py (the resolved-or-flagged metric + behavior-bearing
denominator) and the coverage.behavior_kinds / crawl.* keys in config.json.scripts/graph_normalizer.py (drafts the requirements scaffold from the
annotated graph; unchanged in WF1, no longer the code-graph parser).skills/swarm/SKILL.md (developer swarm prompt guidelines)skills/test-strategy/SKILL.md or scripts/test_runner.pyskills/setup/references/anti_patterns.md or skills/blueprint/references/nfrs.mdBefore writing code fixes, add a test case that captures the bug or gap:
tests/test_wicked_estate.py.tests/test_coverage.py.tests/test_demo_pipeline.py or write a dedicated test file under tests/.Modify the target files in the plugin codebase. Maintain documentation integrity and preserve unrelated docstrings or comments.
Run the specific test and then the full test suite to guarantee compile and runtime integrity:
# Run the specific test file
python3 -m unittest tests/test_my_fix.py -v
# Run the full test suite
python3 -m unittest discover -s tests -v
Halt and correct if any test fails.
Commit the fix to the git repository:
git add scripts/ skills/ templates/ tests/
git commit -m "plugin: fixed {bug_desc} based on {finding_source} finding {finding_id}"