mikeparcewski/adopt-legacy
skills/adopt-legacy/SKILL.md
Detect and transform legacy beta.3 project markers to v6.0 format (D5, AC-13 c). Handles three markers: missing phase_plan_mode, markdown re-eval addendums in process-plan.md (pre-D2 format), and references to the removed legacy gate-bypass env-var in project files. Safe to run on v6-native projects — no markers detected means no-op. Dry-run by default; --apply to write changes. Use when: upgrading a project from wicked-garden v6.0-beta.3 to v6.0; checking whether a project needs migration; transforming legacy artifacts before running crew:approve on a beta project.
$ install --global
skillsauthnpx skillsauth add mikeparcewski/wicked-garden adopt-legacyInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 19, 2026, 4:06 AM7.5s1 file scanned
SKILL.md
- name:
- adopt-legacy
- description:
- |
- Handles three markers:
- missing phase_plan_mode, markdown re-eval addendums in
- Use when:
- upgrading a project from wicked-garden v6.0-beta.3 to v6.0; checking
- crew:
- approve on a beta project.
Adopt Legacy (beta.3 → v6.0 upgrade)
Inspects a crew project directory for three legacy markers and offers to transform them in-place. All transformations are idempotent — running twice is a no-op if no markers remain.
Detected markers
| Marker | Detection | Transformation |
|--------|-----------|----------------|
| Missing phase_plan_mode | project.json lacks the key | Sets phase_plan_mode = "facilitator" |
| Markdown re-eval addendum | ## Re-evaluation YYYY-MM-DD in process-plan.md | Serialises each block to phases/{phase}/reeval-log.jsonl (best-effort); replaces block with a migration comment |
| Legacy gate-bypass reference | Any .md/.json file contains the removed env-var string | Replaces with a commented removal note |
Usage
# Preview changes (default — no writes)
sh "${CLAUDE_PLUGIN_ROOT}/scripts/_python.sh" \
"${CLAUDE_PLUGIN_ROOT}/scripts/crew/adopt_legacy.py" <project-dir>
# Apply transformations
sh "${CLAUDE_PLUGIN_ROOT}/scripts/_python.sh" \
"${CLAUDE_PLUGIN_ROOT}/scripts/crew/adopt_legacy.py" <project-dir> --apply
Or invoke directly as a crew command:
/wicked-garden:adopt-legacy <project-dir>
Output example
[adopt-legacy] Scanning project: my-feature
[adopt-legacy] Mode: dry-run (pass --apply to write changes)
[adopt-legacy] Detected 3 legacy marker(s)
[adopt-legacy] Transformation 1/3: [dry-run] would set phase_plan_mode = "facilitator" in project.json
[adopt-legacy] Transformation 2/3: [dry-run] would migrate 2 markdown addendum(s) from process-plan.md → phases/unknown/reeval-log.jsonl
[adopt-legacy] Transformation 3/3: [dry-run] would replace legacy gate-bypass reference in status.md
[adopt-legacy] Dry-run complete. Run with --apply to write changes.
When to use
- You see
phase_manager.pycomplaining about missingphase_plan_mode - You have a beta.3 project with prose re-eval addendums in
process-plan.md - Any project file references the removed legacy bypass env-var
Script location
scripts/crew/adopt_legacy.py — stdlib-only, no external dependencies.
Related Skills
mikeparcewski/wicked-garden-engineering-conformance-reviewer
development
VerifiedTrustedCommunity
Pattern-conformance agent-half: evaluates a produced artifact or diff against a set of architectural/design pattern rules from the conformance-rule store (wicked_governance schema). Returns structured findings with rule ID, severity, and rationale — the deterministic half (mechanical rule recall) is done by the guard pipeline; this is the semantic evaluation step. Triggered by: the guard_pipeline `outgov_pattern` check (session-close), or explicitly by an engineering review when WICKED_OUTGOV_RULES_DIR is populated. NOT a replacement for the full `engineering` review skill — focuses only on conformance to stored Pattern rules; architecture and code-quality checks live in the `engineering` skill. Semantic evaluation reuses `wicked-garden-qe-semantic-reviewer` as the designated agent-half evaluator (per garden#983 spec). This skill is the orchestrating wrapper that loads applicable Pattern rules and delegates the per-rule semantic judgment to qe-semantic-reviewer.
8SKILL.mdUpdated Jul 22, 2026
mikeparcewski/wicked-garden-domain
tools
VerifiedTrustedCommunity
The FOUNDATIONAL domain-model capability: extract a codebase's domain — testable business rules (with confidence + provenance), entities, requirements — as a schema-conformant model on the estate graph. The workers annotate the store; wicked-core reads it and builds the requirements graph, coverage-gating fail-closed. Steers three fork workers. A shared substrate, not a modernization tool. The `modernize` archetype DERIVES from it; build / migrate / review / specify / explore consume the SAME domain model — none OWN it. Understanding a codebase's domain is upstream of almost everything else garden does. Use when: "extract the business rules / domain model from this codebase", "build a requirements graph from the code", "what does this system actually require", "reverse-engineer the domain before we build/port/migrate". Works on ANY codebase (modern or legacy) — the value is the domain model, not the porting. NOT the code transform itself (that is the archetype consuming this model). This skill produces the DOMAIN MODEL, not new code.
8SKILL.mdUpdated Jul 15, 2026
mikeparcewski/wicked-garden-domain-modeler
development
VerifiedTrustedCommunity
Domain-graph fork worker for the modernize archetype. Groups the estate's Louvain communities into business domains, attaches each requirement to its cluster (advisory cluster_id provenance), and invokes wicked-core's domain-graph build (which reads the annotated estate store, recomputes coverage fail-closed, and builds the requirements graph) — then validates core's output against the vendored schema. Use when: dispatched by wicked-garden-domain after rule extraction to turn a flat rule set into cluster-keyed domains; "group these into domains", "build the requirements graph", "translate clusters into a domain model". NOT for mining the rules themselves (that is domain-extractor) or threat-modeling (that is domain-coverage).
8SKILL.mdUpdated Jul 15, 2026
mikeparcewski/wicked-garden-domain-extractor
tools
VerifiedTrustedCommunity
Rule-extraction fork worker for the FOUNDATIONAL domain-model capability. Mines testable business rules from a codebase — each with a numeric confidence and a provenance{source, ref, source_kinds} — and annotates them into the estate store so wicked-core can build the domain-model requirements graph (coverage-gated). This is a substrate, not a modernization tool: the `modernize` archetype DERIVES from it, and build / migrate / review / specify / explore can consume the same domain model — none OWN it. Use when: dispatched by wicked-garden-domain to mine the business_rules of a codebase (or a module); "extract the domain rules", "what does this system require", building the requirements half of a domain model. NOT for grouping into domains (that is domain-modeler) or judging coverage (that is domain-coverage — a seat-distinct evaluator).
8SKILL.mdUpdated Jul 15, 2026