ice-stage

name	ice-stage
description	Use Ice Stage when the best move is to change the board's traction: make motion fast, slippery, and harder to stop cleanly so both allies and opponents have to operate on altered movement physics.
version	0.1.0
author	mmbnchips
license	CC0-1.0
compatibility	Hermes Agent skills system
metadata	{"hermes":{"tags":["shipping-now","hybrid","control-and-terrain","control","terrain","positioning","room-control"],"homepage":"https://github.com/Hmbown/mmbnchips"}}

Ice Stage

Freeze the field so movement carries farther than intended and precise footing becomes the real problem.

What This Skill Does

Use Ice Stage when the best move is to change the board's traction: make motion fast, slippery, and harder to stop cleanly so both allies and opponents have to operate on altered movement physics. In this chip pack, Ice Stage is treated as a hybrid battle-chip procedure with a shipping-now delivery profile. Canonical reference input: Ice Stage. Hermes shelf: Control and Terrain.

When To Use

• The current problem is about bad footing, overcommitment, or uncontrolled momentum rather than ownership of space.
• You want to make the whole operating surface faster to cross but harder to navigate precisely.
• The right move is to expose who can handle slippery conditions and who depends on stable stopping points.

Prerequisites

• Name which part of this move is real tool use versus battle-chip framing before you act.
• 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 workflow, room, or surface whose movement rules should become slippery.
• Describe who is most likely to benefit from low-traction movement and who is likely to lose footing.
• State what kinds of overshoot, forced carry, or reduced precision are acceptable.
• Identify the tactical gain you want from changing traction instead of changing ownership.

Procedure

1. Restate the target, success condition, and no-touch boundaries before you spend the chip.
2. Collect the operator inputs below so the chip lands on the right panel.
3. Name the field, workflow, or decision surface whose traction you want to alter.
4. Define what sliding behavior should become easier and what precise movement should become harder.
5. Convert the board, then explain how operators should exploit or survive the new footing.
6. Package the result with concrete evidence, what stayed untouched, and the next recommended chip only if follow-up is truly needed.

Deliverables

• A board-wide change in operating conditions that reduces traction and increases carry-through motion.
• A short note on what actions now slide, overshoot, or require extra care.

Output Contract

• A clear description of how the field movement rules changed and what now counts as slippery behavior.
• An explanation of which moves become easier, which become riskier, and who is affected on both sides.
• A concrete recommendation for how to exploit the new low-traction terrain.
• An explicit note that precision costs went up along with speed or carry.

Do Not Use For

• Simple repositioning problems where one shove from Air Shot would solve it cleanly.
• Ownership disputes where the real need is to claim panels with Panel Grab or Area Grab.
• Recovery or repair work that depends on a calm, high-control operating surface.

Pair With

• Ice Stage + Air Shot: make footing unstable first, then use one shove to send the target sliding farther than normal.
• Ice Stage + Panel Grab: freeze the field, then claim the one stopping point or lane that still matters.
• Ice Stage + Time Bomb: reduce clean escape routes by making movement harder to stop before the delayed effect lands.

Pitfalls / Guardrails

• Keep the theatrical framing, but name the concrete mechanism that makes the chip useful right now.
• Do not use Ice Stage if the operator needs a stable work surface for delicate execution.
• If everyone on the field loses control equally and no advantage is created, the ice is wasted.
• If the problem is ownership rather than footing, switch to a grab chip instead.
• 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 the response changes movement physics or footing, not merely ownership or position labels.
• Confirm the new terrain creates a meaningful advantage for someone who understands the slip conditions.
• Confirm the costs of reduced precision and possible overshoot are named explicitly.
• Check which parts are concrete actions versus framing, so the operator can tell what is real now.

Example Invocation

Use Ice Stage on this workflow: make the whole process fast but slippery so overcommitted steps become obvious, then tell me how to exploit the new footing.
Use Ice Stage here to reduce precise stopping points across the board, but be honest about who on my side might also lose traction.