Skip to content

mikeparcewski/wicked-garden / skills/core

wicked-garden-core

Flagged

Core utility surface for the wicked-garden plugin: help/overview, first-run setup + codebase onboarding, the wicked-* peer installer, selective state reset, the where-am-i path manifest, and structured issue filing. Use when: "wicked-garden help", "show wicked-garden commands", "what can wicked-garden do", "set up wicked-garden", "setup", "--reconfigure", "onboard this codebase", "install wicked tools", "add peers", "install layers", "reset wicked-garden", "clear state", "--list-projects", "where am I", "path manifest", "report issue", "file a bug", "--list-unfiled", or any former /wicked-garden:{help|setup|install|reset| where-am-i|report-issue} invocation.

FileKindSize
SKILL.mdskill md13.4 KB
refs/install.mdmarkdown5.3 KB
refs/inventory-report.mdmarkdown1.3 KB
refs/report-issue.mdmarkdown8.4 KB
refs/reset.mdmarkdown4.3 KB
refs/runtime.mdmarkdown4.2 KB
refs/setup.mdmarkdown23.5 KB
refs/templates.mdmarkdown2.3 KB

refs/templates.md

View on GitHub
# Issue-body templates (report-issue action)

Loaded by `refs/report-issue.md` § 5 (Compose Issue). Pick the template that
matches the issue type parsed in § 1, fill the fields collected in § 2, then
append the research findings from § 3 and the SMART-validated acceptance
criteria from § 4. `{…}` are fill-ins; drop any **optional** line the user
left blank; drop any research section that found nothing.

Every issue body opens with the same reporter line and closes with the same
acceptance-criteria + desired-outcome block.

## Header (all types)

```markdown
> Reported via the wicked-garden-core `report-issue` action (manual report).
```

## Bug Report (label: `bug`)

```markdown
> Reported via the wicked-garden-core `report-issue` action (manual report).

## Steps to Reproduce
1. {step 1}
2. {step 2}
3. {…}

## Expected Behavior
{what should have happened}

## Actual Behavior
{what actually happened}

## Impact
{severity / who is affected — omit if not provided}
```

## UX Friction Report (label: `ux`)

```markdown
> Reported via the wicked-garden-core `report-issue` action (manual report).

## What You Tried
{the intent and actions taken}

## What Happened Instead
{the confusing or unexpected result}

## Suggested Improvement
{how it could be better — omit if not provided}
```

## Unmet Outcome Report (label: `gap`)

```markdown
> Reported via the wicked-garden-core `report-issue` action (manual report).

## Goal
{what the session was trying to achieve}

## What Happened
{the actual result — where it fell short}

## What Would Have Helped
{suggestions — omit if not provided}
```

## Research findings (append after the type-specific body)

Append only the sections that produced results in § 3. Use the exact section
markup already specified in `refs/report-issue.md` §§ 3a–3c:

- **Duplicate Check** — `## Duplicate Check` (always appended; states matches or
  "No open duplicates detected.")
- **Related Code** — `## Related Code` (only when relevant files were found)
- **Prior Context** — `## Prior Context` (only when relevant memories were found)

## Closing block (all types)

```markdown
## Acceptance Criteria
- [ ] {SMART-validated criterion 1}
- [ ] {SMART-validated criterion 2}
- [ ] {…}

## Desired Outcome
{one-sentence statement of the outcome that would close this issue}
```
receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 322kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 322kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 322kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 322kUpdated Claude CodeCodexVerifiedInstall