Conciseness

The body is 13 lines with zero padding: no explanation of what a handoff is or why context matters, just a conditional, a five-item section list, a save location, and a reporting instruction. Every token earns its place, matching the 'lean and efficient' anchor.

Actionability

Concrete, executable guidance throughout: a named artifact ('HANDOFF.md'), a read-before-update conditional, five named sections, a save location ('project root'), and a final instruction ('tell the user the file path'). Not a 5 because there is no example or template of the handoff document itself, leaving the desired format per section implicit.

Workflow Clarity

The sequence is clear and correctly ordered (check existence → read prior context → create/update with named sections → save → report path), and the conditional in step 2 acts as a lightweight checkpoint. Not a 5 because there is no validation step confirming all five sections are filled before saving; not a 3 because the sequence is explicit and the operation is non-destructive.

Progressive Disclosure

At 13 lines with no need for external references, the single body with a well-organized step list and bulleted section names is the appropriate structure, matching the under-50-lines guideline for a top score.

Specificity

The description names the domain ('handoff document') and one concrete action ('write or update'), which matches the 'names domain and 1-2 concrete actions' anchor. It is not a 4 because it lists no further capabilities (what the handoff contains, when to update vs. create).

Completeness

The 'what' is clear ('write or update a handoff document... continue this work') but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. Not a 4 because the 'when' is entirely absent rather than merely weakly implied.

Trigger Term Quality

Relevant keywords like 'handoff document', 'next agent', and 'fresh context' are present, but common variations users would naturally say ('hand over the work', 'brief the next session', 'session summary', 'continue where we left off') are missing. Not a 4 because the natural-phrase coverage is thin beyond the single term 'handoff'.

Distinctiveness Conflict Risk

'Handoff document' is a clear niche term with distinct triggers, giving mostly distinct intent with only minor overlap risk against general documentation or summarization skills. Not a 5 because without an explicit trigger clause it could fire on broader 'document the work' or 'summarize this session' requests.