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).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 12.7 KB |
| refs/arch.md | markdown | 4.5 KB |
| refs/conformance.md | markdown | 3.8 KB |
| refs/debug.md | markdown | 4.0 KB |
| refs/docs.md | markdown | 5.8 KB |
| refs/engineering-checklists.md | markdown | 2.7 KB |
| refs/engineering-templates.md | markdown | 1.2 KB |
| refs/plan.md | markdown | 4.1 KB |
| refs/release.md | markdown | 7.4 KB |
| refs/review.md | markdown | 7.4 KB |
| refs/scaffold.md | markdown | 5.6 KB |
refs/plan.md
View on GitHub# plan — implementation planning rubric
Checklist and output format for generating detailed implementation plans with file changes,
risk assessment, and test recommendations before writing code.
## Pre-plan exploration checklist
Before drafting a plan, explore the codebase to understand:
- [ ] Files that implement the functionality being changed
- [ ] Direct callers and consumers of those files (blast radius)
- [ ] Existing patterns and conventions (naming, error handling, module structure)
- [ ] Test patterns and coverage for affected areas
- [ ] Any feature flags or config that gates the change
- [ ] What the chosen framework or library already provides for the job, at the version the
repo pins (its docs or source). The user and the steering policies choose the stack
(wicked-core rule POL-2101); plan inside that choice
Use the `wicked-garden-search` skill's `blast-radius` action on `{symbol}` to find all call sites. Fall back to
the estate MCP SearchEntity tool, or Grep when the index is unavailable.
## Risk assessment checklist
For each change, evaluate:
| Risk Category | Questions to ask |
|---------------|-----------------|
| Breaking changes | Does this change any public interface, event schema, or API contract? |
| Performance | Does this add I/O, a loop, or a DB query to a hot path? |
| Security | Does this touch auth, session, credentials, or user-supplied input? |
| Data integrity | Does this touch a migration, schema, or data transform? |
| Test gaps | Are there untested edge cases that the change could break? |
| Deployment | Does this require a coordinated deploy (e.g. schema before code)? |
## Implementation plan output format
```markdown
## Implementation Plan: {title}
### Summary
{1-2 sentence overview of what changes and why}
### Scope
- **In scope**: {what will change}
- **Out of scope**: {explicitly NOT changing}
### Built-ins Checked
- {Framework/library @ pinned version}: {what you read} → {what it already provides for this job}
- Custom code that duplicates a built-in: {none, or what and why the built-in does not fit}
### Changes Required
#### 1. {path/to/file.ext}
**Purpose**: {why this file changes}
**Changes**:
- {Specific change — e.g., "Add null check before accessing `.id`"}
- {Add / Modify / Remove — be concrete}
#### 2. {path/to/another-file.ext}
**Purpose**: {why}
**Changes**:
- {change}
### Risk Assessment
| Risk | Likelihood | Impact | Mitigation |
|------|------------|--------|------------|
| {risk} | Low/Med/High | Low/Med/High | {action} |
### Test Plan
- [ ] Unit: {what unit behavior to cover}
- [ ] Integration: {what flow to exercise end-to-end}
- [ ] Manual verification: {scenario to check in the running app}
- [ ] Regression: {existing tests to re-run}
### Rollout Considerations
{Any deployment notes: feature flags, migration order, canary, backward compatibility window}
### Open Questions
- {Question that needs resolution before implementation starts}
```
## Planning heuristics
**Start with the test** — if you can't describe what test would fail without this change,
the requirement isn't specific enough yet.
**One file at a time** — each file in "Changes Required" should have its own purpose;
if two files have the same purpose, merge them in the plan.
**Flag unauthorized scope** — if exploration reveals the change will require touching
files well outside the stated scope, surface this before proceeding.
**Security checklist for any change touching auth, input, or data**:
- [ ] No credentials logged
- [ ] Input validated before use
- [ ] Authorization checked (not just authentication)
- [ ] SQL/injection-safe if DB queries change
- [ ] No plaintext secrets in new config
**Performance checklist for any change on a hot path**:
- [ ] No new synchronous I/O added to request path
- [ ] No N+1 query pattern introduced
- [ ] Timeout specified on any new external call
- [ ] No unbounded collection loaded into memory
## After presenting the plan
Ask:
> Ready to proceed with implementation, or would you like to adjust the approach?
If approved, execute using `engineering:apply` or the build archetype
(`/wicked-garden-archetype build`).
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 |