mikeparcewski
145 verified skills1,160 total stars
wicked-garden-smaht
Context assembly / briefing builder (the name is a phonetic play on "smart"). Gathers a relevant on-demand context briefing over wicked-brain + wicked-garden:search + domain state. Pull-model: subagents call it when they need background rather than having context pushed onto every prompt (v6 replaced the v5 push orchestrator, #428). Routes three sub-actions backed by refs/: briefing (what happened since the last session — NOT live state), state (live SessionState/adapter/directive inspection — NOT since-last-session), events-import (DomainStore records → unified event log). Use when: gathering a context briefing before a task, "assemble context", "give me a briefing", "what happened since my last session", resuming work after a session break, building background on an unfamiliar area, "show session state", "inspect live session state", "import domain records into the event log", or any former /wicked-garden:smaht:{briefing|state|events-import} invocation. Aliases: context-assembly, briefing, smart-context.
development8
wicked-garden-engineering
Consolidated engineering domain skill: senior-engineer code review, architecture analysis, systematic debugging, implementation planning, and documentation generation — plus cross-cutting guidance on code quality, patterns, and maintainability. Use when: "review this code / file / diff" (quality, patterns, maintainability; --focus security|performance|patterns|tests, --persona <name>, --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 specific file changes, risk assessment, and test recommendations before writing code"; "generate API docs / README / guide / inline comments" (--type api|readme|guide|inline) or "docs drifted from code". Replaces the former /wicked-garden:engineering:{review,arch,debug,plan,docs} commands. 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 (architecture knowledge module or the wicked-garden-engineering-solution-architect fork skill).
development8
wicked-garden-product-accessibility
Use when auditing code for WCAG 2.1 AA compliance — keyboard navigation, ARIA patterns, color contrast, and semantic HTML. Produces prioritized remediation with code-level fixes. NOT for running automated a11y tools (use product:a11y command) or visual design review (use product/visual-review).
tools8
wicked-garden-jam-brainstorm-facilitator
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 — dispatched by the wicked-garden-jam skill's brainstorm sub-action.
testing8
wicked-garden-jam-council
Runs structured multi-model council evaluations using external LLM CLIs. Use when: multi-model evaluation, council verdict on defined options, high-stakes decision needing genuinely independent model perspectives — dispatched by the wicked-garden-jam skill's council sub-action.
tools8
wicked-garden-platform-security-engineer
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.
development8
sync
Keep documentation in sync with code changes. Detect stale docs, identify drift between code and docs, and suggest updates when code changes. Use when: "check doc freshness", "sync docs", "docs out of date", "update docs after refactor", "docs drift", "docs out of sync"
development8
docs-audit
Audit documentation coverage and quality. Find undocumented code, assess completeness, and provide coverage metrics. Use when: "audit docs", "doc coverage report", "find undocumented code", "documentation gaps", "what's missing docs", "doc completeness"
development8
traces
Distributed tracing analysis for performance investigation and service dependency mapping. Analyze latency breakdowns, identify bottlenecks, map service calls, and correlate slow requests with code changes. Use when: "trace analysis", "distributed tracing", "latency investigation", "slow requests", "service dependencies", "performance tracing"
development8
policy
Policy interpretation and compliance guidance. Translates regulatory requirements into actionable controls, maps policies to code, and provides implementation guidance. Use when: "regulatory policy", "compliance policy", "translate policy to controls", "map regulation to code", "policy implementation guidance"
development8
design-review
Visual design and UI consistency review — design system adherence, spacing tokens, typography, color usage, component patterns, and responsive polish. Use when: "design critique", "polish the UI", "design system adherence", "responsive design", "visual polish", "review the design", "UI inconsistency"
testing8
wicked-garden-product-ui-reviewer
Visual and UI design review. Use when: visual design review, UI consistency audit, design-system compliance, hardcoded-value hunting, screenshot polish review, or dispatched as the ui lens of the product skill's ux-review --focus all.
development8
wicked-garden-product-a11y-expert
Audit accessibility compliance - WCAG guidelines, keyboard navigation, screen reader support, color contrast, semantic HTML. Use when: accessibility audit, WCAG compliance, keyboard-navigation review, screen-reader support check, or dispatched as the a11y lens of the product skill's ux-review --focus all.
development8
agent-browser
Browser automation skill with priority-ordered CLI discovery. Detects the best available browser automation tool in the system PATH and provides usage patterns for Playwright, Puppeteer, Cypress, and Selenium WebDriver. Use when: - Taking screenshots or extracting page content - Automating web forms and UI interactions - Accessibility audits - Web scraping for AI agents - Testing web applications - End-to-end test execution
tools8
wicked-garden-platform-prereq-doctor
Diagnose missing tools and dependencies, offer to install them. Use when: "command not found", "ModuleNotFoundError", "missing tool", "install dependency", "prereq check", "setup validation"
tools8
wicked-garden-platform-peer-health
Run a health check on all wicked-* peer tools (wicked-vault, wicked-testing, wicked-brain, wicked-bus). Reports reachability, version vs. pin, and declared capability status for each peer. The replacement for `npx wicked-loom doctor` after Phase B absorption — peer-resolution now runs in-process via scripts/loom/, no external wicked-loom needed. Use when: "peer health", "check the wicked peers", "is wicked-vault reachable", "loom doctor", "peer version drift", "capability gap", or any former /wicked-garden:platform:peer-health invocation.
tools8
wicked-garden-platform-observability
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.
tools8
wicked-garden-platform-gitlab-ci
Write secure, optimized GitLab CI/CD pipelines. Use when: "create CI/CD pipeline", "GitLab CI config", "fix pipeline", ".gitlab-ci.yml", "configure runners", "pipeline optimization"
testing8
wicked-garden-platform-glab-cli
Use when you need glab CLI patterns for GitLab — pipeline debugging, MR management, or release automation. Provides composable glab invocations for power users. NOT for GitHub (use the gh-cli skill) or simple git commands (use Bash).
tools8
wicked-garden-platform-github-actions
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.
development8
wicked-garden-product-requirements-analyst
Elicit and document requirements with precision. Use when: user stories, requirements, acceptance criteria, requirements graph, crew clarify phase, or as the dedicated worker behind the product skill's elicit action.
testing8
wicked-garden-platform-gh-cli
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).
tools8
wicked-garden-product-ux-review
Use when evaluating UX quality — user flows, information architecture, user research synthesis, personas, and usability assessment. Also covers generative UX flow design from requirements. NOT for visual design consistency (use visual-review) or accessibility code audits (use product/accessibility).
development8
wicked-garden-smaht-propose-skills
Mine recent Claude Code session transcripts to propose skills that would automate repetitive patterns the user actually does. Read-only MVP — outputs a markdown report only. No interactive UI, no scaffolding handoff in v1 (those are v2/v3 follow-ups). Use when: "find skills I should build", "what should I automate", "propose skills from my sessions", "mine my history for skill ideas", "session-mined skill builder", "skill discovery from past usage".
development8
wicked-garden-product-imagery-alter
AI-powered image modification: img2img editing and mask-based inpainting. Requires a provider that supports editing operations. Use when: "edit image", "modify image", "change image", "inpaint", "img2img"
data-ai8
wicked-garden-product-analyze
Sentiment analysis, theme extraction, and trend detection from customer feedback. Use when: analyzing customer feedback for sentiment, extracting themes from support or survey data, or detecting trends in voice-of-customer signal.
data-ai8
wicked-garden-product-imagery
Visual asset lifecycle management — analysis, generation, modification, and review. Three sub-skills cover the full creative pipeline with provider abstraction. Use when: generating, editing, analyzing, or reviewing an image — routes to the appropriate sub-skill (create / alter / review).
devops8
wicked-garden-product
Product domain skill: 13 user-invokable actions — a11y | acceptance | align | analyze | elicit | listen | mockup | screenshot | strategy | synthesize | ux | ux-review | visual-direction — backed by the rubrics in refs/ and this domain's knowledge-module sub-skills. Use when: "accessibility audit", "WCAG compliance", "define acceptance criteria", "stakeholder alignment", "build consensus", "analyze customer feedback", "elicit requirements", "write user stories", "aggregate customer feedback", "ASCII wireframe or HTML mockup", "review this screenshot", "strategic analysis", "ROI / value proposition / market / competitive", "synthesize feedback into recommendations", "design a user flow", "UX review", "design audit", "visual direction", or any former /wicked-garden:product:{action} invocation.
development8
wicked-garden-product-imagery-create
AI-powered image generation from text prompts using multiple providers. Supports 5 providers: cstudio, vertex-curl, OpenAI, Stability AI, Replicate. Use when: "generate image", "create image", "text to image", "new visual"
data-ai8
wicked-garden-platform-health
System health overview from discovered observability sources. Aggregates errors, performance metrics, and SLO status across services. Correlates with deployments and code changes. Use for proactive health monitoring and post-deployment validation. Use when: checking aggregated system health, validating a post-deployment state, correlating production status with recent changes, "how is production", "check system health", or any former /wicked-garden:platform:health invocation. NOT for plugin-level diagnostics (use the observability sub-skill) or distributed tracing (use the platform domain skill's traces action).
tools8
wicked-garden-product-acceptance-criteria
Define testable acceptance criteria from requirements and design. Bridge product requirements with QE test scenarios. Use when: "define acceptance criteria", "how do we know it's done", "what should QE test", "definition of done"
testing8
wicked-garden-platform-errors
Use when investigating a production error spike or pattern across services — aggregates errors from discovered tracking sources, correlates with deployments, and assesses user impact. NOT for general observability (use platform/observability) or tracing latency (use the platform:traces command).
testing8
wicked-garden-product-requirements-navigate
Navigate, query, and maintain requirements graphs. Regenerates meta.md on demand, checks coverage, finds gaps, and lints the graph structure. Use when: navigating or querying a requirements graph, generating a coverage report, refreshing meta.md, or linting graph structure for gaps.
development8
wicked-garden-platform-gate-benchmark-rebaseline
Re-baseline procedure for the AC-11 gate-result benchmark lane (`tests/crew/test_gate_result_benchmark.py`). The benchmark enforces a 2× p95 SLO on `gate-result.json` ingestion. When a deliberate perf change lands on main (validator hardening, cache tuning, schema expansion), the baseline needs updating. Never re-baseline to silence a regression. Use when: "re-baseline AC-11 benchmark", "gate-result benchmark regression", "p95 benchmark baseline out of date", "update benchmark_baseline.json", "benchmark.yml failure", "gate-result p95 exceeds 2x baseline", "rebaseline procedure", or `AC-11` baseline drift.
testing8
wicked-garden-product-ux-designer
Design and evaluate user flows, interaction patterns, and information architecture. Use when: user flow design, IA mapping, Nielsen heuristic review, interaction-pattern selection, or dispatched as the flows+research lens of the product skill's ux-review --focus all.
development8
wicked-garden-product-mockup
Use when you need a quick ASCII wireframe or HTML mockup in-chat without Figma overhead. NOT for production design work — use the figma plugin for that.
tools8
wicked-garden-product-requirements-analysis
Use when turning a vague idea or stakeholder ask into structured user stories with acceptance criteria and a requirements graph. For complexity >= 3 or compliance projects, defaults to graph mode. NOT for navigating an existing requirements graph (use requirements-navigate) or stakeholder alignment (use product:align).
research8
wicked-garden-product-requirements-graph
Graph-based requirements as atomic markdown files with rich frontmatter. Filesystem-as-graph: each AC is a node, directories are groupings, meta.md files are the human interface, frontmatter traces are the edges. Use when: defining requirements as a filesystem graph of atomic ACs, eliciting user stories, or laying out acceptance criteria with traceable edges.
testing8
wicked-garden-product-imagery-review
Multi-dimensional visual analysis and quality review of images. No external provider required — reads image files directly. Use when: reviewing an image for visual quality, brand-guideline adherence, or accessibility before production use.
testing8
wicked-garden-product-requirements-migrate
Convert monolithic requirements documents into graph-structured requirements directories. Parses user stories and acceptance criteria from existing docs and creates atomic graph nodes. Use when: "migrate requirements", "convert to graph", "split requirements", "restructure requirements"
documentation8
wicked-garden-product-strategy
Strategic business analysis for technical investments. Evaluates ROI, value proposition, competitive positioning, and market alignment. Provides decision support with business justification. Use when: building a business case for a technical investment, evaluating ROI or value proposition, or doing competitive positioning analysis.
development8
wicked-garden-product-synthesize
Generate actionable recommendations from customer voice insights. This skill should be used when the user needs to translate analyzed feedback into product priorities, feature recommendations, or strategic guidance. Use when: "recommendations from feedback", "translate feedback to priorities", "feature priorities from customer data", "synthesize feedback into action"
data-ai8
wicked-garden-product-value-strategist
Value-proposition design AND stakeholder alignment in one agent. Use when: value proposition, differentiation, JTBD mapping, defensibility, consensus building, or dispatched as the value lens of the product skill's strategy --focus all.
development8
wicked-garden-prove
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.
development8
wicked-garden-product-visual-direction
Figure out what a section of content *should be* visually before reaching for any implementation pattern. Answers five structured questions — content structure, audience mental model, desired action, physical artifact metaphor, and the stupid-question test — then produces a one-paragraph visual brief for the implementer. Use when: designing a new section, evaluating a proposed visual treatment, or catching the nearest-neighbor trap (copying the adjacent project's pattern without asking if it fits). NOT for: accessibility audits (use product:a11y), visual consistency review (use product:ux-review), or wireframing (use product:mockup).
testing8
wicked-garden-product-visual-review
Use when auditing visual design for consistency — design system adherence, spacing tokens, typography scale, color palette, component patterns, and responsive polish. Structured checklist + scoring. NOT for UX flows or user research (use ux-review) or accessibility code audits (use product/accessibility).
development8
wicked-garden-qe-semantic-reviewer
Render an INDEPENDENT semantic verdict on whether code implements what each acceptance criterion MEANS — not whether the AC id is referenced. Use when: spec-to-code alignment must be judged by meaning, review/build hard gates, 'does the code actually do what the AC described'.
development8
wicked-garden-smaht-intent
Show or set the session intent variable. Intent gates how loud the framework is — simple-edit (silent), feature/research (synthesis directive), rigor (full crew context). Auto-detected on turn 1; this skill overrides explicitly. Sticky for the session. Use when: "set intent", "intent override", "/wicked-garden:intent", "make the framework quiet", "force rigor", "what's my intent".
development8
wicked-garden-swarm
Parallel verification-swarm orchestration playbook: fan out N scoped subagents over N units of work (repos / modules / files), then run a SEPARATE verifier wave that re-derives each result from a clean state — self-graded "done" is rejected. Composes the crew agents, the qe semantic-reviewer, /wicked-garden:prove, wicked-vault attestation, and the worktrees + deliberate skills rather than reinventing them. This is multi-AGENT parallel execution+verification; for independent multi-MODEL perspectives use jam:council instead. Use when: multi-unit / fan-out work ("review every repo", "resolve the backlog with proof", "apply this across all modules", "audit each service"), high-blast-radius changes that need independent verification, or any run where a claimed "done" must be re-derivable from receipts.
testing8
wicked-garden-workflow
Reference for how the wicked-crew workflow engine operates — phase catalog, gate enforcement, rigor tiers, and facilitator rubric. Use when understanding or troubleshooting crew phase mechanics (gate config, CONDITIONAL resolution, phase dependencies). NOT for starting a project (use crew:start) or proposing a process plan (use propose-process).
development8
wicked-garden-product-listen
Aggregate customer feedback from discovered sources across support, surveys, social, and direct channels. This skill should be used when the user needs to gather customer voice data to inform product decisions or understand sentiment. Use when: aggregating customer feedback from discovered sources, gathering voice-of-customer data, or surveying sentiment across channels.
testing8
wicked-garden-search-codebase-narrator
Narrate codebase structure and architecture for orientation — directory layout, key modules, data flows, technical decisions, and code health. A query + synthesis capability rather than a persistent role; produces a guided reading order and flags gotchas for newcomers. Use when: "give me an architecture walkthrough", "narrate this codebase", "explain how this project is organized", "code navigation", "where should I start reading".
development8
wicked-garden-product-screenshot
Screenshot-based UI review using Claude's multimodal capabilities. Analyzes visual design from image files — layout, spacing, color, typography, responsiveness — and compares against design system rules. Use when: reviewing a UI screenshot for visual design, comparing rendered output against design system rules, or auditing layout from an image file.
testing8
wicked-garden-search
Code-intelligence search over wicked-brain's unified static + injected code-relationship graph (ADR 0004). One skill, six routed actions: index (build/refresh the semantic + structural layers), blast-radius (impact analysis over dependents), lineage (data/dependency flow), hotspots (most-referenced symbols), service-map (service architecture from infra + code), and narrate (codebase orientation walkthrough). Use when: "index the codebase" / "build or refresh the code-intelligence index"; "what would break if I change X" / "blast radius of" / "impact analysis"; "trace lineage" / "where does this flow from/to" / "upstream or downstream of a symbol"; "most-referenced symbols" / "find god objects" / "coupling hotspots"; "map the services" / "service dependency map" / "visualize the service architecture"; "architecture walkthrough" / "narrate this codebase". Replaces the former /wicked-garden:search:* commands (index, blast-radius, lineage, hotspots, service-map). NOT for general code/concept search — use wicked-brain:search or wicked-brain:query directly.
development8
wicked-garden-platform
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 fork 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.
tools8
wicked-garden-platform-compliance-officer
Regulatory compliance expert. Use when: SOC2, HIPAA, GDPR, PCI, regulatory compliance analysis of code and systems — identifies sensitive data handling, verifies required controls, detects violations, and provides prioritized remediation with evidence.
development8
wicked-garden-platform-audit
Audit evidence collection and trail verification. Gathers artifacts, validates controls, generates audit reports, and maintains compliance documentation. Use when: "audit trail", "collect evidence", "audit report", "control testing", "compliance documentation", "gather audit evidence for SOC2/HIPAA/GDPR/PCI", or any former /wicked-garden:platform:audit invocation. NOT for defining compliance policies (use the compliance sub-skill) or ad hoc security checks (use the platform domain skill's security action).
testing8
wicked-garden-platform-compliance
Use when checking code or architecture against a regulatory framework (SOC2, HIPAA, GDPR, PCI) or translating a policy document into actionable controls — detects violations and provides prioritized remediation guidance. NOT for gathering audit evidence artifacts (use platform/audit). Use when: "is this compliant", "compliance check", "regulatory requirements", "check against SOC2/HIPAA/GDPR/PCI", or any former /wicked-garden:platform:compliance invocation.
development8
smaht-synthesize
Internal context synthesis engine. Triggered by UserPromptSubmit hook when complexity or risk is above threshold. Runs agentic exploration — facilitator + fan-out subagents — to produce a complete turn directive grounded in project knowledge. NOT user-invokeable. Called automatically by the hook via skill directive injection.
testing8
scenarios
Guide for writing E2E test scenarios in the wicked-scenarios format. Covers scenario structure, frontmatter fields, step format, and best practices. Use when: - Creating new test scenarios - Understanding the scenario format - Choosing the right CLI tool for a test category
tools8
scenario-executor
Runner for acceptance test scenarios — reads scenario markdown, executes steps via Bash or Skill tool, and reports PASS/FAIL with evidence. Handles mixed bash + slash-command scenarios, prose-only steps, and wicked-scenarios format delegation. A tool/runner capability, not an agent identity — the test-designer agent owns the role of designing and rendering verdicts. Use when: "run this scenario", "execute the acceptance test for X", "run the wicked-scenarios file", "test this slash command end-to-end".
tools8
acceptance-testing
Evidence-gated acceptance testing with three-agent separation of concerns. Writer designs test plans, Executor collects artifacts, Reviewer evaluates independently. Eliminates false positives from self-grading. Use when: "run acceptance tests", "verify it works", "did it pass", "test this scenario", "acceptance criteria", "validate the feature"
testing8
memory
Memory storage, recall, and lifecycle management for maintaining context across sessions. This skill should be used when the user asks to "remember this", "store a decision", "recall what we did", "find past context", "save for later", "what did we learn", "what did we decide", or mentions persisting knowledge, decisions, or learnings. Use when: - "remember this for next time" - "store this decision" - "what did we do before" - "recall past context" - "save this pattern"
testing8
readme-style-guide
Canonical README template and validation rules for Wicked Garden marketplace plugins. Use when: "write a README", "plugin README template", "README structure", "marketplace README", "README style guide", "validate README"
tools8
release
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.
tools8
qe-strategy
Shift-left QE strategy for test planning and quality analysis. This skill should be used when the user needs test scenarios, risk assessment, test plans, or coverage analysis outside of a crew workflow context. Use when: "test strategy", "what should I test", "test scenarios", "shift-left testing", "generate test plan", "test coverage", "risk assessment", "how do I test this"
testing8
adopt-legacy
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.
development8
ux-flow
UX flow design and analysis. Creates user flow diagrams, interaction patterns, and information architecture. Generative — creates and maps flows rather than evaluating existing ones (see product/ux-review for evaluation). Use when: "user flow", "flow diagram", "interaction design", "information architecture", "IA mapping", "user journey map", "navigation design", "flow analysis"
development8
tdd-coach
Guide Test-Driven Development workflow — teach red-green-refactor cycle, test-first approach, and TDD best practices. Validate test quality. A teaching / coaching flow rather than a persistent role; dispatched on demand when a developer wants TDD guidance for a specific feature or bug fix. Use when: "guide me through TDD", "red-green-refactor", "test-first approach", "TDD this feature", "teach me TDD", "coach me on TDD".
development8
unified-search
This skill should be used when searching code, finding documentation, understanding code-doc relationships, or performing impact analysis. Use when: "search code", "find function", "find class", "where is defined", "search docs", "PDF content", "cross reference", "impact analysis", "blast radius", "what calls this", "find all references". Prefer this over raw Grep/Glob for symbol search, impact analysis, code-doc cross-references, and understanding codebase structure.
development8
propose-process
Delegation shim for the lead-facilitator rubric. Dispatches the `wicked-garden:crew:process-facilitator` agent (which holds the rubric extracted in #652 item 3), reads back the JSON plan the agent writes to `${project_dir}/process-plan.draft.json`, and either returns it directly (`output=json`) or renders `process-plan.md` + emits the `TaskCreate` chain. Does NOT score factors or pick specialists itself — that all happens inside the dispatched agent. Use when: starting a new crew project, re-planning after a gate finding, emitting the initial task chain for `/wicked-garden:crew:start`, or invoked on `TaskCompleted` to prune / augment / re-tier the remaining chain. Also used by `/wicked-garden:crew:just-finish` (yolo mode) to drive autonomous completion.
testing8
wicked-garden-runtime-exec
Smart runtime execution for Python and Node scripts with automatic package manager detection. Invoked by other skills and agents when scripts need execution with correct runtime resolution.
development8
pipeline
This skill should be used when designing or reviewing data pipelines — ETL patterns, orchestration, and performance optimization for data workflows. Use when: - "design a data pipeline" - "review this ETL" - "optimize data processing" - "how should I orchestrate this" - "pipeline architecture"
devops8
issue-reporting
Automated GitHub issue detection and filing from Claude sessions. Tracks tool failures and task completion mismatches. Files issues automatically at session end or on demand via /wicked-garden:report-issue. Includes duplicate detection, codebase research, memory recall, SMART criteria validation, and advisory quality gate before filing. Use when: "file a bug", "report issue", "something went wrong", "not working as expected", "create issue", reporting UX friction, logging unmet outcomes, or investigating tool failures.
tools8
reporting
Multi-perspective project delivery reporting with persona-based analysis. Generates actionable reports from project data using 6 specialized stakeholder perspectives. Use when: generating a delivery / status report, preparing a sprint retrospective, or producing a stakeholder update from project data. Enhanced with: - wicked-brain:memory Stores insights across sessions
testing8
rollout
Plan and coordinate progressive feature rollouts. Risk assessment, canary deployments, feature flag management, rollback procedures. Discovers deployment tools via capabilities. Use when: "roll out feature", "progressive rollout", "canary deployment", "feature flag", "rollback plan", "launch feature", "deploy gradually"
tools8
evidence-validation
Validates that completed task descriptions include required evidence fields at the appropriate level for the task's complexity score. Three tiers (low, medium, high) map to complexity ranges 1-2, 3-4, 5-7. Use when: validating a TaskUpdate description before marking complete, or checking that evidence fields match the task's complexity tier.
testing8
change-type-detector
Classifies a list of file paths into change types (ui, api, both, unknown) using an explicit two-pass decision algorithm: extension matching first, then path-segment matching for ambiguous cases. Use when: "detect change type", "classify files", "what kind of change", "ui or api change", "change-type detection", or before creating test tasks.
tools8
adaptive
Adaptive engagement patterns for wicked-crew based on context, phase, and user preferences. Controls autonomy levels (just-finish, balanced, ask-first) and communication style. Use when: setting or changing autonomy level (just-finish / balanced / ask-first), adjusting communication style, or applying a saved engagement preference profile.
tools8
explain
Translate jargon-heavy crew output into plain language. Input is typically a gate finding, reviewer brief, phase summary, or process plan containing specialist vocab (RED, BLOCK, convergence, blast radius, parallelization_check, CONDITIONAL, BLEND rule, etc.). Output is 2-4 sentences at a grade-8 reading level with no specialist vocab left behind. Use when: "explain this", "in plain English", "what does this mean", "translate for me", "simplify", "dumb this down", or any request to render crew jargon into language a non-practitioner can act on. Also used automatically by the orchestrator when `crew.output_style = paired` or `plain-only` — the skill produces the `**Plain:**` line.
development8
ml
This skill should be used when working with machine learning models — architecture review, training pipeline design, feature engineering, and deployment guidance. Use when: - "review this ML model" - "design ML training pipeline" - "how should I deploy this model" - "feature engineering advice" - "ML architecture guidance"
devops8
data
Use when profiling a dataset's structure, validating it against a schema, or generating a data quality report (completeness, uniqueness, validity constraints). Runs the data_profiler.py and schema_validator.py scripts. NOT for exploratory pattern analysis (use data/analysis) or SQL queries (use data:analyze).
testing8
crew-qe-gate
Crew-integrated quality gates for phase transitions: value gate, strategy gate, execution gate. Runs gate analysis at crew checkpoints (post-clarify, post-design, post-build) to validate readiness before advancing. Quality checkpoint within the wicked-crew workflow. Use when: running a value / strategy / execution gate at a crew checkpoint, validating phase-transition readiness, or asking "is this ready to advance".
development8
design
Design statistically rigorous A/B tests and experiments. Formulate hypotheses, select metrics, calculate sample sizes. Discovers analytics and feature flag tools via capability detection. Use when: "design experiment", "A/B test", "hypothesis", "sample size", "what metrics", "test my feature", "should we experiment"
tools8
onboarding-guide
Guide new developers through team onboarding. Analyzes project health, team patterns, delivery metrics, and codebase structure to produce a personalized onboarding plan with specific first tasks, graduated complexity, and human connections. A guided walkthrough, not an agent identity. Use when: "onboard a new developer", "getting-started guide", "team orientation for new hire", "first week plan", "day-one productivity".
development8
analysis
Use when exploring a dataset for patterns, trends, and business insights — EDA, segmentation, anomaly detection, and visualization guidance. Generates the Observation → Insight → Action chain. NOT for schema validation or data quality scoring (use the data/data skill) or SQL queries (use data:analyze).
testing8
facilitator-score
Score 9 risk factors for a new project via structured yes/no questionnaire. Use *before* propose-process to skip the manual rubric tax. Returns a factors block (same shape as propose-process output-schema.md) for direct injection into Step 3. NOT for: re-evaluation of an in-flight project (use propose-process re-evaluate mode), one-off complexity guesses (use deliberate), or any use that requires overriding all 9 factors by hand (just use propose-process directly).
testing8
get-tsconfig
Find, parse, and query tsconfig.json files — extends resolution, file matching, path alias resolution. Use when reading tsconfig.json, checking if a file belongs to a tsconfig, resolving TypeScript path aliases, or working with tsconfig extends chains.
development8
product-management
Strategic product thinking for roadmap, priorities, and business value. Elicit requirements, define scope, and align stakeholders. Works standalone or integrated with wicked-crew. Use when: planning a roadmap, prioritizing a backlog, or defining scope and stakeholder alignment for an upcoming feature.
testing8
wicked-garden-smaht-discovery
Contextual discovery — suggests a related skill or action based on what was just used. Discovers relationships dynamically from skill content, not a static map. Invoked by the Stop hook and the smaht `briefing` sub-action (skills/smaht/refs/briefing.md, step 5) to surface one relevant suggestion.
content-media8
plugin-json-schema
Official Claude Code plugin.json schema reference and validation guide. Use when creating or troubleshooting plugin.json manifest files. Covers all fields, auto-discovery behavior, path formats, and common validation errors.
tools8
engineering
Senior engineering guidance on implementation, code quality, and maintainability. Use when reviewing code for R1-R6 standards violations (dead code, bare panics, magic values, swallowed errors, unbounded ops, god functions) or getting cross-cutting implementation advice. NOT for architecture decisions (use the architecture skill) or debugging (use the debugging skill).
development8
five-layer-architecture
Five-layer architectural model for building production-grade agentic systems with clear separation of concerns. Use when: "agent architecture layers", "five layer", "agent system design", "separation of concerns agents"
development8
maturity-model
Five-level maturity assessment model for agentic systems from prototype to optimized production. Use when: "agent maturity", "production readiness", "how mature is my agent", "agent assessment"
data-ai8
workflow
Core wicked-crew v3 workflow engine with capability-based orchestration and phase progression. Drives projects through crew phases: clarify → design → test-strategy → build → test → review. Smart decisioning analyzes signals to determine which specialists to engage per phase. Use when: "crew phases", "phase plan", "workflow execution", "start a project", "clarify outcome", "design phase", "build phase", "approve phase", "crew workflow", "phase progression", "QE gate", "shift-left testing", or structured delivery guidance.
development8
numbers
This skill should be used when running interactive SQL queries against local data files. Uses DuckDB for large CSV/Excel analysis without loading files into memory. Use when: - "query this CSV with SQL" - "run SQL against this data file" - "explore large dataset with DuckDB" - "join these CSV files" - "aggregate across multiple files" - Detecting data quality issues (nulls, duplicates, type mismatches)
testing8
generate
Generate documentation from code - extract types, comments, and signatures to create API docs, README files, and reference documentation. Focus on useful, actionable docs. Use when: "generate docs", "create documentation", "document the API", "generate README", "make docs from code"
development8
task-management
Persistent task management through kanban boards with cross-session tracking. Provides guidance for using wicked-garden:kanban for CRUD operations, dependencies, priorities, and sprint management. Use when: "track tasks", "create a task", "add a todo", "manage tasks", "show my tasks", "what should I work on", "move task to done", "update task status", "kanban board", "project management"
testing8
wicked-garden-domain-coverage
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.
development8
wicked-garden-data
Data engineering, analysis, and ML toolkit. One skill, routed sub-actions: analyze (interactive EDA on a CSV/Excel/data file), profile / validate / quality (schema-level data engineering ops), ml review / ml pipeline (model review + training-pipeline design), pipeline design / pipeline review (ETL architecture), and ontology (recommend Schema.org, Dublin Core, DCAT, FOAF, GoodRelations, SKOS, or a custom shape for a dataset). Use when: "analyze this CSV/Excel/data file" / "explore this dataset" / one-off data exploration; "profile this dataset" / "validate data against a schema" / "generate a data quality report" (completeness, uniqueness, validity); "review this ML model" / "design an ML training pipeline"; "design a data pipeline" / "review this ETL" / "optimize data processing"; "recommend an ontology for this data" / "map columns to a public ontology". Replaces the former /wicked-garden:data:* commands (analyze, data, ml, ontology, pipeline). NOT for delegated subagent work — dispatch the wicked-garden-data-engineer fork skill for that.
tools8
wicked-garden-deliberate
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.
development8
wicked-garden-agentic-performance-analyst
Token optimization, latency budgets, cost analysis, caching strategy, and parallelization assessment for agentic systems. Use when: performance optimization of an AI agent system, cost analysis or token-budget review, latency profiling, cache-strategy assessment, parallelization opportunities, or as a parallel worker in a heavyweight wicked-garden-agentic review.
data-ai8
wicked-garden-agentic-safety-reviewer
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.
testing8
wicked-garden-crew-implementer
Execute implementation tasks according to approved designs and test strategies. Use when: executing implementation tasks from approved designs and test strategies, building features against phase artifacts, parallel dispatch of independent sub-tasks (single-message multi-Task batch), tracking work via the TaskCreate/TaskUpdate lifecycle with structured Evidence sections.
development8
wicked-garden-agentic
Agentic-systems domain skill: review, design, audit, and framework selection for AI agent systems. Routes to one of four actions (review | design | audit | frameworks) backed by the rubrics in refs/. Use when: "agentic review", "review this agent system", "full agentic codebase review", "trust and safety audit", "audit my agents for GDPR/HIPAA/SOC2/NIST compliance", "design an agentic system", "design a multi-agent architecture", "which agentic framework should I use", "compare LangChain vs CrewAI vs AutoGen", or any former /wicked-garden:agentic:{review|design|audit|frameworks} invocation. Disambiguation: this domain reviews and designs **AI agent systems**. For ordinary source code use the engineering review; for a binding go/no-go verdict use the archetype review (see docs/domains.md → "review appears in three domains").
development8
wicked-garden-agentic-architect
Five-layer architecture validation, agent topology analysis, orchestration pattern assessment, and framework detection for agentic systems. Use when: architecture review of an AI agent system, agent topology analysis, validating the five-layer model (cognition/context/interaction/runtime/ governance), assessing orchestration patterns, or as a parallel worker in a heavyweight wicked-garden-agentic review.
development8
wicked-garden-agentic-frameworks
Use when selecting or comparing agentic frameworks (LangChain, LangGraph, CrewAI, AutoGen, etc.) — curated comparison by use case, language, and maturity. Gets latest context via Context7 when available. NOT for reviewing existing agentic code (use review-methodology) or architecture patterns (use agentic-patterns).
development8
wicked-garden-crew-reviewer
Perform basic code review and validation. Use when: general code review without a domain-specific specialist available, validating implementation against design and evidence quality, gate reviews requiring reviewer separation (evaluator != creator)
development8
wicked-garden-agentic-review-methodology
Use when reviewing an agentic codebase for issues, risks, and maturity gaps — covers the four-phase review process (Detect → Analyze → Prioritize → Report) and the five-level maturity model (Prototype → Functional → Reliable → Production → Optimized) for assessing production readiness. NOT for architecture design (use agentic-patterns) or live agentic review with a subagent (use agentic:review command).
development8
wicked-garden-agentic-context-engineering
Context window management, token optimization, and memory patterns for efficient multi-agent systems. Use when: optimizing token usage in an agentic pipeline, designing memory scope for short / long-term / episodic state, or applying a context-loading strategy (anticipatory / JIT / hybrid).
testing8
wicked-garden-classify
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.
testing8
wicked-garden-data-engineer
ETL pipeline design, data quality assessment, schema validation, and performance optimization as a delegated fork worker. 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.
testing8
wicked-garden-agentic-agentic-patterns
Use when designing or analyzing multi-agent architectures — covers core patterns (sequential, hierarchical, parallel, event-driven), anti-patterns, and the five-layer model (Cognition → Context → Interaction → Runtime → Governance) for separating concerns in production-grade agentic systems. NOT for reviewing existing agentic code (use review-methodology) or framework selection (use the frameworks skill).
development8
wicked-garden-agentic-trust-and-safety
Trust, safety, and control patterns for production agentic systems with human-in-the-loop gates and guardrails. Use when: designing guardrails or human-in-the-loop gates for an agent, or hardening an agentic system against prompt injection.
development8
wicked-garden-crew-researcher
Explore codebase and gather context before design or implementation choices. Use when: codebase exploration, pattern discovery, dependency mapping, read-only recon before design decisions, gathering context ahead of implementation, or fanning out as a recon worker in a swarm's recon wave.
development8
wicked-garden-engineering-api-documentarian
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.
development8
wicked-garden-engineering-migration-engineer
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.
development8
wicked-garden-engineering-integration
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"
development8
wicked-garden-engineering-patch
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).
development8
wicked-garden-engineering-solution-architect
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.
testing8
wicked-garden-multi-model
DEPRECATED — collapsed into the jam council surface. The multi-model council now lives entirely in `wicked-garden-jam` (its `council` sub-action) and the worker `wicked-garden-jam-council`. This stub only keeps existing registry/manifest references resolving; it dispatches nothing. Use `wicked-garden-jam` with `council <topic> --options "A, B, C"` instead.
testing8
wicked-garden-engineering-backend
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"
development8
wicked-garden-engineering-architecture
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"
testing8
wicked-garden-engineering-debugging
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"
development8
wicked-garden-engineering-docs
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).
development8
wicked-garden-engineering-large-scale-migration
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.
tools8
wicked-garden-engineering-unit-test-quality
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.
development8
wicked-garden-persona-agent
Executes tasks under a named persona's behavioral profile. Use when: dispatched by the wicked-garden-persona skill's 'as' action with a fully-formatted persona profile + task — any task that needs a specific perspective (review, analysis, content generation, brainstorming) executed in character.
development8
wicked-garden-engineering-frontend
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"
development8
wicked-garden-platform-privacy-expert
Privacy and data protection specialist. Use when: PII, PHI, data protection, privacy by design, GDPR — detects personal data handling, classifies sensitivity, verifies privacy controls, and assesses data subject rights implementation.
testing8
wicked-garden-engineering-system-design
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).
content-media8
wicked-garden-jam
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 in wicked-brain:memory (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".
testing8
wicked-garden-persona
On-demand persona invocation system for applying named perspectives to any task. Sub-actions: `as <name> <task>` (invoke a persona), `list [--role R]` (discover personas), `define <name> --focus "..." [--save]` (create or update a custom persona). Use when: invoking a named persona ("as platform, review this auth flow"), applying a specific perspective or role lens to a task, listing available personas, defining a house persona that encodes a failure-mode defense, or reviewing work through a specific role's perspective.
development8
test-task-factory
Generates test task creation parameters from a detected change type and implementation task subject. Routes to the correct test type (visual/endpoint) and produces TaskCreate-ready subjects, descriptions, and metadata. Use when: creating test tasks after change-type detection, QE task generation, "test task factory", "create test tasks", "generate QE tasks", or after change-type-detector classifies files as ui/api/both.
development8
scaffold
Component scaffolding toolkit for creating skills, agents, commands, 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.
tools8
wicked-garden-domain-modeler
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).
development8
wicked-garden-domain
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.
tools8
wicked-garden-domain-extractor
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).
tools8
wicked-garden-core
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.
tools8
wicked-garden-wickedizer
Writing humanizer / AI-tell remover (the team's house writing-cleanup skill). Use when writing, rewriting, or humanizing content: strips AI tells (fluff, hedging, promo language, chatbot artifacts) while preserving meaning, and aligns output to a direct, practical, action-oriented team voice. Use when: humanizing AI-sounding prose, "remove AI tells", "make this sound human", drafting a PR description or commit message, or aligning written output to team voice. Aliases: humanize, humanizer, dejargonize, writing-cleanup.
development8
wicked-garden-ground
Grounding / assumption-check: pull deeper context from brain + 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 brain memories, 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 Agent(Explore)), or fetching specific symbols (use wicked-brain:search directly).
development8
wicked-garden-integration-discovery
Capability router that decides which tools, skills, and agents to use for a task. Discovers CLI tools in PATH alongside MCP servers, skills, and agents. Reduces cognitive load on the main agent by making tool selection decisions. Use when: planning work in an unfamiliar domain, deciding which tools or agents fit a task, or discovering installed CLIs / MCP servers.
tools8
wicked-garden-worktrees
Git worktree hygiene — when to create, how to clean up, and what fails silently. Captures three classes of bug that recur with worktree-based agent isolation: subagent dangling commits, orphan branches with unique work, and time-sensitive dangling-commit garbage collection. Includes detection commands, the salvage decision flow, and the trust-but-verify rule for subagent commit reports. Use when: a subagent reports a commit SHA, after a worktree-based agent finishes, cleaning up `.claude/worktrees/`, salvaging old crew worktrees, "is this branch in main?", verifying agent-claimed commits actually landed, planning multi-agent parallel work in worktrees.
development8
wicked-garden-archetype
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).
tools8
wicked-garden-engineering-conformance-reviewer
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.
development8