Back to library

Document summary and action items

Turns business documents into a concise audience-specific summary, a cited action register, and a separate list of dates and commitments. Use for board papers, project material, policies, proposals, reports, meeting notes, and document review; keywords include summary, action items, deadlines, commitments, and key dates.

by adlass TemplatesVersion 1Uses adlass toolsUniversal

Published Aug 21, 2026 · Updated Aug 26, 2026

Helpful · 0View raw SKILL.md

Requirements

Define the preferred summary audience and maximum length. Define the required action-register columns and status vocabulary.

Skill document

The full SKILL.md your agent reads and follows.

Document summary and action items

Purpose

Convert one or more business documents into a decision-ready summary and structured follow-up material. Preserve the difference between what a source states, what it implies, and what remains unresolved.

Scope

Cover the document's purpose, decisions, arguments, figures, commitments, dependencies, owners, and dates. Include only actions supported by the source or explicitly labelled as proposed.

Excluded: Legal advice, factual research beyond the supplied corpus, and execution of any action.

Data basis

  • Source documents in scope, including headings, paragraphs, tables, footnotes, and metadata.
  • Optional audience, length, and action-format inputs.

Result

Produce a concise summary, an action-items sheet with source citations, and a key-dates document. Keep source facts distinct from interpretation and recommendations.

Quality criteria

  • Every material claim in the summary has a document and location citation.
  • Every action row states the action, owner, due date, status, and evidence or says not stated.
  • Dates, amounts, names, and percentages match the source exactly.
  • Conflicts between documents are shown rather than silently reconciled.
  • The summary meets the requested audience and length without omitting material caveats.

Instructions

Use the source's own terminology. Treat a task as assigned only when an owner is named; otherwise mark the owner unassigned. Treat a date as a commitment only when the source frames it as a deadline, milestone, renewal, or meeting. Cite the smallest useful location, such as heading, page, table, or row. Put questions and assumptions in the open-points section, not in the action register.

Adapt before use

  • Define the preferred summary audience and maximum length.
  • Define the required action-register columns and status vocabulary.
  • Add the company's owner names or team mapping if generic role names are insufficient.
  • Define whether proposed actions may be included alongside explicit commitments.
  • Define the preferred date format and citation style for the action register.

Related skills

  • Business travel itinerary

    Turns business appointments, locations, travel preferences, and policy rules into a coordinated itinerary with timing, budget estimates, and preparation requirements. Use for multi-stop work trips and conference travel; keywords include travel plan, itinerary, business trip, travel policy, cost estimate, and logistics.

  • Company wiki page

    Creates or refreshes a navigable company wiki page from authoritative policies, procedures, and operational references, with named owners, version dates, links, and explicit knowledge gaps. Use for internal documentation, SOP pages, knowledge-base maintenance, or policy publishing drafts.

  • Email intake triage

    Classifies an email corpus by topic, urgency, ownership, response need, and due date, then drafts focused replies for the highest-priority messages. Use for shared inbox exports, executive inbox reviews, service requests, and administrative intake; keywords include email triage, inbox review, prioritization, delegation, and reply drafts.

  • Handbook page draft

    Drafts a publishable internal-handbook page from approved policy sources, turning rules into audience-specific guidance with definitions, procedures, decision tables, examples, exceptions, and ownership metadata. Use for employee handbooks, IT runbooks, security guidance, HR knowledge bases, and policy-to-practice documentation.