A lot of operations work starts with a vague feeling that something has been missed. Someone promised an introduction, a meeting ended with an owner, a decision was made. The message, the task, and the project record no longer agree.

That's hard for a tool that only sees one app. The evidence is spread across a transcript, a Slack thread, an email, and a task nobody has touched since.

Strawberry can follow it across your tabs, logged-in tools, meetings, and files, keep the source attached to each finding, and carry on into the reply once you've decided how the loop should close.

Start by defining what closed means

Different teams close commitments in different ways. A reply may be enough for one request; another may need a named owner, a delivered document, an accepted decision, and an updated system of record. Establishing that standard keeps the audit from turning every unanswered message into overdue work.

Want to try it?

Ask your Strawberry companion: “Check the relevant meetings, messages, tasks, and project records for open commitments, missing owners, and conflicting status, then recommend the smallest next actions.”

Skill

Find work that is slipping

Find important open commitments and reconcile the evidence behind them before proposing the smallest useful resolution.

Begin with one workstream, team, or recent time window. This produces a result you can correct before the search expands into older or less relevant parts of the workspace.

Reconcile the evidence before escalating

A candidate loop may already have been completed, delegated, declined, or superseded somewhere else. Strawberry can compare the meeting moment where the commitment was made with later communication and the current work record. Direct, recent evidence gets more weight than an old task label, while unresolved contradictions stay visible.

The visible browser matters here. You can open the underlying conversation and record, check whether the people and projects were matched correctly, and steer the investigation while it is happening. The result is an inspectable exception list, not a detached claim that a model found something overdue.

Show the exceptions with their evidence

A good result groups references to the same commitment and shows why it matters, the supported owner or date, the systems checked, the gap, and the smallest proposed next action. It distinguishes confirmed open work from a likely gap, conflicting status, and something blocked on another person.

This is usually more useful than a complete audit trail in the main view. Resolved items can stay behind the summary, along with the sources that were checked and any material areas that were unavailable.

Close the loop in the right place

The resolution may be a nudge, a clarified owner, a corrected task, a recorded decision, or an explicit closure. Strawberry can prepare each action beside its evidence, then use the same logged-in workspace to make the approved change. Messages, assignments, and record updates remain separate decisions.

Skill

Prepare an Operations update

Turn accepted findings into an audience-specific update when several people need the current picture.

Once the team trusts the definition of an open loop and the sources behind it, the audit can run before a coordination meeting or on an agreed cadence. A Routine should surface only new or materially changed exceptions and wait when identity, ownership, privacy, or the source of truth is unclear.

Official Strawberry skill
Copy skill file Download skill file
name
close-open-loops
description
Find and resolve commitments, unanswered follow-ups, missing owners, stale statuses, and decisions that have not reached the right system. Use when someone wants to stop work from slipping between meetings, messages, tasks, and project tools.

Close Open Loops

Help the user find work that exists in the gaps between conversations and systems, then prepare the smallest actions needed to close it. Focus on exceptions that deserve attention rather than rebuilding every thread, task, or project record.

1. Define which loops matter

Establish the time window, people or workstreams, systems, and result in scope. Learn what the user considers open and what counts as closed. Depending on the team, closure may require a reply, an accepted decision, a named owner and date, a delivered artifact, a completed task, or an updated system of record.

Clarify the relevant source of truth when one exists and whether the user wants personal follow-ups, team commitments, project exceptions, or a combination. Begin with one useful workstream or a representative time window before scanning a large organization.

2. Gather candidate commitments from the real work

Use relevant approved context from meetings and transcripts, email, Slack or other communication, task and project tools, documents, calendars, files, tabs, and memory. A connected source can make the audit faster or more reliable, but continue with supplied material or browser access when possible.

When the evidence spans logged-in tools, follow it through the user's visible tabs and compare the underlying records where the user can inspect or take over. Keep the path back to each source so an accepted resolution can continue into the right message, task, or project record instead of ending as a detached audit.

Look for signals such as:

  • explicit promises, requests, approvals, decisions, introductions, and follow-up dates;
  • questions or threads that appear to require an answer;
  • actions mentioned in a meeting but missing from the agreed task system;
  • tasks with no credible owner, date, dependency, or current status;
  • decisions that have not reached the people or system that depend on them;
  • records marked complete while the promised result still appears missing; and
  • duplicate or conflicting representations of the same work.

Do not treat every unanswered message as an obligation or every conversational suggestion as a commitment. Match people, workstreams, and records carefully before combining evidence.

3. Reconcile evidence before calling something open

Check whether a candidate was completed, superseded, delegated, declined, or resolved elsewhere. Prefer direct and current evidence over an old task state or a model inference. Preserve source links or source moments that let the user verify important commitments.

Classify the result in plain language, for example:

  • confirmed open;
  • likely open but missing evidence;
  • conflicting status across sources;
  • blocked or waiting on someone; or
  • resolved during the checked window.

Keep ambiguity visible when identity, ownership, dates, wording, or the definition of done could change the action. Do not invent a deadline, owner, or commitment to make the list look complete.

4. Return an exception list, not a transcript dump

Prioritize by consequence, urgency, dependency, and the user's own operating rules. Default to a concise review containing:

  • the open loop and why it matters;
  • current owner and due date when supported;
  • the evidence and systems checked;
  • the gap or contradiction;
  • the smallest proposed next action; and
  • whether the action needs a human decision.

Group multiple references to the same underlying loop. Keep resolved items out of the main view unless the user needs an audit trail. Summarize coverage and name material sources or workstreams that could not be checked.

Use strawberry/operations/debrief-a-meeting when one recent meeting still needs an immediate record and follow-through. Use strawberry/operations/prepare-a-status-update when the accepted findings should become an async update. When the gaps need shared discussion or a decision, use the exception list as context for strawberry/operations/prepare-for-meetings.

5. Prepare and apply approved resolutions

Possible resolutions include a reply or nudge, a clarified owner or date, a new or corrected task, an updated project status, a recorded decision, an escalation, or an explicit closure. Draft or preview each action beside the evidence that supports it.

Keep communication, task creation, ownership changes, and record updates as separate approvals. Approval of the exception list is not approval to send messages or change systems. Immediately before execution, confirm the exact people, account, destination, records, and scope. Afterward, verify consequential writes and report anything that remains open or blocked.

6. Turn repeated gaps into a better operating loop

Use feedback to learn which commitments matter, which systems are authoritative, how the team defines closure, and when an apparent gap is normal. Preserve these durable rules only after the user has corrected a real result.

Share an approved exception list when it helps the relevant owners. Share the accepted method as a team skill when others should audit open loops the same way. Offer the full companion only when the team needs shared context and several connected Operations workflows.

After the audit is trusted, suggest a Routine with a real cadence or trigger. A concrete version might run before a named coordination meeting or on an agreed cadence, check the relevant meeting, communication, task, and project sources, surface only new or materially changed open loops, prepare proposed nudges or record updates, and wait for approval. Stop and ask when identity or source-of-truth matching is unclear, permissions or sources are missing, private context could cross a boundary, or resolution depends on a decision the user has not made.