Set the customer and business outcome
The work begins with the result the company needs to create and the person responsible for it.
Set the product outcome, engineering standard, and scope of the work. Lead Dev carries that direction across specialists and concurrent work, then returns the decisions where your context and responsibility determine what ships.
The work begins with the result the company needs to create and the person responsible for it.
The product promise, experience, and tradeoffs being protected travel with the objective.
Architecture, quality expectations, and the meaning of done remain present across specialist work.
The workforce knows which decisions to carry and which ones return to the people responsible.
From the first brief through specialist work and review, the objective and engineering standard remain in one Thread. Your team can enter wherever its judgment matters and see how the work arrived there.
The assistant follows the style guide in short chats and ignores it in long ones. Why would length change its behavior?
I will diff the exact context sent in both cases, measure where the token budget runs out, and check what gets dropped first.
Retrieved documents are appended until the window fills, and the system prompt is what silently falls off the end. The fix reserves tokens for instructions before retrieval ever runs, verified in a preview.
If the instructions can fall out of context, so can the guardrails. Add the eviction case to the release checks.
Reviewable diff ready with the token reservation covered and preview verification attached.
The objective, product promise, work completed, and open question arrive together.
The return includes the evidence, quality checks, and uncertainty that matter to the call.
Your attention enters where engineering judgment changes the product, the risk, or what happens next.