Project Brief

Time to build something real. Not a tutorial project — something that solves an actual problem in your work. The goal: apply at least 3 modules from this course in one project.

Choosing Your Project

Pick a project that:

• Solves a real pain point (not a toy example)
• Can be built in 2-4 hours
• Uses tools and data you already have
• Can be tested and evaluated

Option A: MCP Bridge Server

Build an MCP server that connects two of your existing tools. Examples:

• Obsidian + Linear: Search meeting notes for action items, auto-create tickets
• PostHog + Notion: Fetch weekly metrics, generate report page
• Calendar + Slack: Check tomorrow's meetings, send prep summaries to yourself

Modules applied: Tool Use (M1), MCP Servers (M5), Eval Frameworks (M6)

Option B: RAG System over Obsidian

Build a retrieval system over your 279+ meeting notes, accessible via an MCP tool. Features:

• Chunk meeting notes by section with metadata
• Store embeddings in Supabase pgvector
• Search by semantic query + project/date filters

Modules applied: RAG (M3), MCP Servers (M5), Eval & Testing (M6)

Option C: Multi-Agent Workflow

Build a multi-agent system for a client process. Example:

• Agent A: Data gatherer (PostHog metrics, Linear issues)
• Agent B: Narrative writer (turns data into human-readable insights)
• Agent C: Formatter + delivery (creates deliverable, posts to Slack)

Modules applied: Multi-Agent (M4), Orchestration (M4), Shipping (M6)

Option D: Your Own Idea

Combine 2+ modules to solve a problem unique to your work. Write the brief below.

The Brief Template

Your project brief should cover:

1. Problem: What pain point does this solve? Be specific.
2. User: Who uses this? (You, your team, a client?)
3. Architecture: Which agent pattern? (Router, orchestrator, pipeline, ReAct)
4. Tools needed: List every tool/API the agent needs
5. Success criteria: How do you know it works? (3 specific, testable conditions)
6. Eval plan: At least 3 eval cases (happy path, edge case, error case)