Build a Claude Code Multi-Agent Pipeline (Microsoft 365)

# Build a Claude Code Multi-Agent Pipeline (Microsoft 365) ## Overview I need an experienced Claude Code developer to build a sequential multi-agent pipeline that prepares a weekly executive 1:1 journal. You will build and fully test it against your own Microsoft 365 account, then hand off the finished agent files for me to drop into my project folder. You will not need access to my data; the connector resolves at runtime on my machine. ## What it does A single trigger runs the pipeline end to end: 1. **Five collector subagents run in parallel**, each in its own clean context, each writing one signal file: - Calendar (Outlook) - Teams chats - Email (Outlook, sent + received) - Meeting transcripts (arrive via email attachment, auto-archived) - Prior Claude conversation threads 2. **Synthesis subagent** reads all five files, clusters themes across sources. 3. **Checkpoint** surfaces the synthesis for my review. 4. **Draft subagent** applies an editorial brief I provide (section rules + a relevance filter), assigns each item to exactly one of six sections. 5. **Publish** updates an existing HTML journal file on my Desktop. Each stage hands off through saved files. Clean-context isolation between stages is the core design principle. ## Key requirements - Built in **Claude Code** using the `.claude/agents/` subagent structure (markdown agent definitions). - Uses the **Microsoft 365 MCP connector** for calendar, Teams, and email retrieval. - **Teams rate limiting (HTTP 429) is the hard problem.** A one-pass, full-week Teams pull does not work. You must implement **date-slicing** (day-by-day or small chunks) so retrieval reliably reaches the full window. Do not hand off a version that only covers the most recent day. - Dynamic date window: the pipeline reads a "last updated" timestamp from the journal HTML and pulls everything since then. - Fixed output filenames, overwritten each run (no accumulating files). - Collectors must **never fabricate data**; note gaps honestly when a source is incomplete. - Strict formatting rules I will provide (tight one-line-per-item, initials for known people, specific style constraints). ## What I will provide - The editorial brief (six section definitions + relevance filter + dedup rules). - My Desktop file path and initials roster (simple string values to set). - The existing HTML journal file to publish into. - A working single-skill version that shows the intended logic to decompose. ## What you deliver - All agent definition files, tested and working against your own M365. - Brief setup notes: where files go, how to trigger, and any find-and-replace I need to run for my connector name and path. - The Teams collector proven to reach a full 7-to-14-day window via date-slicing. ## Skills required - Prior hands-on Claude Code experience (subagents, MCP tool configuration). - Microsoft 365 / Microsoft Graph familiarity, especially rate-limit handling. - Comfort with markdown agent definitions and prompt design. ## Scope + timeline Estimated **8 to 15 hours**. The five collectors and synthesis/draft/publish stages are straightforward; **budget most of the time for the Teams date-slicing**, which is where the real engineering is. Please confirm in your proposal that you have built Claude Code subagents before and describe how you would handle the Teams 429 limit.