Appendix: Prompt Engineering

Prompt engineering is a real skill, and it is worth developing once your agent teams are designed and operational — which is why it belongs here, at the back of a book about organizational design, rather than at the front. It is not, however, the skill to develop first. Writing effective prompts for an agent team is only useful when you know what the agent team is accountable for — which is the output of Signal, Source, and Design. An excellent prompt that is pointed at the wrong accountability, or that operates within a workflow that was never designed, will produce excellent output that changes nothing.

If you have read this book and you are interested in prompt engineering, your timing is right: you now have the organizational design context that makes prompt skill meaningful. If you are reading this appendix before you have run a sprint, go back to Signal. The design work comes first.

What Effective Prompting Looks Like in the Sprint Context

In the Design phase, when Work Decomposition has identified the specific tasks an agent team will execute, prompt design is the activity of writing precise, testable instructions for each task. The best prompts in a sprint context have three characteristics: they are specific about the input format the agent receives, they are explicit about the output format the agent should produce, and they include the constraints and edge cases the human supervisor identified during the Design phase. Prompts built during Design — against a specific accountability, with a known input and output — perform significantly better than prompts written in the abstract.

After the Deliver phase, the sprint retrospective will surface cases where the agent produced unexpected output. Those cases are prompt design signals — they indicate where the instruction was ambiguous or where an edge case was not anticipated. The Compound phase of the sprint is where those signals become prompt improvements, which become Design improvements, which become better sprint performance in the next cycle.

Prompt engineering, in this context, is not a tool skill. It is an organizational design feedback loop.