102: Briefing the Agent
Key question: How do we brief the agent, and where does the briefing live?
This Chapter's ACIs
| ACI | Name | Takeaway |
|---|---|---|
| ACI-007 | The Delegation Model | Delegate rather than pair: a written brief, stated constraints and a checked outcome. Put the standing state in the brief beside the task. |
| ACI-008 | The Prompt That Worked | Define the task as a question, fence its purpose as well as its features, and check its dependencies before the work starts. |
| ACI-009 | Context Engineering vs Prompt Engineering | When the agent fails, ask what it could not see before you reword the prompt. Hold every context artefact to the thing it describes. |
| ACI-010 | The Guidance File | Write it as an index of one-line rules, each traced to an incident you can name, within its load budget. In a generated file, only the hand-authored block is yours. |
| ACI-011 | Style Rules vs Architecture Rules | First check that a rule is true of this code. Delete style the model already follows, keep project knowledge, and climb for rules that keep breaking. |
| ACI-012 | Cross-Project Contamination | Say what the project is, what it is not and which named patterns do not belong. The section's survival in the file shows presence and nothing more. |