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-2/

{
  "context": "The agent must produce a handoff for a documentation project in mid-flight. This scenario specifically tests whether the Critical References section is present and contains only the minimum references needed, and whether unresolved questions are foregrounded rather than hidden in a project overview.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "Critical References section present",
      "description": "The document has a section explicitly labelled 'Critical References' (or equivalent) listing files, URLs, or people.",
      "max_score": 10
    },
    {
      "name": "Critical References are minimal",
      "description": "Critical References does NOT list all content mentioned in the task — it selects only the references genuinely needed for immediate continuity (e.g. style guide, docs site, SME contact).",
      "max_score": 10
    },
    {
      "name": "Unresolved section contains open questions",
      "description": "The Unresolved section lists at least two of the three open questions from the task context (screenshot blockers, migration guide approach, glossary scope) as genuine questions, not just tasks.",
      "max_score": 12
    },
    {
      "name": "Unresolved section present",
      "description": "The document has a section explicitly labelled 'Unresolved' (or equivalent).",
      "max_score": 7
    },
    {
      "name": "Questions over recap in Unresolved",
      "description": "The Unresolved section is dominated by questions and blockers, not by a list of articles yet to be written.",
      "max_score": 10
    },
    {
      "name": "Objective section present",
      "description": "The document has an Objective section stating the purpose of the documentation work.",
      "max_score": 7
    },
    {
      "name": "Completed section present",
      "description": "The document has a Completed section.",
      "max_score": 7
    },
    {
      "name": "Assumptions section present",
      "description": "The document has an Assumptions section with at least one stated assumption.",
      "max_score": 7
    },
    {
      "name": "Next Action section present",
      "description": "The document has a Next Action section.",
      "max_score": 7
    },
    {
      "name": "Next action is concrete",
      "description": "The Next Action contains a specific first step (e.g. a specific guide to start, a specific person to contact) rather than 'continue the documentation'.",
      "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": 7
    },
    {
      "name": "No narrative recap",
      "description": "The Completed section does not narrate the writing process; it lists what is published or done in concise bullet points.",
      "max_score": 8
    }
  ]
}

evals

tile.json