miaodx/intuitive-flow/intuitive-reduce-entropy

Intuitive Reduce Entropy

Use this skill to find a bounded set of changes that remove real maintainer or execution friction. Prefer deletion, reuse, and one canonical owner over new workflow, code, test, or documentation surfaces.

Modes

Pick the mode and discovery intensity (quick scan, selection scan, or saturation scan) and name them in the packet, with a redirect only when another mode or skill fits better.

Read First

Load only the reference needed for the active pass:

For broad repo scans, read the repo's thin orientation surface and run the bundled high-noise summary before searching planning archives, logs, generated trees, or other high-noise roots. Deep-read only enough to prove a candidate.

Candidate Gate

Every selected candidate must pass both gates:

1. Demand sanity: the change deserves to exist now. For additions, explain why

reuse, narrowing, deletion, or documentation cannot achieve the outcome. For removals, show why preserving the surface is stale, misleading, or costly.

1. Materiality: evidence shows false confidence, live source drift, a stale

reachable surface, real workflow friction, or recurring rediscovery.

Use scripts/materiality-gate.mjs when a deterministic gate helps compare a batch. Scripts provide evidence; they do not override repo facts or a required human decision.

Rank deletion and cleanup candidates in this order:

1. Stale surfaces with an active replacement.
2. Compatibility aliases, wrappers, or legacy paths without a live contract.
3. Duplicate owners for one concept, state envelope, fixture, or rule.
4. Pass-through modules and tests/docs that keep stale concepts alive.
5. Bounded source-of-truth or verification drift.

Formatting, line motion, speculative abstraction, and taste are not selected candidates. Park work that needs product direction, public migration approval, credentials, hardware, paid services, or unavailable proof.

Ownership Boundary

• This skill owns discovery, ranking, evidence, and routing.
• $intuitive-refactor owns mutation of selected cleanup seams.
• $intuitive-doc, $intuitive-init, and $intuitive-tests own their

specialist surfaces.

• $grill-with-docs-batch owns unresolved human/domain decisions.
• $intuitive-preflight owns the approved execution contract.
• $intuitive-flow starts only after that contract is approved.

Use the shared delegation policy for independent read-only probes. Keep the main session responsible for ranking, architecture decisions, and final synthesis.

Stop And Handoff

Stop when a decision-complete ranked packet is ready, or when a saturation pass finds no new material candidate. The user selects the subset and approves implementation. If nothing passes, say Selected candidates: none and stop there, with no gate, commit, or follow-up proposal.

End with a packet the next owner can act on without repeating the audit. Always include selected candidates (with evidence, specialist owner, and proof command), Recommended next action:, and Shortcut: (a ready-to-paste command, or park/none when there is no useful next step). Add parked items or saturation status only when they carry information.