mikeparcewski/wicked-garden / skills/engineering
wicked-garden-engineering
VerifiedEngineering domain skill: code review, architecture analysis, debugging, implementation planning, documentation, release PRs and scaffolds. Use when: "review this code / file / diff" (quality, patterns, maintainability; --focus, --persona, --scenarios); "review the architecture of X" / "evaluate component boundaries, coupling, or layer violations" (--scope module|service|system); "debug this error / bug / unexpected behavior" (root cause, reproduction, fix, prevention); "plan this change" / "implementation plan with file changes, risks and tests before writing code"; "generate API docs / README / guide / inline comments" (--type api|readme|guide|inline) or "docs drifted from code"; "prepare a release PR" (never tags or publishes); "scaffold a new CLI / service / library". NOT for reviewing an AI agent system (agentic review), a UI (product ux-review), a go/no-go verdict (archetype review), greenfield design (the solution-architect worker) or scaffolding a new MCP server (wicked-garden-mcp-scaffold).
Engineering
Senior engineering guidance on code quality, architecture, and implementation. The seven actions below run inline (no dispatch); genuinely structural, migration, or API-reference work hands off to the workers listed at the end.
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.
Routing
| Ask | Action |
|---|---|
| Code-level quality review of files or a diff | § review |
| Component/system-level architecture review | § arch |
| Bug / error / unexpected-behavior diagnosis | § debug |
| Implementation plan before writing code | § plan |
| Generate or refresh documentation | § docs |
| Prepare a release pull request (versions, changelog; never tags or publishes) | § release |
Start a new CLI, service or library (Kind: line in the brief) | § scaffold |
| Multi-file mechanical change (add-field/rename/remove) | patch |
Review disambiguation: this skill reviews source code. For an AI agent
system use agentic review, for a UI use product ux-review, and for a binding
go/no-go verdict use archetype review (see docs/domains.md → "review appears
in three domains"). arch is component/system-level review; review is
code-level; greenfield design is the architecture module.
review — senior-engineer code review
- Parse scope (path or git-diff target),
--focus,--persona, and--scenarios. - Read
refs/review.md(relative to this skill's base directory) — R1–R6 Bulletproof Coding Standards, T1–T6 Bulletproof Testing Standards, agent overstepping checklist, focus lane definitions, persona routing instructions, wicked-scenarios format, and output template. - Persona branch (only if
--persona <name>present): resolve the persona viawicked-garden run scripts/persona/registry.py --get {name} --json. If found, apply the review through that persona's frame. If not found, warn and fall through. - Read the target file(s) / diff. Apply R1–R6 to all code; add T1–T6 when
--focus testsor reviewing test files. If--focusgiven, deepen that lane. Flag agent overstepping (scope creep, commented-out code, over-engineering) withfile:linecitations. Flag every piece of custom code that duplicates a built-in of the chosen framework or library: cite the code and the built-in, and judge the author's stated reason (refs/review.md, "Duplicates of a built-in"). - Emit the standard Engineering Review output (Strengths, Issues table with rule + location,
Architecture Notes, Maintainability Concerns, Agent Overstepping, Recommendations).
If
--scenarios, append wicked-scenarios blocks for each Critical/High finding.
arch — architecture analysis
Use arch for component/system-level review; use review for code-level review.
- Parse
[target]and--scope(module | service | system; infer if absent from directory depth and file count). - Read
refs/arch.md— rubric, checklists, output formats, and architecture principles for both module/service and system scope. - Map the directory layout, entry points, key dependencies, and data flow of the target.
- Apply the scope-appropriate checklist from the rubric directly. Flag unauthorized architectural changes or scope creep when reviewing a diff.
- Emit the scope-appropriate output format (strengths, concerns table, recommendations, trade-off table, ADR candidates for system scope).
For genuinely structural greenfield design, hand off to
wicked-garden-engineering-solution-architect.
debug — systematic debugging session
- Parse the error message, symptom, or issue description.
- Run the hypothesis loop inline: gather context, form a hypothesis, test it, document the
root cause — the systematic method on every seat (
refs/debug.mdcarries the rubric). - Read
refs/debug.mdfor garden-specific heuristics: check the wicked-bus first, loom/vault availability for gate failures, cross-platform hook issues, and the standard debug output format. - Apply the six-step process. Read relevant files at error locations, search for related patterns, check logs if available.
- Emit the standard Debug Analysis output format (Symptom, Root Cause with confidence, Evidence, Reproduction Steps, Recommended Fix with rationale, Verification, Prevention).
- If the user approves the fix, implement it, add a regression test, and verify resolution.
Patterns and deeper process live in the debugging module.
plan — implementation planning
Analyze a change request against the current codebase and produce a detailed implementation plan
with specific file changes, risk assessment, and test recommendations. Distinct from the patch
module's patch-plan (propagation preview for mechanical patches — see
patch/SKILL.md); this plan produces a human implementation plan.
- Parse the change request: identify goal, scope, and constraints. Ask a clarifying question if the request is too vague to scope (e.g. no target file or system identified).
- Read
refs/plan.md— exploration checklist, risk assessment checklist, plan output format, and security/performance heuristics. - Explore the affected code: entry points, key files, callers, existing patterns, test coverage.
Use the
wicked-garden-searchskill'sblast-radiusaction on{symbol}for impact analysis. Check what the chosen framework or library already provides for the job, at the version the repo pins. The user and the steering policies choose the stack; the plan works inside that choice and does not swap it out. - Apply the risk assessment checklist (breaking changes, performance, security, data integrity, test gaps, deployment coordination).
- Emit the Implementation Plan output format: Summary, Scope (in/out), Built-ins Checked, Changes Required per file, Risk Assessment table, Test Plan, Rollout Considerations, Open Questions. Any custom code that duplicates a built-in states why the built-in does not fit.
- Present the plan and ask: "Ready to proceed with implementation, or would you like to adjust the approach?" Do not write any code until approved.
docs — documentation generation
- Parse
<file or component>and--type(api | readme | guide | inline). Infer if absent:.ts/.py/.go→ api or inline; top-level directory → readme; workflow request → guide. - Read
refs/docs.md— type-routing table, pre-generation checklist, API/README/guide/inline checklists, OpenAPI template, and quality standards. - Read the source code: public interfaces, function signatures, types, error conditions, and existing docs (check for drift from implementation).
- Apply the type-appropriate checklist and generate the documentation inline following the
output template in the rubric. API/reference docs hand off to
wicked-garden-engineering-api-documentarian. - Present the documentation for user review before writing to file. When writing: API docs →
docs/api/; READMEs → component root; guides →docs/guides/; inline → edit in-file with your file-edit tool.
Audit (coverage metrics) and sync (stale-docs detection) modes live in the docs module.
release — prepare a release pull request
- Read
refs/release.md— the last release and the range, the bump rule, every version-carrying file, lockfile re-stamps, the changelog cut, and the release record the fidelity check reads. - A NO-GO readiness verdict stops here: report its blockers. Never tag, publish, create a hosted release or merge; "tag it when you're done" is answered, not obeyed.
- Emit the release record in your output and the pull request body.
scaffold — start a new CLI, service or library
- Read
refs/scaffold.md— stack and target checks, built-ins first, the per-kind table (CLI, HTTP or worker service, library) and the scaffold record. The kind is the brief'sKind:line. - The stack is the design step's (or the repository's); never pick one. Never overwrite a file.
A new MCP server goes to
wicked-garden-mcp-scaffoldinstead. - Run the build and tests, then emit the scaffold record with their exit codes.
Knowledge modules
architecture · backend · frontend · integration · system-design · debugging · docs · large-scale-migration · patch · unit-test-quality
- refs/conformance.md — pattern-conformance review: load the applicable Pattern rules,
judge the artifact semantically per rule, emit
CONFORMANT/DRIFT/VIOLATION(report only, never gate).
Workers
| Skill | Hand off for |
|---|---|
wicked-garden-engineering-solution-architect | System design, structural trade-offs, greenfield architecture, ADRs |
wicked-garden-engineering-migration-engineer | Production schema/data migrations, expand-contract, deprecation paths |
wicked-garden-engineering-api-documentarian | OpenAPI specs, endpoint reference docs |
Hand-off — open the worker skill by name with the ask as the argument; on Claude Code this is the Skill tool, on any other seat open the named skill from your catalog and run it inline, keeping its output separate from yours, then continue here.
Frontend (React/CSS/browser), backend (APIs/databases/server-side), and debugging
(error investigation, root-cause analysis) are handled inline by this skill —
apply the relevant checklist from refs/.
Key principles
- Code quality: clear naming and organization, DRY, SOLID, consistent style.
- Architecture: design patterns, separation of concerns, component boundaries, dependency management.
- Maintainability: easy to understand, modify, and test; well-documented; deliberate error handling.
- Performance: efficient algorithms and data structures, resource management, caching strategies.
Review process
Use comprehensive checklists covering structure (patterns, abstractions, dependencies), quality (naming, duplication, style), error handling (recovery, messages), maintainability (clarity, configuration), performance (queries, data structures), and agent overstepping (unnecessary changes, commented-out code, scope creep). See refs/engineering-checklists.md for detailed review checklists and severity guidelines.
Output formats
Structured guidance for implementation planning (approach + steps) and code reviews (strengths, issues, recommendations). See refs/engineering-templates.md for output templates and focus areas.
Integration with wicked-crew
Engaged during the build phase (implementation guidance and pattern recommendations), the review phase (code quality and architecture review), and error recovery (when issues are encountered during development).
Notes
- Always explain the "why" behind recommendations.
- Be constructive, not critical.
- Offer alternatives with tradeoffs.
- Encourage questions and discussion.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the work | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation code | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |