fast-gauge

Identify a friction source in a healthy loop and implement a speed-up.

Updated Apr 11, 2026
One-click install
npx skills add https://github.com/Hmbown/mmbnchips --skill fast-gauge
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fast-gauge
Source: https://github.com/Hmbown/mmbnchips/tree/main/generated/codex/fast-gauge
Command: npx skills add https://github.com/Hmbown/mmbnchips --skill fast-gauge

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Speed up the cycle so the next hand arrives sooner.

Core Features & Use Cases

  • Identify the loop you want to accelerate.
  • Remove one friction source or shorten one wait.
  • Check that signal quality survived the speed-up.

Quick Start

Apply Fast Gauge to accelerate one healthy loop and confirm that the tempo gain came from genuine speed-up, not sloppier work.

Frequently Asked Questions about fast-gauge

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I improve software engineering workflow speed without sacrificing quality?

To improve workflow speed without sacrificing quality, you accelerate a healthy feedback loop by identifying a single friction source, implementing the speed-up, and verifying that signal quality remains intact.

What is a healthy feedback loop in software development?

A healthy feedback loop is a workflow cycle where signal quality is accurate, but the tempo is slow. It becomes a target for optimization when you need quicker iterations without introducing sloppier work.

How do I shorten cycle time and increase responsiveness in a development loop?

You shorten cycle time by removing one specific wait or friction source from the loop. This ensures the next hand arrives sooner while maintaining the integrity of the original signal.

When should I apply feedback loop optimization techniques?

Apply feedback loop optimization techniques when your loop is healthy but slow and you need quicker iterations. Do not use it if the loop is already fast but producing low-quality signals.

How do I verify that a tempo gain came from genuine speed-up?

You verify a genuine tempo gain by checking that signal quality survived the speed-up. This confirms the cycle time reduction came from removing friction, not from sloppier work.