Operations Agent

Work Intake

Turn a loose or half-formed request into one clear piece of work, with the outcome, one owner (a person, an agent or a Flow), a due date and a done-when line, after checking it is not already tracked, asking at most three questions. Use when someone says "can someone handle…", "we need to…", "add this to the list", "who should do this", "make this a task", or drops a request with no owner or date. Do not use for a whole project with phases (use @file:project-setup), for breaking one big task into steps (use @file:task-decomposition), or for work that needs several specialist agents in sequence (use @file:multi-agent-plan).

Project Setup

Turn a goal and a deadline into a Loop project plan, with phases, milestones and tasks worked back from the date, each task carrying one owner, a due date and a done-when line, plus the critical path and what to cut first. Use when someone says "set up the project for…", "plan the work to hit…", "break this into phases", "what has to happen before launch day", or "build me a project plan". Do not use for a product or pricing launch's go-to-market plan (use @file:launch-planning), for a customer implementation (use @file:implementation-planning), for one loose request that needs an owner (use @file:work-intake), or for a one-domain list of steps with no project around it (use @file:task-decomposition).

Weekly Operating Review

Read the team's real task list, calendar and running Loops and turn them into the week's operating review, covering what shipped, what is late, what is due, what is blocked, what has no owner, and the few things that need a decision from a person, written so a leader can act on it in two minutes. Use when someone asks "how are we doing this week", "what's late", "status of the project", "prep the weekly review", "what's at risk", or "write the weekly update". Do not use for a product status update written for stakeholders outside the team (use @file:stakeholder-update), for moving work between people (use @file:workload-replan), or for a post-mortem after the project ends (use @file:project-retrospective).

Workload And Replan

Find where the team's work is stuck (overloaded people, single points of failure, blocked chains, too much started and too little finished) and propose one replan of cuts, new dates, new owners and splits that the person approves on a single card before anything changes. Use when someone says "we're overloaded", "this keeps slipping", "rebalance the work", "replan the project", "who has too much on", "reorganize these tasks", or "what should we drop". Do not use for this week's status alone (use @file:weekly-operating-review), for planning a new project from scratch (use @file:project-setup), or for deciding which product features to build (use @file:feature-prioritization).

Meeting To Actions

Turn meeting notes or a transcript into what the meeting actually produced (the decisions with who made them, the action items each with one owner, a date and a done-when line, and the open questions), then propose the action items as tasks on one card. Use when someone pastes or mentions notes and says "pull out the action items", "what did we decide", "turn this into tasks", "write up the meeting", or "who owes what". Do not use to prepare for a meeting that has not happened (use @file:meeting-brief), to prep a sales meeting (use @file:meeting-prep), or to plan a whole project out of a kickoff (use @file:project-setup).

Project Retrospective

Run a blameless retrospective on a finished project, launch or incident, reconstructing what happened from the task history, finding the root cause of the one or two biggest misses with five whys, and ending in owned follow-up actions and changes to how the team works next time. Use when someone says "run a retro", "post-mortem on…", "what went wrong with…", "lessons learned", "why did this slip", or "what should we do differently". Do not use for a deal won or lost (use @file:win-loss-analysis), for a live customer escalation (use @file:escalation-management), or for this week's status (use @file:weekly-operating-review).

Launch Planning

Orchestrate a product, feature, or pricing launch across every team — matching effort to market impact, translating capability into buyer value, and driving adoption, gated on product readiness and field enablement. Use when user needs launch strategy, GTM coordination, a launch timeline, go/no-go criteria, tier classification, or a cross-functional launch checklist. Do not use when positioning definition is the need — the launch plan consumes positioning, it doesn't author it.

Implementation Planning

Plan complex customer implementations with stakeholder mapping, phased milestones, and risk registers. Use when user needs implementation plan, go-live roadmap, deployment strategy, or post-sale handoff plan. Do not use when customer is already live and needs first-90-days onboarding — use onboarding-plan instead.

Stakeholder Update

Write an internal status update that builds confidence by surfacing risks early and answering questions before they're asked — a trust instrument, not a reporting chore. Use when user needs an exec/board product update or project status. Do not use when the audience is customers — use @file:roadmap-communication; or it's a shipped-feature note — use @file:release-notes.