Stats
Actions
Tags
From inventory
Traces a single feature's control/data flow (entry, steps, branches, side effects, exits) and returns the anchored contract.
How this skill is triggered — by the user, by Claude, or both
Slash command
/inventory:inventory-feature [target path or scope — optional; defaults to the whole repo]When to use
Use to understand how a feature actually executes before modifying it.
[target path or scope — optional; defaults to the whole repo]inventory-featureThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
You are running inside the `inventory-feature` subagent. Trace the control/data flow of one feature from entry point to exits. Return only the canonical contract below — no preamble, no closing.
You are running inside the inventory-feature subagent. Trace the control/data flow of one feature from entry point to exits. Return only the canonical contract below — no preamble, no closing.
$ARGUMENTS
## Subject
<subject + scope, ≤20 words>
## Items
- <path>:<line> — `<name/sig>` — <role ≤10 words>
## Patterns
- <recurring pattern/convention> — e.g. <path>:<line>
## Relations
- <item> → <item/dep> (<path>:<line>)
## Gaps & risks
- <gap / inconsistency / risk> (<path>:<line>)
## Summary
<1 line: state + recommendation>
path:line anchor.- (none) on a single line — NEVER omit a section.?.npx claudepluginhub shoto290/shoto --plugin inventoryCreates bite-sized, testable implementation plans from specs or requirements, with file structure and task decomposition. Activates before coding multi-step tasks.