Hmbown Fast Gauge
Speed up the cycle so the next hand arrives sooner.
What This Skill Does
Use Fast Gauge when the loop itself is healthy but too slow, and you need quicker draws, shorter iteration, or faster feedback. In this chip pack, Fast Gauge is treated as a metaphorical battle-chip procedure with a shipping-now delivery profile. Canonical reference input: Fast Gauge. Hermes shelf: Tempo and Hand Management.
When To Use
- The bottleneck is tempo, not direction.
- The team or toolchain can handle a faster cadence.
- You want more iterations in the same time window.
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 exact loop to accelerate.
- State the current cycle time or waiting point.
- Identify one friction source to remove or compress.
- Name the quality signal that must not degrade.
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.
- Identify the loop you want to accelerate.
- Remove one friction source or shorten one wait.
- Check that signal quality survived the speed-up.
- Package the result with concrete evidence, what stayed untouched, and the next recommended chip only if follow-up is truly needed.
Deliverables
- A tempo improvement to a clear loop.
- A before-and-after note about cycle time.
Output Contract
- A named target loop and one specific tempo intervention.
- A before/after cycle-time expectation or proxy.
- A quality protection check so speed does not become sloppiness.
- A revert condition if acceleration harms outcomes.
Do Not Use For
- Loops that are unclear, disputed, or structurally broken.
- Situations where the real issue is bad prioritization, not speed.
- Pushing humans or systems past safe review capacity.
Pair With
- Use Slow Gauge instead when the room is too fast to reason safely.
- Use Full Custom after Fast Gauge if the loop is fast enough but the available options are still stale or poor.
- Pair Fast Gauge with Cannon when faster cadence exposes one repeated narrow fix worth taking immediately.
Pitfalls / Guardrails
- Keep the metaphor anchored to a real operator move instead of drifting into lore.
- Do not speed up a loop that is already confused.
- If quality falls apart under faster gauge, revert.
- 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 loop got faster in a measurable or observable way.
- Confirm error rate, rework, or confusion stayed flat or improved.
- Confirm the acceleration hit one healthy loop instead of speeding up the whole room blindly.
- Check that the metaphor still maps cleanly to a real operator mechanism.
Example Invocation
Use Fast Gauge on our PR feedback loop. Identify one wait state to compress, name the quality metric we will protect, and give me a reversible plan.
Use Fast Gauge on this support-triage workflow: show the current bottleneck, the smallest safe acceleration move, and how we will verify we did not just create sloppier work.