mikeparcewski
@mikeparcewski
Public Skills
wicked-garden-platform-gh-cli
by mikeparcewski
Use when you need gh CLI patterns beyond the basics — debugging failed workflow runs, bulk PR operations, release automation, or repo health checks. Provides composable gh invocations for power users. NOT for simple git commands (use Bash) or GitLab (use the glab-cli skill). Use when: "debug the failed workflow run", "bulk PR management", "release automation with gh", "gh operations", or any former /wicked-garden:platform:gh invocation (operations: workflows prs releases repo).
wicked-garden-platform-github-actions
by mikeparcewski
Write secure, optimized GitHub Actions workflows. Security-first approach with performance optimization. Use when: "GitHub Actions", "CI/CD pipeline", "workflow YAML", "deploy pipeline", "automate deployment", "debug workflow", "Actions security", "generate a workflow", "optimize this workflow", "troubleshoot the failing workflow", or any former /wicked-garden:platform:actions invocation.
wicked-garden-platform
by mikeparcewski
Platform domain skill: security scanning, incident triage, infrastructure review, and distributed-trace analysis. Routes to one of four inline actions (security incident infra traces) backed by the rubrics in refs/, and links out to the domain's sub-skills (audit, compliance, health, observability, CI/CD tooling, peer-health) and workers. Use when: "security scan", "vulnerability assessment", "scan this PR for vulnerabilities", "run the security scanners", "incident", "production is down", "triage this alert", "root cause this error", "review our Terraform", "IaC review", "infrastructure review", "cloud cost review", "trace analysis", "why is this endpoint slow", "latency investigation", or any former /wicked-garden:platform:{security incident infra traces} invocation.
wicked-garden-engineering-backend
by mikeparcewski
Backend engineering specialist for APIs, databases, server-side patterns, data modeling, scalability, and integrations. Use when: "design an API", "database schema", "how to handle auth", "backend performance", "REST endpoint", "query optimization", "server-side architecture"
wicked-garden-engineering-docs
by mikeparcewski
Use when generating documentation from code, auditing documentation coverage for gaps, or detecting code-doc drift after a refactor. Covers generate (API docs, READMEs), audit (coverage metrics, undocumented exports), and sync (stale docs detection) in one skill. NOT for architecture documentation (use the architecture skill) or product requirements (use product/requirements-analysis).
wicked-garden-engineering-architecture
by mikeparcewski
Complete solution architecture design with patterns, decisions, and diagrams. Define overall system structure, technology choices, and architectural trade-offs. Use when: "design the architecture", "what's the overall structure", "architecture patterns", "technology stack", "system architecture"
wicked-garden-engineering-large-scale-migration
by mikeparcewski
How to execute a LARGE MECHANICAL change across any codebase with LEVERAGE instead of an agent-grind or hand-edits — a cross-cutting migration, refactor, rename, dialect/framework/DB port, library adoption, or bulk transform. The map→transform→gate pattern: a deterministic transform driven by a source-of-truth map, proven by a differential-equivalence gate. Use when the work is "migrate all X to Y", "rename Z everywhere", "port to a new DB/dialect/framework", "adopt a library across N files", "refactor this pattern in M places", or any change touching dozens-to-thousands of sites. Language/DB/framework-agnostic — the thinking, not a specific tool.
wicked-garden-engineering-unit-test-quality
by mikeparcewski
Language- and framework-neutral guard against useless unit tests — the kind that pass forever, never catch regressions, and inflate coverage without protecting behavior. Provides two complementary thought-experiment filters (execution + behavior), a pre-write self-check, a taxonomy of seven recurring anti-patterns (tautological, assertion-free, implementation mirror, framework retest, constant verification, sleep-coupled, exception-swallowing), and a one-line decision rule per pattern. Use when: writing or reviewing a unit test, auditing a suite with high coverage but low confidence, or pairing a regression test with a bug fix.
wicked-garden-engineering-system-design
by mikeparcewski
Use when decomposing a system into components with clear boundaries, module organization, and interface contracts — the "how do we slice this?" question at design time. NOT for reviewing an existing system's health (use the architecture skill or engineering:arch).
wicked-garden-engineering-debugging
by mikeparcewski
Systematic debugging and root cause analysis for investigating errors, diagnosing complex issues, and performance profiling. Use when: "debug this error", "why is this failing", "root cause analysis", "fix this bug", "investigate crash", "stack trace", "not working"
wicked-garden-engineering-patch
by mikeparcewski
Language-agnostic code generation and change propagation. Use this skill when adding fields to entities, renaming symbols across files, or propagating changes that affect multiple files. Use when: "add field", "add a field to this entity", "rename everywhere", "rename this field across the codebase", "remove this field and all its usages", "propagate change", "generate migration", "update all references", "apply saved patches", "show what a change would affect" (patch-plan propagation preview), "create a new language generator for wicked-patch". Replaces the former /wicked-garden:engineering: {add-field,rename,remove,apply,patch-plan,new-generator} commands. This is the CODE MUTATION counterpart to wicked-garden-search (which is read-only).
wicked-garden-engineering-migration-engineer
by mikeparcewski
Schema migrations, data backfills, deprecation paths, rollback plans, and the expand-contract pattern for changing live production systems without breaking them. Use when: schema migration, data backfill, splitting/merging tables or services, renaming fields or primary keys in production, changing data types or tightening constraints, sunsetting API versions, breaking changes to event payloads, or "how do we ship this breaking change safely?". NOT for large mechanical codebase changes with no production data in flight — use the engineering/large-scale-migration knowledge module (map→transform→gate) for those.
wicked-garden-engineering-solution-architect
by mikeparcewski
Design end-to-end solutions with appropriate patterns, technology choices, and architectural trade-offs — ADRs, system diagrams, cross-cutting concerns. Use when: system design, greenfield architecture, structural trade-offs, technology/pattern selection, "design the solution architecture", writing Architecture Decision Records, or when the engineering domain skill's arch action or the architecture knowledge module escalates genuinely structural design work.
wicked-garden-engineering-integration
by mikeparcewski
Design API contracts, service boundaries, and integration patterns. Define how components and services communicate and interoperate. Use when: "API design", "service integration", "how do these communicate", "API contract", "integration pattern", "REST API", "GraphQL", "event schema"
wicked-garden-engineering-api-documentarian
by mikeparcewski
Specialize in API documentation — OpenAPI specs, endpoint documentation, request/response examples, error documentation, and authentication docs. Use when: API docs, OpenAPI specs, "document this API/endpoint", generating endpoint reference documentation from code, or when the engineering domain skill's docs action routes an api-type request here.
wicked-garden-engineering-frontend
by mikeparcewski
Frontend engineering specialist for React, CSS, browser APIs, component design, accessibility, and performance. This skill should be used when the user asks about UI implementation, component review, or frontend-specific questions. Use when: "build a React component", "CSS layout issue", "frontend performance", "browser API", "component design", "accessibility check", "responsive design"
wicked-garden-archetype
by mikeparcewski
v11 work-shape archetype runner. When a prompt has been routed to one of the archetypes (triage, explore, specify, decide, ship, review, incident, build, migrate, modernize), this skill is the entry point. It picks the right per-archetype playbook from refs/ and executes the phase shape declared in .claude-plugin/archetypes.json. Use when: a <wg archetype="X"> or <wg archetypes> system-reminder tag appears, an explicit "let's run the X archetype" request, or a direct per-archetype ask — "triage this prompt", "review this PR / artifact", "build this feature", "decide between these options", "explore this problem", "handle this incident", "run this migration", "modernize / port this legacy app", "ship this release", "write acceptance criteria" (invoke with archetype=<name> plus the user's args — see the Direct invocation table).
wicked-garden-classify
by mikeparcewski
v11 LLM-based work-shape classifier. Replaces the regex archetype detector with the model's own reasoning. Reads the user's prompt, picks the right archetype(s) from the catalog, identifies signals (blast_radius, novelty, reversibility, etc.), and persists to SessionState so subsequent turns steer correctly. Use when: the prompt_submit hook emitted a <wg classify-due /> directive, OR explicitly invoked at session start, OR when re-classifying after the user changes scope mid-session.
wicked-garden-ground
by mikeparcewski
Grounding / assumption-check: pull deeper context from the knowledge layer (wicked-estate memory + knowledge) and the bus when uncertain, before acting. Use when: getting mixed signals from the codebase, about to commit to a non-obvious decision, prior decisions might exist for this exact problem, or you want to verify an assumption before action ("am I sure about this?", "have we decided this before?"). Returns relevant memories, knowledge chunks, recent bus events, and linked priors ranked by relevance — not a wall of text. Aliases: grounding, sanity-check, verify-assumption. NOT for: routine "what does this code do" questions (use Read or Grep), broad codebase exploration (use your harness's exploration agent, or search inline), or fetching specific symbols (use the wicked-estate MCP SearchEntity tool directly).
wicked-garden-prove
by mikeparcewski
Prove a claim by re-deriving it (run + gate) instead of asserting "done" — the one-line re-derivation verb — plus the compile action that emits a self-contained, vault-backed build gate into any repo. Use when: "prove it", "prove tests pass", "prove the build is clean", "re-derive done", "run the produces-gate", "gate this claim", "--with-attestations", "compile", "emit a build gate", "stamp a gate into a repo", "compile a repo-native build gate", "--trigger hook,ci", or any former /wicked-garden:{prove compile} invocation.
wicked-garden-domain
by mikeparcewski
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 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. 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.
wicked-garden-deliberate
by mikeparcewski
Critical thinking framework applied before doing work. Challenges assumptions, reframes problems, identifies hidden opportunities, and validates whether the stated ask is the right ask. A way of approaching work, not a specialist discipline. Use when: challenging assumptions before implementation, reframing a stated problem, asking whether the right thing is being asked at all, "deliberate on this", "deliberate #42" (a GitHub issue number), "critically analyze this request before implementing", --deep (blast-radius analysis), --batch (multiple issues, shared root causes), or any former /wicked-garden:deliberate invocation.
wicked-garden-domain-coverage
by mikeparcewski
Coverage evaluator + pre-build threat model for the domain-extraction workflow (CONTRACT-3 §2). Emits coverage-report.json from the estate store, then adversarially reviews the extracted domain model: hunts missing error paths, ungrounded rules, reason-less drops, cross-cluster smears, and coverage holes. Use when: dispatched as the coverage phase of a domain-extraction workflow run. The phase runs in a git worktree; WICKED_ESTATE_DB points at the live estate store. NOT for mining rules (domain-extractor) or grouping domains (domain-modeler). This worker EMITS coverage evidence AND CRITIQUES the domain model.
wicked-garden-domain-modeler
by mikeparcewski
Domain-graph 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).