Hmbown Panel Grab
Take one square of the field and make it yours.
What This Skill Does
Use Panel Grab for narrower room control when a single lane, dependency, or decision surface matters more than broad expansion. In this chip pack, Panel Grab is treated as a metaphorical battle-chip procedure with a shipping-now delivery profile. Canonical reference input: Panel Grab. Hermes shelf: Control and Terrain.
When To Use
- You only need one extra lane to proceed.
- A small ownership change is safer than a broad takeover.
- The system is tight enough that one panel changes the fight.
Prerequisites
- These procedures rely on the normal tools already present in the active Hermes runtime; this repo does not ship a separate integration layer.
Operator Inputs
- Name the one lane, dependency, panel, or ownership edge that matters most.
- Explain why that single capture is enough to unlock progress.
- Describe the exact next action Hermes should take advantage of once the panel is yours.
- Provide the practical signal that the narrow grab succeeded.
Procedure
- Restate the target, success condition, and no-touch boundaries before you spend the chip.
- Collect the operator inputs below so the chip lands on the right panel.
- Find the exact panel worth stealing.
- Take that panel and no more.
- Exploit the new lane immediately.
- Package the result with concrete evidence, what stayed untouched, and the next recommended chip only if follow-up is truly needed.
Deliverables
- A narrowly scoped ownership or dependency adjustment.
- A note about why that single panel mattered.
Output Contract
- One narrowly scoped ownership, access, or dependency adjustment.
- A brief explanation of why that exact panel mattered more than broader expansion.
- A clear note on the next step now unlocked by the grab.
- No drift into full-field takeover unless the operator explicitly changes chips.
Do Not Use For
- Room-control problems that clearly need multiple surfaces reclaimed.
- Tasks where the bottleneck is not actually ownership, access, or lane control.
- Situations where capturing one panel creates obligations larger than the original problem.
Pair With
- After Panel Grab, switch to Cannon when the captured lane now gives you one clean direct action.
- After Panel Grab, switch to Sword when the newly opened lane exposes a single local block that should be cut out.
- After Panel Grab, switch to Area Grab when one panel was not enough and the operator still lacks room.
Pitfalls / Guardrails
- Keep the metaphor anchored to a real operator move instead of drifting into lore.
- Do not convert Panel Grab into Area Grab out of impatience.
- Avoid stealing panels that create new hidden obligations.
- Keep the chip metaphor anchored to a real operating move; do not let flavor substitute for procedure.
Verification
- Check that the response includes every promised deliverable and leaves an inspectable audit trail.
- Check that confirmed facts, assumptions, and proposed follow-up are visibly separated.
- Confirm Hermes captured exactly one meaningful lane or boundary and did not broaden scope.
- Confirm the output explains why this panel was the highest-leverage one.
- Confirm the newly opened next step is concrete and immediately actionable.
- Check that the metaphor still maps cleanly to a real operator mechanism.
Example Invocation
Use Panel Grab to secure the one dependency boundary blocking this release task, then show the exact next step that becomes possible.
Use Panel Grab on this repo decision: capture one clear ownership lane without redesigning the whole structure.