WFGY method

WFGY (Wan Fa Gui Yi, "all methods return to one") is a reasoning-drift-control technique from onestardao/WFGY. This skill ports its genuinely portable behavioral core to a text-generating agent's own multi-step work. It does not reproduce the original project's TXT-OS prompt file, its hardcoded demo-benchmark output, or its user-skepticism-deflection script -- see references/honesty-and-provenance.md for exactly what was kept, what was dropped, and why.

The original names four "Big Bang" modules (BBMC, BBPF, BBCR, BBAM) plus a numeric drift score, deltaS = 1 - cos(I, G) (I = current state, G = goal/anchor), and a trend classifier over consecutive deltaS values (convergent/recursive/divergent/chaotic). All of this is ported below. Where the original relies on real computation this skill cannot perform (real embeddings for deltaS, real attention-weight statistics for BBAM), the instruction explicitly hands that judgment to you, the calling agent, to make in plain language instead -- see references/wfgy-core-mechanism.md for the full technical basis of every claim in this file, and references/honesty-and-provenance.md for exactly what was reframed and why.

On deltaS: absent a real embedding call, any numeric deltaS you produce is your own qualitative estimate, not a measurement. Use the label ("deltaS is climbing," "deltaS looks high here") as shorthand for "this step is drifting from the stated goal" -- never present a specific decimal (e.g. "deltaS = 0.42") as if it were computed, because it is not, unless real embeddings are actually available (see below).

If a gm-plugkit spool is running in this project (check .gm/exec-spool/.status.json) AND its build serves a similarity verb, you can get a real deltaS instead of a self-estimate: dispatch {"text_a": "<G>", "text_b": "<current state>"} and read back {"similarity", "distance"} -- distance is a genuine 1 - cos(I, G) from real BGE-small-en-v1.5 embeddings. Do NOT assume the verb exists just because a spool is running: not every build serves it, and an unrecognized verb is silently left queued with no response rather than erroring, so a missing response after a normal read cycle means the verb is NOT available -- treat that exactly like no spool. When you get a real distance back, use it as deltaS and say so explicitly ("deltaS = 0.31, computed"). Otherwise fall back to the qualitative label above and say so explicitly too ("deltaS looks high here, my own estimate, no embedding tool available"). Never let the reader assume one when you did the other.

G - the anchor (BBMC pattern: compare state against goal)

At the start of any task this skill applies to, write one sentence stating the actual goal (G) -- not the first sub-task, the actual end state the user wants. Re-read it before any step that could plausibly have drifted: a long tool-call chain, a pivot in approach, a request to "also" do something adjacent.

• Stated G in one sentence before starting.
• Before each major step, ask: does what I'm about to do still serve G, or have I started solving a different, adjacent problem?
• If drift is real (not just "this step looks different from the last one" -- actual scope change, contradicted earlier decision, answering a different question than asked), say so explicitly and re-anchor before continuing.

Gotcha: the temptation is to silently keep going once you notice drift, because stopping to say "wait, I've drifted" feels like an interruption. Don't suppress it -- a silently-corrected drift is invisible to the user and looks like it never happened; a stated one is a real signal they can act on.