wicked-garden-product

wicked-garden-product is a skill for Claude Code from mikeparcewski/wicked-garden. It costs 190 tokens per session (4,381 once invoked), scanned A, original, MIT.

A single product-planning entry point for accessibility checks, acceptance criteria, stakeholder alignment, customer-feedback analysis, user-experience work, and visual review.

In plain words
What is it for?
It is for running product strategy and alignment work, analysing customer feedback, defining requirements, reviewing UX and accessibility, and checking visual design.
Why use it?
It puts related product tasks behind one set of actions and supporting guidance, so teams can handle requirements, research, design, and validation in one workflow.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: mentions subagents; mentions Claude Code.

Part of the wicked-garden plugin — 145 skills, 5 commands, 1 agent, 13 hooks shipped together

Good fit It is for running product strategy and alignment work, analysing customer feedback, defining requirements, reviewing UX and accessibility, and checking visual design.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/mikeparcewski/wicked-garden/product
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add mikeparcewski/wicked-garden --skill product
Clone the repo
git clone --depth 1 https://github.com/mikeparcewski/wicked-garden

Made for: Claude Code.

Or install wicked-garden, the plugin that ships this one along with the rest of its 145 skills, 5 commands, 1 agent, 13 hooks.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for wicked-garden-product

README.md
[![agentmods](https://agentmods.dev/badge/skills/mikeparcewski/wicked-garden/product/github.svg)](https://agentmods.dev/skills/mikeparcewski/wicked-garden/product)
Your own site
<a href="https://agentmods.dev/skills/mikeparcewski/wicked-garden/product"><img src="https://agentmods.dev/badge/skills/mikeparcewski/wicked-garden/product/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for wicked-garden-product

Your own site · 80×15
<a href="https://agentmods.dev/skills/mikeparcewski/wicked-garden/product"><img src="https://agentmods.dev/badge/skills/mikeparcewski/wicked-garden/product.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 190 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,381 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00190 $0.04381
Opus 5.5 $0.00076 $0.01752
Sonnet 5.5 $0.00038 $0.00876
Haiku 4.5 $0.00019 $0.00438

Measured 1mo ago against content hash 08a7f6f18502, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

wicked-garden-product scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

The scan reads SKILL.md. This mod also ships 4 executable files (imagery/scripts/analyze.sh, imagery/scripts/edit.sh, imagery/scripts/generate.sh, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/product/SKILL.md · 190 lines

How it starts

The opening of the file, as written. The whole thing — 190 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Product Domain

One entry point for the product domain. Pick the action, parse its args, load its ref, apply it inline. Only strategy --focus all and ux-review --focus all dispatch.

Runtime

Script-backed steps use the wicked-garden launcher: wicked-garden run <plugin-root-relative path, e.g. scripts/…> [args]. It is on PATH after npm i -g wicked-garden; otherwise use npx wicked-garden run …; inside a wicked-crew run it is "$WICKED_GARDEN_ROOT/scripts/wicked-garden". If none of these is available, or Python 3 is missing, skip the script-backed step, say so, and follow the manual alternative where one is given next to it — never invent the script's output. Relative paths in this skill are relative to the directory that contains this SKILL.md.

Action router

Action Use for Args Ref
a11y Accessibility audit: WCAG 2.1 AA, keyboard, screen reader, contrast <target> [--level A|AA|AAA] [--quick] refs/a11y.md
acceptance Define testable acceptance criteria from requirements/design <path> [--story US-ID] [--feature name] [--format gherkin|table|markdown] [--scenarios] refs/acceptance.md
align Stakeholder alignment: surface concerns, map trade-offs, build consensus [target-doc] [--stakeholders] [--focus concerns|tradeoffs|conflicts] [--conflict] refs/align.md
analyze Customer-voice pipeline 2/3: themes, sentiment, trends [--theme X] [--sentiment pos|neg] [--trend period] [--segment] refs/analyze.md
elicit Turn a vague ask into user stories + AC [target-doc] [--interactive] [--personas] [--scope] refs/elicit.md
listen Customer-voice pipeline 1/3: aggregate feedback from sources [--capability type] [--days N] [--since] [--tags x,y] [--limit N] refs/listen.md
mockup ASCII wireframe / HTML mockup / annotated spec <description-or-target> [--format ascii|html|spec] [--fidelity low|medium|high] refs/mockup.md
screenshot Multimodal UI review from image files <image-path> [<reference-path>] refs/screenshot.md
strategy Strategic analysis: ROI, value, market, competitive <target> [--focus roi|value|market|competitive|all] [--quick] refs/strategy.md
synthesize Customer-voice pipeline 3/3: prioritized recommendations [--priority high|medium|low|critical] [--feature X] [--format brief|detailed] refs/synthesize.md
ux Create or analyze user flows / IA / interaction patterns <target-or-description> [--mode create|analyze] refs/ux.md
ux-review Broad design audit: flows + UI + a11y + research, score 1-5 per lens <target> [--focus flows|ui|a11y|research|all] [--quick] refs/ux-review.md
visual-direction Reason from content structure to visual form (five questions) <section-or-description> [--skip-to N] visual-direction/SKILL.md

Read the full file on GitHub · 190 lines

Files

What ships with it

60 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 1mo ago Changed · -11 lines 08a7f6f18502
  2. 1mo ago Changed 151037369858
  3. 1mo ago First seen · 201 lines · 190 tokens per session scan A e94d06bb2ba0

Subscribe to this mod's changes

wicked-garden-product is a skill published in the GitHub repository mikeparcewski/wicked-garden (9 stars, last pushed today), licensed MIT. It adds 190 tokens to every session and 4,381 once invoked, about $0.0008 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.

Related

Other skills, from other repositories

acceptance-criteria-gwt

Use when writing acceptance criteria for a task - express each as an observable Given/When/Then that QA can execute, including negative cases.

makifbaysal/tasktrooper · 34 tokens

pm-uat-review

Use when a task is in pmuat - verify every acceptance criterion and the human's comments yourself in the browser, on a device, or over a loopback HTTP request, record a verdict per criterion, then move to humanuat or needrevision.

makifbaysal/tasktrooper · 56 tokens

qa-verify-before-verdict

Use before any reviewcriterion approval or column move - the evidence each verdict needs, how to treat skipped, blocked and intermittent cases, and which exit a blocker takes.

makifbaysal/tasktrooper · 40 tokens

retest-after-revision

Use when the task came back to QA after needrevision - what to re-run, what may carry over, and how to keep old passes from approving new code.

makifbaysal/tasktrooper · 38 tokens

vibe-workstream-orchestration

Runs a multi-phase project from an orchestrating main thread that plans, routes and verifies but does not build. Defines a few long-lived workstreams, each owning a file area end to end in its own worktree, and routes every follow-up to the owning agent instead of spawning a one-off. Covers base-SHA recording…

ash1794/vibe-engineering · 115 tokens

vibe-requirements-validator

Validates PRD, user stories, or feature requirements against SMART criteria. Use when reviewing requirements to catch vagueness before it causes expensive rework.

ash1794/vibe-engineering · 38 tokens