The competent stranger test: could someone with skills but zero context produce an acceptable result from your spec alone?
Test specification completeness by asking whether a competent stranger with relevant skills but zero context could produce an acceptable result from your specification alone—if not, the missing information must be externalized before delegation.
Why This Is a Rule
The gap between what's in your head and what's in your specification is the primary source of delegation failure. You know the client prefers concise communications, that the deadline is actually Thursday not Friday (because Friday is a buffer), and that "good enough" quality for this project means 90% not 100%. None of this is in the specification. The delegate, working from the spec alone, produces the wrong communication style, targets Friday, and over-invests in perfection — all predictable failures caused by missing specification, not missing competence.
The "competent stranger" test makes specification gaps visible: imagine someone with relevant skills who has never worked with you, knows nothing about this project, and has only your written specification to guide them. Could they produce an acceptable result? Every gap the stranger would encounter — "What tone? What deadline interpretation? What quality bar?" — is context you're carrying in your head that needs to be externalized.
This is Write agent actions as procedures a stranger could follow — aspirations and principles are not executable steps (write procedures a stranger could follow) applied to delegation specifications. The stranger test is the most demanding version of specification testing because it assumes zero shared context — no institutional knowledge, no relationship history, no implicit assumptions.
When This Fires
- Before delegating any significant task — apply the test to your specification
- When delegation produces disappointing results despite the delegate being competent — the spec may be incomplete
- When writing delegation briefs, project descriptions, or task assignments
- Complements Three-component handoff spec: output format, explicit expectations, and return protocol — ambiguous handoffs create bottlenecks (three-component handoffs) with the specification completeness test
Common Failure Mode
Assuming shared context: "They know what I mean." They don't — or they know 60% of what you mean and fill in the remaining 40% with their own assumptions. The resulting output is 60% what you wanted and 40% surprise, producing rework that consumes more time than writing a complete specification would have.
The Protocol
(1) Write your delegation specification. (2) Imagine a competent stranger reading it: someone with relevant technical skills but zero context about you, your project, your preferences, or your organization. (3) For each decision the stranger would need to make: is the answer in the specification? If yes → the spec covers this. If no → the stranger will guess, and their guess may not match your expectation. (4) For each gap, externalize the missing context into the specification: quality standards, tone preferences, deadline interpretations, scope boundaries, success criteria. (5) Re-test: with the added context, could the stranger now produce an acceptable result? If gaps remain → continue externalizing. (6) The specification is complete when the competent stranger needs to ask zero clarifying questions.