CtrlK
BlogDocsLog inGet started
Tessl Logo

coding-agent-helpers/compact-handoff

Use when work needs to be handed off to another agent or another human. Produce a continuation-ready brief with the objective, completed work, assumptions, unresolved issues, and next action instead of a generic summary. Good triggers include "prepare a handoff", "make this resumable", and "summarize this for another agent".

92

1.41x
Quality

100%

Does it follow best practices?

Impact

89%

1.41x

Average score across 8 eval scenarios

SecuritybySnyk

Passed

No known issues

Overview
Quality
Evals
Security
Files

criteria.jsonevals/scenario-4/

{
  "context": "The agent must produce a handoff for a partially-built data pipeline. This scenario tests whether the agent keeps the document minimal and transfer-focused rather than comprehensive, and whether it favours surfacing unresolved questions over writing a narrative recap of what was built.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "No long prose paragraphs",
      "description": "The handoff document does NOT contain multi-sentence prose paragraphs explaining how things work; information is in bullet points or short statements.",
      "max_score": 12
    },
    {
      "name": "Critical References minimal",
      "description": "The Critical References section does NOT include every file and URL from the task; it contains only the subset needed for the receiver to start immediately.",
      "max_score": 10
    },
    {
      "name": "Unresolved prioritised",
      "description": "The Unresolved section is present and contains at least both open decisions (deduplication approach and schema sign-off), not just a list of remaining tasks.",
      "max_score": 12
    },
    {
      "name": "Completed section is factual",
      "description": "The Completed section lists what is done without re-explaining implementation details or how things work.",
      "max_score": 8
    },
    {
      "name": "Objective section present",
      "description": "The document has an Objective section that states the end goal of the pipeline.",
      "max_score": 7
    },
    {
      "name": "Next Action is singular and concrete",
      "description": "The Next Action section names one specific action to take first (not a list of all remaining work).",
      "max_score": 10
    },
    {
      "name": "Assumptions section present",
      "description": "The document has an Assumptions section listing at least one assumption (e.g. production volume, schema state).",
      "max_score": 8
    },
    {
      "name": "All six sections present",
      "description": "The document includes all six prescribed sections: Objective, Completed, Assumptions, Unresolved, Next Action, Critical References.",
      "max_score": 8
    },
    {
      "name": "Document is concise",
      "description": "The entire handoff document is shorter than 400 words — the brevity reflects transfer-optimization, not completeness.",
      "max_score": 10
    },
    {
      "name": "Critical References section non-empty",
      "description": "The Critical References section lists at least one file path, command, or URL.",
      "max_score": 7
    },
    {
      "name": "No completeness narration",
      "description": "The document does NOT contain a section or paragraph that summarises the full scope of all work still to be done (i.e., does not try to be a complete project plan).",
      "max_score": 8
    }
  ]
}

evals

tile.json