Mechanism: Session Handoff — Summary for the Next Chat
A session handoff is a short structured summary — goal, what changed, verify state, open questions — passed to the…
Mechanism: Rules & Skills as Memory — Persistent Conventions the Agent Re-Reads
Rules and skills as memory means storing stable project conventions in files the agent loads every session — so you…
Mechanism: Anchor Files — Always Include the Project’s Compass
Anchor files are the small set of documents or source files you almost always attach — README, types, architecture note,…
Mechanism: Progressive Disclosure — Add Context Only When Stuck
Progressive disclosure is starting an agent session with minimal context — goal, anchors, failing output — and adding files or…
Mechanism: Escalation — When to Switch Model, Mode, or Human
Escalation is a planned step-up when the current approach stalls — switch model, mode, human reviewer, narrower slice, or different…
Mechanism: Interface-First — Types and API Before Implementation
Interface-first means defining the contract — types, function signatures, route schemas, or module API — before the agent implements internals,…
Mechanism: Vertical Slice — One Thin End-to-End Pass
A vertical slice is a single session that ships one path through the stack — request to response, UI to…
Mechanism: Example-Driven Spec — Behavior as Input/Output Pairs
An example-driven spec defines behavior through concrete input/output pairs (and edge cases) before implementation — so the agent builds toward…
Mechanism: Acceptance Criteria — Testable Done Beyond the Goal
Acceptance criteria are specific, checkable conditions that must all pass for work to count as done — turning a (/mechanism-goal/)…
Mechanism: Split & Conquer — One Session, One Job
Split & conquer is planning work so each agent session has a single shippable job — with its own (/mechanism-goal/),…