evnchn-agentic

Use when bringing forward priors from PAST sessions / cross-agent history before doing new work — NOT about re-reading the current context window (which is trivially in-context). Specifically triggered when auto-compact is lossy, when cross-session reference is needed, when the same topic has been treated before, or when the original work was done in a different agent's session. The discipline is

Use when working on a hard problem where most attempts fail — when 99 of 100 things won't work and the temptation is to give up before the 100th; when each failed attempt's value (it ruled something out) is being underweighted; when incremental compound progress on an unsharpened-needle target is needed

Use when, just after abandoning or failing at something, you catch yourself concluding "that wasn't worth reaching anyway" — the post-mortem self-deception / motivated-reasoning anti-pattern. Fires when writing a post-mortem after a failure or rollback, recording a lesson after a retreat, or when an operator/agent's stated reason for quitting smells like comfort rather than analysis. The tell: a g

Use when user asks for a rough draft, first pass, brainstorm, MVP, stub, sketch, or proposes to "draft a PR for review and refinement before sending upstream" — anywhere the user is throwing a brick (deliberately rough work) to elicit jade (refinement, feedback, selection)

Use when tempted to treat the current session as interchangeable with past or future ones — the every-session-is-unique discipline, and the invocation surface that fires durable-fix skills a fungible-session mindset would skip. Fires when about to defer something to "a future session" as if that session will reconstitute this exact context, when a memory-aware agent assumes "I'll just re-derive it

Use when about to claim work is done / verified / working — empirical verification is required, not model-based confidence. Run the code, observe the output, check the file exists, verify the page renders, read the actual stack trace. Don't trust your model of the system; trust the system. Pairs with the verification-before-completion superpower by giving it a cultural handle that operator-side ha

Use when a symptom has an OBVIOUS causal root and the temptation is to patch the symptom — when a bug fix is masking the real issue, when retries are hiding a contract violation, when a workaround is becoming permanent. The default debugging frame; reach for chengyu-besiege-wei-save-zhao only after exhausting this.