wicked-garden-crew-implementer

wicked-garden-crew-implementer is a skill for Claude Code from mikeparcewski/wicked-garden. It costs 70 tokens per session (1,393 once invoked), scanned A, original, MIT.

An implementation workflow for carrying out approved software designs and test plans. It organizes work into tasks and can dispatch independent tasks in parallel.

In plain words
What is it for?
Use it to build features from design documents, follow test scenarios, divide work into atomic tasks, manage dependencies, and implement independent pieces concurrently.
Why use it?
It helps keep implementation tied to agreed designs, acceptance criteria, dependencies, and safety rules. It also provides a way to track progress across the work.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: model in frontmatter; mentions subagents; mentions Claude Code.

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

Good fit Use it to build features from design documents, follow test scenarios, divide work into atomic tasks, manage dependencies, and implement independent pieces concurrently.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/mikeparcewski/wicked-garden/crew-implementer
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 crew-implementer
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 148 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-crew-implementer

README.md
[![agentmods](https://agentmods.dev/badge/skills/mikeparcewski/wicked-garden/crew-implementer/github.svg)](https://agentmods.dev/skills/mikeparcewski/wicked-garden/crew-implementer)
Your own site
<a href="https://agentmods.dev/skills/mikeparcewski/wicked-garden/crew-implementer"><img src="https://agentmods.dev/badge/skills/mikeparcewski/wicked-garden/crew-implementer/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-crew-implementer

Your own site · 80×15
<a href="https://agentmods.dev/skills/mikeparcewski/wicked-garden/crew-implementer"><img src="https://agentmods.dev/badge/skills/mikeparcewski/wicked-garden/crew-implementer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 70 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,393 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 2 findings, up to medium

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • medium Excessive Agency · line 6
    Skill selects an external model or provider that may use a different account or billing plan than the operator expects. Undisclosed model switches can cause unexpected cost or quota consumption.
    Fix: Remove the model/provider override or disclose it prominently and require explicit operator approval before invoking an external coding CLI or billed model.
  • medium analysis-evasion · line 1
    Suspicious Unicode normalization or mixed-script content
    Fix: Review the flagged content for security risks. Ensure no credentials, secrets, or sensitive data are exposed.
How audits are shown
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.00070 $0.01393
Opus 5 $0.00035 $0.00696
Sonnet 5 $0.00014 $0.00279
Haiku 4.5 $0.00007 $0.00139

Measured 9d ago against content hash e635cac23280, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

wicked-garden-crew-implementer scanned grade A with 1 finding 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 9d ago.

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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

- Verification: {command run + output excerpt, e.g. curl response or script output}
skills/crew-implementer/SKILL.md · 174 lines

How it starts

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

Implementer

You execute implementation tasks according to approved designs and test strategies.

Your Role

  1. Implement features according to design documents
  2. Follow test scenarios as acceptance criteria
  3. Track progress via Claude's native task tools (TaskUpdate)
  4. Respect guardrails and safety boundaries

Implementation Process

1. Understand the Task

Read from phase artifacts:

  • phases/design/ - Architecture and approach
  • phases/qe/ - Test scenarios (acceptance criteria)
  • outcome.md - Success criteria

2. Plan Implementation

Break down into atomic tasks:

  • Each task should be completable in one step
  • Create tasks with TaskCreate using phase-prefixed subjects
  • Set dependencies with addBlockedBy/addBlocks

Identify independent units of work. Tasks that touch disjoint files, do not share state, and have no blockedBy relationship to each other are independent. Mark them as such in the plan.

3. Execute

Default: parallel dispatch when independent. When you are spawned by phase-executor with phase_executor_may_delegate=true (build / test phases) and you have N >= 2 independent sub-tasks (no shared file edits, no producer → consumer ordering), dispatch them in a single-message multi-Task batch. Serial execution is allowed only when:

  • One sub-task's output is a documented input to another (blockedBy set), or
  • Sub-tasks edit the same file where order matters, or
  • You record a principled serial_reason in your return summary.

A serial run with no documented reason is a protocol violation — phase-executor will fail the parent execution with parallelization-check-missing (SC-6 / AC-α10). When you are dispatched as a single sub-task by phase-executor, you do not re-dispatch — execute the assigned slice directly.

For each task:

  1. Start: Call TaskUpdate(taskId="{id}", status="in_progress")
  2. Read relevant code context
  3. Make focused changes
  4. Verify against test scenario
  5. Complete: Call TaskUpdate(taskId="{id}", status="completed", description="{original description}\n\n## Outcome\n{what was done, decisions made, lessons learned}")

Read the full file on GitHub · 174 lines

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. 9d ago First seen · 174 lines · 70 tokens per session scan A e635cac23280

Subscribe to this mod's changes

wicked-garden-crew-implementer is a skill published in the GitHub repository mikeparcewski/wicked-garden (9 stars, last pushed today), licensed MIT. It adds 70 tokens to every session and 1,393 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

recipe-create-meet-space

Create a Google Meet meeting space and share the join link.

googleworkspace/cli · 18 tokens

workthreads

SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…

specstoryai/getspecstory · 126 tokens

atmos-config

Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.

cloudposse/atmos · 31 tokens

story-readiness

Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…

Donchitos/Claude-Code-Game-Studios · 77 tokens

autotask-creator

Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.

Orkas-AI/Orkas · 5 tokens

monorepo-management

Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.

wshobson/agents · 54 tokens