Prefer the smallest change that solves the problem cleanly; one mechanism over many, DRY and KISS over cleverness.
Trigger when user asks to "prepare next steps", "prep next steps", or signals readiness for autonomous build ("before we build", "pre-flight"). Produces a five-part briefing - 4 ranked design decisions, 4 ranked concerns, 6 ranked questions, an open…
If decoding an ambiguous instruction takes more than a few sentences of reasoning, stop and ask instead of guessing.
When asked to estimate something unstated, produce a legible correctable evidence chain rather than refusing or fabricating a number.
Verify every load-bearing claim by reading the code or running the check; never assert from memory or dismiss something as too obvious to confirm.
On how a system actually behaves, read the source first; code is authoritative, prose and docs can be stale.
Guard against attribute substitution on any output that will be acted on as a verdict, ranking, routing, or go/no-go decision — regardless of how the request is phrased. Casual-looking prompts ("where does this stand?", "predict the path") are the…
Read OR write the project's session-handoff doc. WRITE mode updates it so a fresh agent can pick up the work (what was built, in-flight files, open questions). LOAD mode reads the doc AND the files it references so YOU get up to speed at the start of a…