mikeparcewski
@mikeparcewski
Public Skills
wicked-garden-draft
by mikeparcewski
The quality floor for DOCUMENT deliverables drafted from a repo — brochures, one-pagers, flyers, pages, decks, memos — design guidance plus one self-check run before "done". Three floors: (1) READABLE — every text/background pair ≥ 4.5:1 (WCAG AA; 3:1 for large text) on COMPOSITED colours, print text ≥ 7pt; (2) SIZED TO THE BRIEF — the RENDERED page count honours the brief's page budget (wrappers are not pages); (3) GROUNDED — every number, URL and claim cites a repo path, mocks visibly labelled, no placeholder ships. Use when: "draft a brochure / one-pager / flyer / product page / deck / memo about <repo>", "print-ready A4 / Letter", "make it two pages", "is this brochure readable / grounded", before declaring a wicked-interactive draft/edit/revision done, or as the skill a governed drafting run (wicked-crew interactive-*) follows. NOT for code documentation (the engineering documentarian) or a running app's accessibility audit (the product a11y action / the qe a11y engineer).
wicked-garden-governed-worker
by mikeparcewski
"The discipline every governed unit follows, by role — creator (fix/build), evaluator (reproduce/verify/judge) or neutral (triage/recon/plan): run the repo's checks in the worktree and paste exit codes, prove any 'pre-existing' claim on the base, regenerate instead of hand-editing, evaluators write only to their output, neutral units never implement, no questions into a headless run, honest counts, no secrets. Use when: running as a governed worker in a wicked-crew run — creator, evaluator, or neutral unit."
wicked-garden-platform-observability
by mikeparcewski
Use when monitoring or diagnosing the wicked-garden plugin ecosystem — health probes, contract assertions, hook traces, error pattern detection, and APM/logging/metrics toolchain discovery. NOT for distributed tracing across services (use the platform domain skill's traces action) or audit evidence (use platform/audit). Use when: "plugin health", "health probe", "hook didn't fire", "hook traces", "contract assertions", "validate script outputs", "what monitoring tools are installed", "toolchain discovery", or any former /wicked-garden:platform:{plugin-health assert toolchain} invocation.
scaffold
by mikeparcewski
Component scaffolding toolkit for creating skills, context:fork worker skills, and hooks within the unified wicked-garden plugin. Generates complete, valid structures that pass validation out-of-the-box. Use when creating new domain components, setting up boilerplate, or ensuring proper structure from the start.
wicked-garden-core
by mikeparcewski
Core utility surface for the wicked-garden plugin: help/overview, first-run setup + codebase onboarding, the wicked-* peer installer, selective state reset, the where-am-i path manifest, and structured issue filing. Use when: "wicked-garden help", "show wicked-garden commands", "what can wicked-garden do", "set up wicked-garden", "setup", "--reconfigure", "onboard this codebase", "install wicked tools", "add peers", "install layers", "reset wicked-garden", "clear state", "--list-projects", "where am I", "path manifest", "report issue", "file a bug", "--list-unfiled", or any former /wicked-garden:{help setup install reset where-am-i report-issue} invocation.
release
by mikeparcewski
Release management and versioning toolkit for the wicked-garden plugin. Automates changelog generation, semantic versioning, and version bumping from git history. Use when preparing releases, generating changelogs, or managing plugin versions.
wicked-garden-data-engineer
by mikeparcewski
"ETL pipeline design, data quality assessment, schema validation, and performance optimization as a delegated worker skill. Use when: designing or reviewing ETL/ELT pipelines, assessing dataset quality (completeness, uniqueness, validity, consistency, timeliness), validating data against schemas, optimizing data-processing performance, or recording data-engineering findings on an active task. For inline (non-delegated) data work, use the wicked-garden-data skill's sub-actions instead."
wicked-garden-platform-security-engineer
by mikeparcewski
Security scanning and vulnerability assessment from DevSecOps perspective. Use when: security review, vulnerability assessment, OWASP Top 10 scan, secrets detection, dependency audit, CI/CD pipeline security review, or as the triage rubric behind the platform domain's security action. NOT THIS WHEN: a scenario-driven security TEST run that must produce evidence artifacts + a ledger verdict row (SAST/DAST/secrets scan as a QE gate input) — use wicked-garden-qe-security-test-engineer (executor). Both skills may run semgrep; the contract differs — THIS skill advises on security posture, it does not write QE evidence.
wicked-garden-agentic-safety-reviewer
by mikeparcewski
Guardrails, prompt injection defense, PII protection, human-in-the-loop gates, and hallucination mitigation for agentic systems. Use when: safety review of an AI agent system, guardrail assessment, prompt injection audit, PII/compliance exposure check, HITL gate verification, or as a parallel worker in a heavyweight wicked-garden-agentic review. Cross-ref: EXECUTING injection/jailbreak/refusal-rate/drift probes against a live LLM feature with evidence artifacts + a ledger verdict is wicked-garden-qe-ai-feature-test-engineer (executor); THIS skill is the design-time safety review.
wicked-garden-qe-coverage-archaeologist
by mikeparcewski
Find dark corners in legacy code — untested, unreferenced, or low-confidence paths. Prioritizes by risk using coverage + git history + call-graph. Use when: legacy code audit, coverage gap analysis, dark-code discovery, risk prioritization, test-debt assessment.
wicked-garden-qe-code-analyzer
by mikeparcewski
Static code analysis for testability, quality, and maintainability. Reviews code structure, identifies test-coverage gaps, and flags risky areas. Use when: static analysis, code-quality metrics, testability assessment, maintainability review, coverage-gap identification. Runs on arbitrary source code, anytime — does not require a spec or an active build phase. NOT THIS WHEN: - Reviewing acceptance criteria for SMART+T (pre-code, no implementation yet) — use wicked-garden-qe-requirements-quality-analyst - Judging whether the implementation matches a spec (post-code divergence detection) — use wicked-garden-qe-semantic-reviewer - Rendering a full acceptance verdict (writer + reviewer + executor pipeline) — use wicked-garden-qe accept NOT THIS WHEN: senior-engineer code review (quality, patterns, architecture) — use the wicked-garden-engineering skill's review action; in-run crew review — wicked-garden-governed-worker (Evaluator). THIS skill analyses testability + static quality signals for QE.
wicked-garden-qe-acceptance-test-writer
by mikeparcewski
Reads qe acceptance scenarios and produces structured, evidence-gated test plans. Transforms qualitative criteria into concrete, verifiable artifact requirements. Use when: acceptance testing, test plan generation, scenario verification design <example> Context: New feature scenario needs a structured test plan. user: "Write an acceptance test plan for the 'user can export data as CSV' scenario." <commentary>Use acceptance-test-writer to produce structured, evidence-gated test plans from scenarios.</commentary> </example>
wicked-garden-qe-a11y-test-engineer
by mikeparcewski
Accessibility specialist — axe-core + pa11y, WCAG 2.1 AA / 2.2 AA, keyboard-only flows, focus-ring detection, prefers-reduced-motion, color contrast ≥ 4.5:1. Writes axe/pa11y JSON to the evidence dir, appends a verdict row to DomainStore, and defaults to a CONDITIONAL verdict because automated tools only catch ~30% of WCAG violations. Use when: a11y audit, WCAG compliance, keyboard-only flows, screen reader verification, color contrast, focus management, "is this page accessible". NOT THIS WHEN: design/review-phase accessibility judgment without running tools — use wicked-garden-product-a11y-expert (advisor). This skill EXECUTES axe-core/pa11y and writes evidence artifacts + a ledger verdict row; if no evidence artifact will be written, you want the advisor.
wicked-garden-qe-ai-feature-test-engineer
by mikeparcewski
Tier-2 specialist — testing LLM-backed features. Prompt-injection probes (direct / indirect / payload-smuggling / multi-turn), jailbreak library (DAN, grandma, token-smuggling, base64), refusal-rate regression, hallucination drift against a caller-provided golden set, output-drift monitors (JSON-schema, token length, citation fidelity). Use when: LLM feature under test, prompt-injection review, jailbreak sweep, refusal-rate check, hallucination regression, RAG citation audit, "does this AI feature still behave after the prompt change". NOT THIS WHEN: post-deploy LLM cost/latency monitoring (use wicked-garden-qe-production-quality-engineer); classical model-accuracy metrics (use wicked-garden-qe-data-quality-tester); security bugs in the surrounding app (use wicked-garden-qe-security-test-engineer) — AI-specific attack surface stays here. Cross-ref: design-time agent-safety review is wicked-garden-agentic-safety-reviewer; THIS skill EXECUTES the probes with evidence.
wicked-garden-qe-contract-testing-engineer
by mikeparcewski
API contract testing specialist. Designs and reviews consumer-driven contracts, Pact-style tests, OpenAPI contract verification, schema versioning, and breaking-change detection across service boundaries. Use when: API contract tests, CDC, Pact, OpenAPI verification, schema versioning, breaking-change detection, provider/consumer negotiation.
wicked-garden-qe-chaos-test-engineer
by mikeparcewski
Chaos + resilience specialist — failure injection via Toxiproxy, tc, Chaos Mesh, or AWS FIS. Pre-registers a steady-state hypothesis, caps blast radius, writes a rollback plan, and records the experiment as a task + verdict in DomainStore. REFUSES to run against production targets unless the scenario's frontmatter carries trust_level: production-authorized AND a change-ticket: reference. Use when: resilience testing, chaos engineering, failure injection, game-day design, graceful-degradation verification, recovery drill, dependency-down simulation.
wicked-garden-qe-compliance-test-engineer
by mikeparcewski
Regulatory-control specialist — SOC 2 / HIPAA / GDPR / PCI-DSS evidence collection. Reads a controls: list from the scenario frontmatter, executes a deterministic evidence-gathering command per control, and emits an auditor-ready control-evidence.md + a control-coverage CSV matrix. Verdict tags each control as satisfied / unsatisfied / out-of-scope. Use when: SOC2 readiness run, HIPAA control mapping, GDPR Article-30 record-of-processing, PCI-DSS scope audit, "prove we have evidence for CC6.1", control-walk-through generation. NOT THIS WHEN: regulatory analysis, sensitive-data-handling review, or remediation planning — use wicked-garden-platform-compliance-officer (advisor). THIS skill collects controls EVIDENCE against scenarios and records verdict rows; the officer analyses and advises.
wicked-garden-qe-acceptance-test-reviewer
by mikeparcewski
Evaluates evidence artifacts against test plan assertions independently. CRITICAL ISOLATION: Receives ONLY evidence file paths. Never sees execution context. Catches semantic bugs that self-grading misses. Use when: acceptance test review, evidence evaluation, test verdict <example> Context: Executor produced evidence and it needs independent evaluation. user: "Review the evidence from the file upload acceptance tests and render a verdict." <commentary>Use acceptance-test-reviewer for independent, unbiased verdict on test evidence.</commentary> </example>
wicked-garden-qe-acceptance-test-executor
by mikeparcewski
Follows structured qe test plans step-by-step, collecting evidence artifacts. Executes and captures only — does not judge or grade pass/fail. Writes evidence files to .wicked-qe/evidence/{run-id}/. Use when: acceptance test execution, evidence collection, test plan execution <example> Context: Test plan is ready and needs to be executed step by step. user: "Execute the acceptance test plan for the file upload feature." <commentary>Use acceptance-test-executor for mechanical step execution and evidence capture without judging results.</commentary> </example>
wicked-garden-mem-ingest
by mikeparcewski
"Ingest source files into the wicked-estate knowledge store as cited chunks. Handles text files (md, txt, csv, html, json, code) with deterministic chunking and binary documents (pdf, docx, pptx, xlsx, png, jpg, gif, webp) via LLM vision — the agent extracts and chunks, estate persists and ranks. Use when: dispatched by the wicked-garden-mem skill's ingest action, or directly for 'ingest this file', 'add this document to the knowledge base', 'index this directory', 'learn from this pdf'."
wicked-garden-engineering
by mikeparcewski
Consolidated engineering domain skill: senior-engineer code review, architecture analysis, systematic debugging, implementation planning, and documentation generation. Use when: "review this code / file / diff" (quality, patterns, maintainability; --focus, --persona, --scenarios); "review the architecture of X" / "evaluate component boundaries, coupling, or layer violations" (--scope module service system); "debug this error / bug / unexpected behavior" (hypothesis-driven root cause, reproduction, fix, prevention); "plan this change" / "implementation plan with file changes, risks and tests before writing code"; "generate API docs / README / guide / inline comments" (--type api readme guide inline) or "docs drifted from code". NOT for reviewing an AI agent system (agentic domain review), a UI (product ux-review), or a binding go/no-go verdict (archetype review); NOT for greenfield system design (the architecture module or the wicked-garden-engineering-solution-architect worker).
wicked-garden-mem-capture
by mikeparcewski
"Session-teardown memory capture: sweep the conversation for decisions, patterns, gotchas, discoveries, and preferences, classify each onto the estate kind/tier vocabulary, and batch-write them to wicked-estate memory. Use when: dispatched by the wicked-garden-mem skill's capture action, at session end, before /clear or exit, or when the user says 'capture what we learned' / 'remember this session'."
wicked-garden-jam-brainstorm-facilitator
by mikeparcewski
"Role-plays as focus group personas and synthesizes brainstorming discussions. Use when: brainstorming, ideation, running a full jam session with evidence gathering, discussion rounds, and decision record storage — handed off by the wicked-garden-jam skill's brainstorm sub-action."
wicked-garden-jam
by mikeparcewski
Orchestrates AI-powered brainstorming sessions with dynamic focus groups. quick sessions are ephemeral (no storage). brainstorm and council sessions are tracked as native tasks (process) and stored via wicked-garden-mem (outcome). Use when: "brainstorm this", "explore ideas", "get different perspectives", "focus group", "what do you think about", "pros and cons", "quick check", "jam quick <idea>", "jam brainstorm <topic>", "jam council <topic> with options A/B/C", "multi-model evaluation", "council verdict", "jam revisit <decision>", "how did that decision work out".