Capstone spec template

Fill this out by end of Week 2 Saturday. One page maximum.

Five sections. Be specific. Vague specs lead to vague capstones.

1. Domain & target user

Who is this for? What domain are you tracking?

Example: Software engineers tracking new open-source projects in the agentic-AI space. Specifically people who want a 90-second briefing on what shipped this week without reading 50 GitHub repos.

2. Sources (at least 3 types)

What do you pull from? Aim for at least 3 distinct source types — RSS, scraping, platform APIs.

• Source 1: type + URL or API + how often new content arrives
• Source 2: ...
• Source 3: ...

3. Relevance description (the Skill)

Prose paragraph describing what counts as "relevant" for this topic. This becomes a Skill that scores each item.

Example: Relevant items are public announcements (not internal commits) of new agentic-AI frameworks, libraries, or significant feature releases. Tutorials and opinion pieces are NOT relevant. The signal is "something new exists in the world that I can use."

4. Output format(s) (at least 1 multi-modal)

What does the user get, and how often? At least one output beyond plain text.

Options: email digest (Resend), in-app podcast (ElevenLabs), in-app video (Marp + ffmpeg), notes page, exported PDF.

5. Acceptance criteria for Demo Day

What proves this works? Three concrete checks the audience could verify.

Review

Schedule a 10-min spec review with Kamal or a TA during the Week 2 capstone work block. Specs locked by 4:00 PM Saturday.