Scans the last 24 hours of email, Teams chats and meeting transcripts for commitments in both directions, things the user promised to others and things others promised to the user. Maintains a running commitments.md ledger with open, done and overdue statuses, flags overdue items first, and creates To Do entries with a file fallback. Use when the user asks what they promised, what they are owed, whether they missed a commitment, or to run a daily commitment sweep.
Builds a role-tuned morning brief as a Word document covering emails that need replies, today's calendar, Teams mentions and upcoming deadlines, using section presets from an editable config file. Use when the user asks for their daily brief, morning brief, start-of-day summary or custom briefing, or wants to change which sections their brief covers.
Generates a self-contained single-file HTML project dashboard (status banner, milestones, risks heat list, decisions log, links) from the tracker files in /Documents/Cowork/projects/, saved as dashboard-<project>-YYYY-MM-DD.html. Use when the user asks for a project dashboard, a shareable or pinnable status page, an HTML project overview, or a one-page visual summary of milestones, risks and decisions.
Sweeps the inbox, categorises every message as needs-reply-today, needs-reply-this-week, waiting-on-others, FYI or noise, creates reply drafts in the Drafts folder, and saves a dated triage report to OneDrive. Moves or archives mail only when a rule the user wrote in its rules file says so. Use when the user asks to triage, sort, clean up or catch up on their inbox, or asks what needs a reply today.
Reviews a proposal, business case, deck or plan in character as a Chief Business Officer archetype, covering commercial model, partnerships, deal structure, market positioning, strategic fit and opportunity cost. Produces a DRAFT review document with a verdict, findings that cite the artifact, risks and five interrogation questions. Use when the user asks for a CBO review, a commercial pressure-test of a document, or to prepare a proposal for an executive meeting.
Reviews a proposal, business case, deck or plan in character as a Chief Data Officer archetype, then saves a structured review document with a verdict, findings that cite the artifact, data and AI governance risks and five interrogation questions. Use when the user asks for a CDO review, a data or AI governance pressure-test of a document, or to prepare for a real CDO, data governance or privacy review meeting.
Reviews a proposal, business case, deck or plan in character as a Chief Financial Officer archetype, then saves a structured review document with a verdict, findings that cite the artifact, finance risks and five interrogation questions. Use when the user asks for a CFO review, a finance-lens pressure-test of a document, or to prepare for a real CFO or finance review meeting.
Reviews a proposal, business case, deck or plan in character as a Chief Human Resources Officer archetype, then saves a structured review document with a verdict, findings that cite the artifact, people and organisation risks and five interrogation questions. Use when the user asks for a CHRO or HR review, a people-lens pressure-test of a document, or to prepare for a real CHRO, people committee or works council meeting.
Reviews a proposal, business case, deck or plan in character as a Chief Information Security Officer archetype, producing a DRAFT review document with a verdict, findings cited to specific passages, security and compliance risks, and the five interrogation questions a real CISO would ask. Use when the user asks for a CISO review, a security or compliance pressure-test of a document, or help preparing for an executive review where security, privacy or third-party risk will be challenged.
Reviews a proposal, business case, deck or plan in character as a Chief Marketing Officer archetype, producing a structured DRAFT review document with a verdict, findings cited to specific passages, risks and five interrogation questions. Use when the user asks for a CMO review, a marketing executive's read on a document, or wants to pressure-test positioning, messaging, pricing or a launch plan before a real executive review.
Reviews a proposal, business case, deck or plan in character as a Chief Operating Officer archetype, producing a structured review document with a verdict, findings cited to specific sections, delivery risks and five interrogation questions. Use when the user asks for a COO review, an operations review, or wants to pressure-test execution feasibility, capacity, timelines or cross-team dependencies before a real executive meeting.
Reviews a proposal, business case, deck or product plan in character as a Chief Product Officer archetype, then saves a structured review document with a verdict, findings that cite the artifact, product and adoption risks and five interrogation questions. Use when the user asks for a CPO review, a product-lens pressure-test of a document, or to prepare for a real CPO or product leadership review meeting.
Reviews a proposal, business case, deck or plan in character as a Chief Revenue Officer archetype, producing a structured review document with a verdict, evidence-cited findings, revenue risks and five interrogation questions. Use when the user asks for a CRO review, a revenue-lens pressure test, or to challenge a document the way a sales leadership executive would before a real review meeting.
Reviews a proposal, business case, deck or plan in character as a Chief Technology Officer archetype, producing a structured DRAFT review document with a verdict, findings cited to specific parts of the artifact, technology risks and five interrogation questions. Use when the user wants a CTO review, a technical pressure-test of a document, or to rehearse the technology seat of an executive review before the real meeting.
Reviews a proposal, business case, deck or plan in character as a Customer Advocate archetype, then saves a structured review document with a verdict, findings that cite the artifact, customer-side risks and five interrogation questions. Use when the user asks for a customer advocate review, a customer-lens or voice-of-the-customer pressure-test of a document, or wants to know what a plan really asks of paying customers before approving it.
Reviews a proposal, business case, deck or rollout plan in character as a Frontline Skeptic archetype, the experienced staff member who will have to live with the change, then saves a structured review with a verdict, findings that cite the artifact, adoption risks and five interrogation questions. Use when the user asks for a frontline review, an adoption-lens pressure-test of a plan, or asks what the people who do the work will say about it.
Reviews a proposal, business case, deck or plan in character as a General Counsel archetype, then saves a structured review document with a verdict, findings that cite the artifact, legal risks and five interrogation questions. Use when the user asks for a legal review, a general counsel pressure-test of a document, or to prepare for a real legal, contract or deal review meeting.
Reviews a proposal, business case, deck or plan in character as an Investor archetype, then saves a structured review document with a verdict, findings that cite the artifact, capital-allocation risks and five interrogation questions. Use when the user asks for an investor review, a capital-lens pressure-test of a document, or to prepare for a funding pitch, investment committee or sponsor meeting.
Reviews a proposal, business case, deck or vendor contract in character as a Head of Procurement archetype, then saves a structured review document with a verdict, findings that cite the artifact, commercial risks and five interrogation questions. Use when the user asks for a procurement review, a commercial or vendor-lens pressure-test of a document, or to prepare for a real procurement, sourcing or contract review meeting.
Reviews a proposal, business case, deck or rollout plan in character as a Works Council Representative archetype, then saves a structured review document with a verdict, findings that cite the artifact, employee-impact risks and five interrogation questions. Use when the user asks for a works council review, an employee-representative pressure-test of a document, or to prepare for a real works council, staff council or employee consultation meeting.
Plain text files in a repository that tell a coding agent how the project works: commands to run, conventions to follow and things to avoid. CLAUDE.md, AGENTS.md, cursor rules and skills are the common kinds.
CLAUDE.md or AGENTS.md?
CLAUDE.md is read by Claude Code. AGENTS.md is an open format that Codex, Cursor and other agents read. Many projects keep one and point the other at it.
What is a skill?
A folder with a SKILL.md that describes one capability, such as filling PDFs or reviewing code. The agent loads it only when the task calls for it.
Can I search my own team's files too?
Your agents already can, over MCP, limited to the files you're allowed to read. Searching them from this page is coming.