
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"
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"
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"
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"
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"
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
--- name: large-scale-migration description: 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/fra
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.
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
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".
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"
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"
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"
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"
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.
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"
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.
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"
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".
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.
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.
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"
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.
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
Pull deeper context from brain + bus when uncertain. 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. Returns relevant brain memories, recent bus events, and linked priors ranked by relevance — not a wall of text. 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).
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"
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).
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).
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.
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.
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).
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.
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.
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"
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).
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".
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.
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"
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".
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).
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).
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"
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).
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).
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).
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", "rename everywhere", "propagate change", "generate migration", "update all references". This is the CODE MUTATION counterpart to wicked-garden:search (which is read-only).
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"
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"
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"
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.
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".
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.
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.
Multi-model AI collaboration: discover installed LLM CLIs and orchestrate council sessions, cross-model reviews, and diverse perspective gathering. Detects codex, copilot, gemini, opencode, pi, aider, llm, aichat, and goose CLIs at runtime via PATH discovery. Decisions stored in wicked-brain:memory. Transcripts persisted via jam scripts. Use when: running a council session across multiple LLM CLIs, getting a second opinion from a different model on a decision, or doing a cross-model code or architecture review.
Diagnose missing tools and dependencies, offer to install them. Use when: "command not found", "ModuleNotFoundError", "missing tool", "install dependency", "prereq check", "setup validation"
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.
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"
On-demand persona invocation system for applying named perspectives to any task. Use when: invoking a named persona via persona:as, defining or listing personas, or reviewing work through a specific role's perspective.
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, or correlating production status with recent changes.
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 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 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).
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"
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).
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.
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).
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.
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"
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.
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.
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:traces command) or audit evidence (use platform/audit).
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.
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"
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.
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.
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".
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).
On-demand context assembly over wicked-brain + wicked-garden:search. v6 replaced the v5 push-model orchestrator (deleted in #428) with a pull-model skill — subagents call this skill directly when they need a context briefing rather than having one pushed onto every prompt. Use when: gathering a context briefing before a task, resuming work after a session break, or assembling background on an unfamiliar area.
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.
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).
Contextual command discovery — suggests related commands based on what was just used. Discovers relationships dynamically from command/skill content, not a static map. Invoked by the Stop hook and smaht:briefing to surface one relevant suggestion.
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).
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"
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.
--- name: workflow description: | 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). context: fork **Plain:** wicked-crew v6 — propose-process rubric picks phases and rigor tier; gates are hard
This skill should be used when writing, rewriting, or humanizing content. Removes AI tells while preserving meaning. Aligns output to team voice: direct, practical, action-oriented. Use when: humanizing AI-sounding prose, drafting a PR description or commit message, or aligning written output to team voice.
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.
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.
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.
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"
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"
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.
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)
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"
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"
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".
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"
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".
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"
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, or asking whether the right thing is being asked at all.
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.
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).
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).
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"
v11 work-shape archetype runner. When a prompt has been routed to one of the 9 archetypes (triage, explore, specify, decide, ship, review, incident, build, migrate), 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 when one of the per-archetype slash commands resolves to this skill.
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.