Handbook
L — Triage size L
Large request — ~100k–400k token order; cross-cutting or multi-surface within ecosystem.
What it is
Triggers detailed plan structure: phases, tests, dual wiki, PDCA loops, drift gate, model tiering.
When people say this
Crypto migration, Cockpit+lcdl boundary feature, KS propagation across consumers.
Where it lives
.cursor/rules/forge-planning-standards.mdc
How it fits the ecosystem
triage-planning-effectiveness harness Scenario A expects L for E2EE-style features.
Typical usage in plans and chat
L plans mandatory: acceptance per phase, rollback, subagent tier proposal, DoR/DoD checkpoints.
Related terms
Disambiguation bridges
Term page — canonical catalog entry l.