mikeparcewski/wicked-garden / skills/core
wicked-garden-core
FlaggedCore 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.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 13.4 KB |
| refs/install.md | markdown | 5.3 KB |
| refs/inventory-report.md | markdown | 1.3 KB |
| refs/report-issue.md | markdown | 8.4 KB |
| refs/reset.md | markdown | 4.3 KB |
| refs/runtime.md | markdown | 4.2 KB |
| refs/setup.md | markdown | 23.5 KB |
| refs/templates.md | markdown | 2.3 KB |
refs/inventory-report.md
View on GitHub---
codebook: inventory-report
version: 1
block: wicked-inventory
---
# Inventory report
When your step lists things a later step acts on (issues, PRs, files, endpoints, records), say
whether the list is complete. End your reply with one block per source, nothing after them:
```wicked-inventory
{"source": "gh issue list -R owner/repo --state all", "answered": "partial", "listed": 9, "expected": 10, "unread": ["issue #936: not in the API page"]}
```
- `source`: the command, API or path you listed from, exactly as you ran it.
- `answered`: `full` only when the source returned everything, `unread` is empty, and `listed`
equals `expected` (or the source reports no total and you paged to the end). `partial` when
some of it could not be read. `none` when the source failed.
- `listed`: how many you have.
- `expected`: the total the source reported, or `null` when it reports none.
- `unread`: what you could not read and why. Never leave out a failure.
A fallback (another tool, a web page, a cached copy) is a different source: name it in `source`
and say `partial` unless you checked it against the first one. crew reads the block and serves it
with the run, so a reviewer sees an incomplete list without reading your reply. A step that acts on
a list it was handed says so first when that list is not `full`.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| 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 implementation | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| 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 fallback | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| 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 always | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |