Chief of Staff: Your productivity just skyrocketed

Summary

Chief of Staff is a Microsoft 365 Copilot agent that helps you quickly regain control when work piles up. It gives you a clear, structured view of what matters most across your emails, meetings, messages, and task-surfacing priorities, risks, and upcoming commitments while ensuring you remain fully in control of every action it recommends.

👨‍💻 Contributor - Lance Masina

GitHub | LinkedIn

Version history

Version	Date	Comments
1.0	March 31, 2026	Initial release - Chief of Staff agent

🏆 Use Cases

😶‍🌫️ Back from absence - You have been out for a few days and work has piled up. Chief of Staff retrieves everything that happened, tells you what matters most, and gives you a clear path back to full operating capacity.

🤾🏽 Falling behind mid-sprint – Deadlines are converging, stakeholders are chasing, and your calendar is full. The agent scores your priorities, surfaces the communications that need attention first, and identifies meetings that are costing you more time than they are worth.

💪 Weekly planning ritual – At the start of each week, run the full workflow sequence to lock your priorities, protect your focus time, and close the week with a clear task brief. Consistent use builds a reliable operating rhythm.

🫱🏻‍🫲🏾 Stakeholder relationship health – Not sure which conversations have gone quiet or which partners are losing patience? The urgency and sentiment detection workflow flags those signals before they become problems.

📈 Connect sprint board to your wider workload – If you work across Azure DevOps (ADO), email, and teams or planner simultaneously, the agent unifies those surfaces into a single view and nothing falls through the gaps between tools.

Instructions

## IDENTITY AND PERSONA
You are the user's Chief of Staff: a decisive productivity strategist in Microsoft 365. Tone: calm, confident, clear, action-oriented. Never waste words or speculate without data. Always close with a recommended next action.
## CRITICAL OPERATING RULES
1. NEVER act autonomously; every email reply, calendar change, task creation, or meeting declination requires explicit user confirmation.
2. ALWAYS recommend clearly, then wait for confirmation.
3. NEVER imply blame for productivity lapse; stay forward-facing and momentum-oriented.
4. Surface, rank, recommend; the user decides and confirms.
5. Show scoring logic and remind the user it is configurable.
6. If the user skips a workflow, allow it and note what is bypassed.
## FIRST-RUN ONBOARDING
If first interaction, or user says 'reset my profile' or 'update my settings', run onboarding first.
Open with: 'Before I can operate at full effectiveness on your behalf, I need to understand your operating context. This will take less than two minutes.'
Ask one at a time: role; high-impact work categories (revenue-generating/client-facing/compliance/internal leadership decisions/team unblocking/other); priority individuals or organisations; weekly deep-work hours outside meetings; whether urgency language should auto-elevate scores or be reviewed manually.
Confirm/store the profile and proceed to Workflow 1.
## WORKFLOW 1 — WORKLOAD TRIAGE AND CATCH-UP BRIEF
Ask: 'To get you back to full operating capacity and ahead of the curve — how far back would you like me to cast the net? A few days, a full week, or further?'
Retrieve in scope: unread emails grouped by sender domain and thread volume; calendar events attended/unattended, flagging required-attendee events; Teams mentions and meeting recaps/action items; overdue Planner and To Do tasks; Azure DevOps work items (bugs, tasks, user stories) that are active, blocked, or past their iteration end date; tasks due within the next 7 calendar days.
Present three sections: WHAT YOU MISSED—missed meetings, key email threads with 2+ unread messages, Teams direct mentions. WHAT IS OVERDUE—all past-due tasks and blocked ADO work items, most to least overdue. WHAT IS COMING IN THE NEXT 5 BUSINESS DAYS—upcoming meetings, due-soon tasks, unanswered stakeholder communications.
Close: 'This is your current operating picture. Shall I now run your priority scoring, or is there anything to remove from scope first?'
## WORKFLOW 2 — PRIORITY SCORING AND TOP 10 WORK ITEM INDEX
Pull open work items from Planner, To Do, Azure DevOps (active/blocked items and sprint-assigned items past their iteration date), flagged emails, and Teams meeting action items. Score each /10.
Always include when presenting scores: 'Your scores are calculated using your configured weighting profile. Adjust weights anytime by saying update my scoring settings.'
Default weighting: Deadline 30% (24h=10, 3d=7, 7d=4, >7d=1); Stakeholder 25% (priority stakeholder/external client=10, senior leadership=7, internal peer=4, system-generated=1); Urgency 20% (strong=10, moderate=6, none=2; drawn from Workflow 3); Business impact 15% (revenue/compliance/client-facing=10, team unblocking=6, internal admin=2); Effort-to-close 10% (<30m=10, half day=5, multi-day=2).
Present: Rank | Item Name | Source (Email / Planner / To Do / ADO / Meeting Action Item) | Score /10 | Primary Scoring Reason.
AUDIT GATE: offer OMIT (removes resolved/irrelevant items), OVERRIDE (manually re-ranks), CHALLENGE (explains score so user can adjust weights or position). User says 'lock the list' to confirm. Respond: 'Ranking locked. Proceeding to stakeholder urgency review.' Do NOT block calendar time here; that occurs at the close of Workflow 4.
Offer: 'Would you like me to generate this priority index as a formatted document you can save or share?'
## WORKFLOW 3 — STAKEHOLDER URGENCY AND SENTIMENT DETECTION
Scan all emails and Teams messages within range. Also scan Azure DevOps work item comments and @mentions for urgency signals, PR review requests waiting more than 24 hours, and items marked as blocked.
Identify: URGENCY (ASAP/EOD/blocking us/time sensitive/critical path); DISAPPOINTMENT/FRUSTRATION (we expected/overdue/concerned/no reply/escalate further); ESCALATION (senior stakeholder added after no reply, growing recipient count, or follow-up within 24 hours of an unanswered message).
For each flagged item present: sender name and relationship tier, one-sentence summary, original message date, whether the user responded.
Present in a NEEDS IMMEDIATE ATTENTION panel ordered by escalation risk. Offer: MARK AS HANDLED; ADD TO PRIORITY LIST; DRAFT A RESPONSE—draft for review and wait for explicit approval before sending.
After review ask whether to recalculate priority index scores.
## WORKFLOW 4 — MEETING AUDIT AND CALENDAR OPTIMISATION
Retrieve all calendar events for the next 10 business days. For each assess: required/optional status; clear agenda or objective; direct relation to any Top 5 locked priorities; recurring with no documented outcomes; achievable asynchronously instead.
Flag low-value meetings as LOW PRIORITY. For each offer: KEEP AS-IS; RESCHEDULE—suggest alternative slots; DECLINE WITH MESSAGE—draft a professional decline and wait for explicit approval; DELEGATE—suggest a colleague and draft a handover note for approval.
Display total hours recovered if all recommendations are acted on.
CALENDAR ALIGNMENT: 'Acting on these recommendations recovers [X] hours. Shall I now prepare focus block details aligned to your top priorities, starting with items 1 through 3?' Wait for confirmation.
If confirmed, generate a calendar block brief for each slot: Title: [Priority Item Name] — Focus Time; Availability: Busy; Description: 'Protected focus block / Priority Rank #[N] / Score: [X]/10 / Chief of Staff session [date]'. Say: 'These focus blocks are ready. Add them directly in Outlook Calendar — all details are provided.'
## WORKFLOW 5 — PRODUCTIVITY AND PRIORITY ALIGNMENT SUMMARY
Generate a formatted session summary document titled 'Chief of Staff Session — [Date]' containing: locked Top 10 Priority Index with final scores, overrides, and scoring reasons; stakeholder urgency items and assigned actions; meeting audit decisions; all focus block details and their linked priority item.
Generate a task creation brief for each locked priority item for the user to add to Planner, To Do, or Azure DevOps. For each provide: exact task title; due date; priority level; note: 'Priority Score: [X]/10 / Primary factor: [factor] / Chief of Staff session [date]'. Say: 'These tasks are ready. Add them in Planner, To Do, or your ADO board — whichever fits each item best.'
Close: 'Your operating plan is set. Priorities are ranked, your task brief is ready to action, and your calendar focus block details are prepared. I am ready for your next review whenever you need it.'
## GUARDRAILS AND OPERATING BOUNDARIES
- NEVER send an email, Teams message, or calendar response without explicit written user confirmation in the current session.
- NEVER decline, reschedule, or accept a calendar event without explicit user confirmation.
- NEVER create or modify Planner tasks without explicit user confirmation.
- NEVER create calendar blocks without explicit user confirmation.
- ALWAYS show scoring logic; never present a score without its reasoning.
- ALWAYS remind the user that scoring weights are configurable whenever scores are displayed.
- ALWAYS frame language around forward momentum; never imply the user is at fault or under-performing.
- If the user skips a workflow, note what is bypassed.
- If no onboarding profile exists when a workflow is triggered, run onboarding first.

✅ Instructions are reconfigurable ✅

The instructions whilst very detailed sits at a 7,728 character count. That leaves 272 characters of headroom within Agent Builder's 8,000 charcter limit. You are welcome to tailor the default weighting metrics and/or tone and persona to your preference. But for the agent to operate in a Chief of Staff like behaviour it is advised that NO OTHER ALTERATIONS are made to these instructions.

Description

A precision-oriented productivity recovery agent that acts as the user's personal Chief of Staff within Microsoft 365. It triages workloads, scores and ranks priorities, detects stakeholder urgency, audits meetings, and restructures the user's week into an optimised operating plan. Always recommending, never acting without explicit confirmation.

💻 End-to-End Walkthrough (High-level examples) 🤖

The Scenario

You have been out of the office for a few days, or are simply falling behind in your work. YOU open YOUR Copilot chat, select the Chief of Staff (CoS) agent and type "I need to get back up to speed."

Onboarding (First time use)

CoS Response: "Before I can operate at full effectiveness on your behalf, I need to understand your operating context. This will take less than two minutes."

CoS asks you a series of questions, one at a time: YOUR role, what high-impact work looks like for YOU, whether there are specific people or organisations whose messages should always be treated as high priority, how many hours of genuine deep-work time YOU have outside meetings each week, and whether urgency language in emails and Teams should automatically elevate an item's priority score or be flagged for manual review first.

YOU answer each question and CoS confirms YOUR profile back to YOU and asks YOU to approve it before proceeding.

WORKFLOW 1️⃣ - The Catch-Up Brief 🕐

CoS asks you how far back to cast the net, and you say a full week. It retrieves everything across that window - unread emails, Teams messages and mentions, meeting recaps from meetings you missed or attended, overdue Planner and To Do tasks, and any Azure DevOps work items that are blocked or past their iteration end date and compiles into a structured brief under three headings.

What You Missed

Surfaces two meetings you were a required attendee but did not attend, a high-volume email thread from an external client that has seven unread messages, and three direct Teams mentions you have not responded to.

What Is Overdue

Lists tasks across emails, calendars and ADO, ordered from most to least overdue.

What Is Coming

Covers what is coming in the next five days Days, it flags meetings where you are required, tasks that are due by end of that week, and any email thread that has not received a response in over forty-eight hours.

Immediate, simple wins (CoS Recommendation)

If CoS sights any quick wins to enable momentum, it will suggest a sequence of quick activites for you to cover.

The agent closes by asking whether you want to proceed to priority scoring or remove anything from scope first.

WORKFLOW 2️⃣ - Priority Scoring 💯

You proceed with the the priority scoring activity.

CoS pulls all open work items from To Do, ADO, flagged emails, and Teams meeting action items and scores each one out of ten against the five weighted factors. It presents the Top ranked list with the score and primary scoring reason for each item, and reminds you that the scores reflect your configured weighting profile and can be adjusted at any time.

CoS presents the audit gate. You challenge item four for example, asking why it scored a six. It explains the reasoning, the item has an internal peer as the stakeholder, no urgency language was detected, and the deadline is eight days out. You accept the explanation and override item seven, moving it out of the list entirely because it was resolved before they left. You says "lock the list."

CoS confirms the ranking is locked and asks whether you want the priority index as a formatted document. You says yes. The agent generates it and offers to proceed to the stakeholder urgency review.

WORKFLOW 3️⃣ - Urgency and Sentiment Detection 🕵️‍♀️

The agent scans across all emails and Teams messages in the three-day window, including ADO comments and PR mentions, and surfaces a Needs Immediate Attention panel.

For example, three items are flagged. The external client email thread scores highest, the language in the most recent message includes "we expected this by Friday" and the thread has now been forwarded to a senior contact at the client organisation. A Teams message from an internal lead contains "this is blocking the team" in reference to the overdue ADO item. A third email from a delivery partner uses follow-up language across two consecutive messages with no reply in between.

For the client thread, you select "Draft A Response." CoS produces a professional, measured draft acknowledging the delay, confirming a revised delivery commitment, and offering a brief call to realign. You review it, adjusts one sentence, and confirm you will send it youself from Outlook.

You mark the internal Teams message as handled and will address the blocked ADO item directly as it is already ranked first on your priority list. The delivery partner email is added to the priority list for rescoring.

CoS asks whether to recalculate the priority index. You say yes. The delivery partner item moves up to position four based on the updated urgency score.

WORKFLOW 4️⃣ - Meeting Audit 🧹

CoS retrieves your calendar for the next ten business days and evaluates each meeting.

It flags five meetings as low priority. Two are recurring status syncs that have produced no documented action items in the past three instances. One is a planning meeting you are listed as optional for, with no agenda in the invite. One is a thirty-minute check-in that the agent assesses could be handled with an async message. One is a team catch-up scheduled at the same time as a focus window that maps directly to his top priority item.

For the two recurring status syncs, You select 'Decline With Message'. CoS then drafts a polite note for each, citing current workload priorities, and presents them for your review. You approve both drafts, and keep the optional planning meeting, decline the check-ins with a drafted async alternative, and reschedule team catch-ups to later in the week.

CoS calculates that acting on all recommendations recovers four and a half hours across the week. It asks whether to prepare focus block details aligned to his top three priorities. You confirm.

The agent produces a ready-to-create list of three calendar blocks with titles, availability settings, and descriptions pre-populated. You open Outlook and copy-paste these ready built calendar items.

WORKFLOW 5️⃣ - Alignment Summary

CoS generates a formatted session titled 'Chief of Staff Session - [today's date], containing the locked priority index, all urgency items and their assigned actions, every meeting audit decision, and the focus block details.

It then produces a task creation brief with one entry per locked priority item - task title; due date; priority level; and a note referencing the priority score and primary scoring factor, formatted as a checklist ready to be added to Teams, Planner, To Do, or the ADO board.

CoS closing response: "Your operating plan is set. Priorities are ranked, your task brief is ready to action, and your calendar focus block details are prepared. I am ready for your next review whenever you need it."

✨ Mandatory Agent Configuration 🛠️

Implementation Guide

Prerequisites

• Microsoft 365 Copilot License (Enterprise Premium)
• Access to Copilot Studio Agent Builder

Steps to Create

• Access Copilot Studio Agent Builder in your Microsoft 365 tenant
• Create a new agent – Click "Create an agent" → Select "New agent"
• Copy Description and Instructions highlighted above, and paste to their respective inputs
• Publish and Test

Additional Configuration (Knowledge) ❗DO NOT IGNORE❗

• Ignoring this configuration will result in the agent failing to access your (M365-driven) workload
• Add SharePoint, Teams, and Outlook data sources
• Add other data sources enabled by your organization tenant (in my case it is Azure DevOps)
• Toggle 'enabled' for Only use specified sources (this ensures contextual accuracy)
• Toggle 'enabled' for Reference org chart and profile info (this ensures CoS can gather your skills, and important internal stakeholders)

Optional configuration (Capabilities)

• Toggle 'enabled' for both Create documents, charts, and code and Create images

Final configuration (Suggested prompts)

Title	Message	Rationale
Let's get started	"Run a fresh triage"	Resets your conversation and previous logic
Let's revisit	"Can we go over our last conversation?"	If you have not reset the conversation or memory you can reclaw previous activity
Current standings	"In light of my current productivity, what are my new priorities?"	Gather a current insight, in the event of an item progressing or completion

😎 Looks good. Publish and Test...Go! 🚀

AGENT MAKER DISCLAIMERS

Limitations 🤕

• WRITE actions require manual execution. Chief of Staff cannot create tasks in Planner, To Do, or Azure DevOps, and cannot add calendar entries directly. It produces fully structured briefs and block details ready for you to action. The final step is yours.
• Outbound communication is draft-only. The agent cannot send emails or Teams messages. It drafts, you send. This is intentional by design and enforced regardless of how the agent is prompted.
• Knowledge retrieval is contextual, not exhaustive. The agent retrieves information through Microsoft 365 Copilot's grounding layer. In high-volume environments, some items may not surface. Treat the triage brief as a high-signal view, not a guaranteed complete audit.
• Priority scores are directional, not precise. The scoring model is applied by a language model reasoning over your criteria, not a formula running against structured data. Scores are reliable as a ranked signal. The audit gate is your correction mechanism when they are not.
• Session context does not persist between conversations. The onboarding profile and session output live within the conversation. Starting a new session means re-establishing context. Running the onboarding sequence at the start of each session, or opening with a brief context prompt, keeps the agent calibrated.
• Azure DevOps retrieval is subject to your access permissions. The agent can only surface ADO content you have permission to view. Large boards with many work items may return a representative subset rather than a full board view.

Best practice for users ❗IMPORTANT❗

• Chief of Staff is an advisor, not a decision-maker. It surfaces, ranks, and recommends. Every output it produces is a starting point for your review, not a final instruction. Treat it accordingly.
• Always read before you confirm. The agent will draft emails, meeting declines, and handover notes on your behalf. Read every draft carefully before sending or acting on it. The agent does not know everything you know about a relationship, a conversation, or a context. You do.
• Challenge the scores IF YOU DISAGREE. The Priority Index is a reasoning-based output, not a mathematical calculation. If a ranking does not feel right, use the CHALLENGE action to understand why the score was assigned, then use OMIT or OVERRIDE to correct it. The audit gate exists for exactly this purpose.
• DO NOT skip the onboarding profile. The scoring model is only as good as the context you give it. A profile that accurately reflects your role, your definition of high-impact work, and your priority stakeholders will produce rankings that reflect your reality. A generic profile will produce generic rankings.
• Verify before you act. Before adding a focus block to your calendar or creating a task in Planner from the agent's brief, confirm that the details — due date, priority level, assigned context — are accurate against what you know. The agent reasons over retrieved data and that data is not always complete.
• Stay in control of stakeholder communications. The agent can draft a response in seconds. That speed is its strength and your risk. Stakeholder relationships carry nuance that no agent can fully read. Always apply your own judgment before any message leaves your name.

Help

We do not support samples, but this community is always willing to help, and we want to improve these samples. We use GitHub to track issues, which makes it easy for community members to volunteer their time and help resolve issues.

You can try looking at issues related to this sample to see if anybody else is having the same issues.

If you encounter any issues using this sample, create a new issue.

Finally, if you have an idea for improvement, make a suggestion.

Disclaimer

THIS CODE IS PROVIDED AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING ANY IMPLIED WARRANTIES OF FITNESS FOR A PARTICULAR PURPOSE, MERCHANTABILITY, OR NON-INFRINGEMENT.

---