Builder Capstone: Design an Agent for Your Life

No code. Just design. Pick a real task you do every week and draft a complete agent spec — goal, tools, loop, stop, approvals, and what success looks like.

40 min · Reviewed 2026

The exercise

Pick a task you do every week that you'd rather not. Not coding. Something from your real life — sorting receipts, clipping news, replying to the same kind of email, filing school forms, checking prices on a thing you want to buy. Your job is to design (not build) an agent that could do it.

The spec template

# Agent Spec: [Name your agent]

## 1. Goal
In one sentence, what does success look like?

## 2. Trigger
What starts the agent? (A button, a schedule, an email, my voice?)

## 3. Inputs
What does the agent see to begin? (URL, file path, prompt, calendar.)

## 4. Tools needed
- [ ] Filesystem (which folders?)
- [ ] Browser (which sites?)
- [ ] Email (send, read, or both?)
- [ ] Calendar
- [ ] Shell / code
- [ ] MCP server (which?)
- [ ] Other

## 5. Steps (the loop)
Sketch the think/act/observe cycle for a typical run.

## 6. Stop condition
What makes the agent say 'done'? What makes it give up?

## 7. Approval gates
Which actions need a human yes before running?

## 8. Failure modes
What could go wrong? How would you notice?

## 9. Sandbox
Where will it run? What can it NOT touch?

## 10. Success metric
How will you measure if it's actually helping?Fill this in on paper, in a doc, or in a notes app. Short answers only.

A worked example

# Agent Spec: Weekly Receipt Sorter

1. Goal: At the end of each week, every receipt email is saved as
   a PDF in ~/Finance/2026/ and logged in a running CSV.

2. Trigger: Sunday 6pm, automatic.

3. Inputs: Gmail inbox. Label 'Receipts'.

4. Tools: Gmail MCP, Filesystem (write only to ~/Finance), Code
   execution (for PDF generation + CSV updates).

5. Steps:
   - Fetch new 'Receipts' emails since last run.
   - For each: extract merchant, amount, date. Save as PDF.
   - Append one row to receipts-2026.csv.
   - Mark email as 'Processed'.

6. Stop: No more unprocessed receipt emails, OR 50 emails
   processed (cap), OR an error on 3 consecutive emails.

7. Approvals: None for read/write inside ~/Finance.
   Approval required if any email suggests fraud (flag amounts > $500).

8. Failure modes:
   - Email without a parseable amount → skip + notify.
   - Filesystem full → stop + notify.
   - Gmail API throttle → back off, retry next run.

9. Sandbox: Runs in OpenClaw. Filesystem scope: ~/Finance only.
   Network: Gmail API only.

10. Success metric: Weekly ritual of 'where did I put that receipt'
    takes zero minutes instead of thirty.A real spec you could hand to a developer (or your future self).

Common design mistakes

Goal too vague ('manage my life') — break it down until each agent does one thing.
No stop condition — always set a cap on steps, time, or cost.
Too many tools — if your agent needs 10 tools, it's probably 3 agents.
No failure plan — what if a tool is down? What if the input is weird?
Skipping approvals on risky steps — speed is not worth surprise bills.

When you're ready to actually build — wire up tools, pick a framework, write code — head to the Creators track. You now have the design muscle to ship something safe and useful.

End-of-lesson check

15 questions · take it digitally for instant feedback at tendril.neural-forge.io/learn/quiz/end-agentic-builder-capstone-builders

What is the core idea behind "Builder Capstone: Design an Agent for Your Life"?
1. No code. Just design. Pick a real task you do every week and draft a complete agent spec — goal, tools, loop, stop, approvals, and what success looks like.
2. AI agent
3. Agent suggests recipes that share ingredients so nothing goes bad.
4. outline
Which term best describes a foundational idea in "Builder Capstone: Design an Agent for Your Life"?
1. capstone
2. agent spec
3. design-first
4. success metric
A learner studying Builder Capstone: Design an Agent for Your Life would need to understand which concept?
1. agent spec
2. design-first
3. capstone
4. success metric
Which of these is directly relevant to Builder Capstone: Design an Agent for Your Life?
1. agent spec
2. capstone
3. success metric
4. design-first
Which of the following is a key point about Builder Capstone: Design an Agent for Your Life?
1. Goal too vague ('manage my life') — break it down until each agent does one thing.
2. No stop condition — always set a cap on steps, time, or cost.
3. Too many tools — if your agent needs 10 tools, it's probably 3 agents.
4. No failure plan — what if a tool is down? What if the input is weird?
Which of these does NOT belong in a discussion of Builder Capstone: Design an Agent for Your Life?
1. AI agent
2. Too many tools — if your agent needs 10 tools, it's probably 3 agents.
3. No stop condition — always set a cap on steps, time, or cost.
4. Goal too vague ('manage my life') — break it down until each agent does one thing.
What is the key insight about "Why design-only" in the context of Builder Capstone: Design an Agent for Your Life?
1. AI agent
2. Agent suggests recipes that share ingredients so nothing goes bad.
3. Building comes later — Creators track dives into code. For now, the skill is thinking in agent-shaped ways.
4. outline
What is the key warning about "Define the guardrails first" in the context of Builder Capstone: Design an Agent for Your Life?
1. AI agent
2. Agent suggests recipes that share ingredients so nothing goes bad.
3. outline
4. Before an agent runs, spell out what it's allowed to read, write, and delete.
What is the key insight about "Start small" in the context of Builder Capstone: Design an Agent for Your Life?
1. Your first agent should save 20 minutes a week, not replace your job. Small wins build trust.
2. AI agent
3. Agent suggests recipes that share ingredients so nothing goes bad.
4. outline
Which statement accurately describes an aspect of Builder Capstone: Design an Agent for Your Life?
1. AI agent
2. Pick a task you do every week that you'd rather not. Not coding. Something from your real life — sorting receipts, clipping news, replying t…
3. Agent suggests recipes that share ingredients so nothing goes bad.
4. outline
What does working with Builder Capstone: Design an Agent for Your Life typically involve?
1. AI agent
2. Agent suggests recipes that share ingredients so nothing goes bad.
3. When you're ready to actually build — wire up tools, pick a framework, write code — head to the Creators track.
4. outline
Which best describes the scope of "Builder Capstone: Design an Agent for Your Life"?
1. It is unrelated to agentic workflows
2. It applies only to the opposite beginner tier
3. It was deprecated in 2024 and no longer relevant
4. It focuses on No code. Just design. Pick a real task you do every week and draft a complete agent spec — goal, too
Which section heading best belongs in a lesson about Builder Capstone: Design an Agent for Your Life?
1. The spec template
2. AI agent
3. Agent suggests recipes that share ingredients so nothing goes bad.
4. outline
Which section heading best belongs in a lesson about Builder Capstone: Design an Agent for Your Life?
1. AI agent
2. A worked example
3. Agent suggests recipes that share ingredients so nothing goes bad.
4. outline
Which section heading best belongs in a lesson about Builder Capstone: Design an Agent for Your Life?
1. AI agent
2. Agent suggests recipes that share ingredients so nothing goes bad.
3. Common design mistakes
4. outline

← Back to interactive lesson

Tendril · Builders · Agentic AI

Builder Capstone: Design an Agent for Your Life

No code. Just design. Pick a real task you do every week and draft a complete agent spec — goal, tools, loop, stop, approvals, and what success looks like.

40 min · Reviewed 2026

The exercise

The spec template

# Agent Spec: [Name your agent]

## 1. Goal
In one sentence, what does success look like?

## 2. Trigger
What starts the agent? (A button, a schedule, an email, my voice?)

## 3. Inputs
What does the agent see to begin? (URL, file path, prompt, calendar.)

## 4. Tools needed
- [ ] Filesystem (which folders?)
- [ ] Browser (which sites?)
- [ ] Email (send, read, or both?)
- [ ] Calendar
- [ ] Shell / code
- [ ] MCP server (which?)
- [ ] Other

## 5. Steps (the loop)
Sketch the think/act/observe cycle for a typical run.

## 6. Stop condition
What makes the agent say 'done'? What makes it give up?

## 7. Approval gates
Which actions need a human yes before running?

## 8. Failure modes
What could go wrong? How would you notice?

## 9. Sandbox
Where will it run? What can it NOT touch?

## 10. Success metric
How will you measure if it's actually helping?Fill this in on paper, in a doc, or in a notes app. Short answers only.

A worked example

# Agent Spec: Weekly Receipt Sorter

1. Goal: At the end of each week, every receipt email is saved as
   a PDF in ~/Finance/2026/ and logged in a running CSV.

2. Trigger: Sunday 6pm, automatic.

3. Inputs: Gmail inbox. Label 'Receipts'.

4. Tools: Gmail MCP, Filesystem (write only to ~/Finance), Code
   execution (for PDF generation + CSV updates).

5. Steps:
   - Fetch new 'Receipts' emails since last run.
   - For each: extract merchant, amount, date. Save as PDF.
   - Append one row to receipts-2026.csv.
   - Mark email as 'Processed'.

6. Stop: No more unprocessed receipt emails, OR 50 emails
   processed (cap), OR an error on 3 consecutive emails.

7. Approvals: None for read/write inside ~/Finance.
   Approval required if any email suggests fraud (flag amounts > $500).

8. Failure modes:
   - Email without a parseable amount → skip + notify.
   - Filesystem full → stop + notify.
   - Gmail API throttle → back off, retry next run.

9. Sandbox: Runs in OpenClaw. Filesystem scope: ~/Finance only.
   Network: Gmail API only.

10. Success metric: Weekly ritual of 'where did I put that receipt'
    takes zero minutes instead of thirty.A real spec you could hand to a developer (or your future self).

Common design mistakes

Goal too vague ('manage my life') — break it down until each agent does one thing.
No stop condition — always set a cap on steps, time, or cost.
Too many tools — if your agent needs 10 tools, it's probably 3 agents.
No failure plan — what if a tool is down? What if the input is weird?
Skipping approvals on risky steps — speed is not worth surprise bills.

When you're ready to actually build — wire up tools, pick a framework, write code — head to the Creators track. You now have the design muscle to ship something safe and useful.

End-of-lesson check

15 questions · take it digitally for instant feedback at tendril.neural-forge.io/learn/quiz/end-agentic-builder-capstone-builders

What is the core idea behind "Builder Capstone: Design an Agent for Your Life"?
1. No code. Just design. Pick a real task you do every week and draft a complete agent spec — goal, tools, loop, stop, approvals, and what success looks like.
2. AI agent
3. Agent suggests recipes that share ingredients so nothing goes bad.
4. outline
Which term best describes a foundational idea in "Builder Capstone: Design an Agent for Your Life"?
1. capstone
2. agent spec
3. design-first
4. success metric
A learner studying Builder Capstone: Design an Agent for Your Life would need to understand which concept?
1. agent spec
2. design-first
3. capstone
4. success metric
Which of these is directly relevant to Builder Capstone: Design an Agent for Your Life?
1. agent spec
2. capstone
3. success metric
4. design-first
Which of the following is a key point about Builder Capstone: Design an Agent for Your Life?
1. Goal too vague ('manage my life') — break it down until each agent does one thing.
2. No stop condition — always set a cap on steps, time, or cost.
3. Too many tools — if your agent needs 10 tools, it's probably 3 agents.
4. No failure plan — what if a tool is down? What if the input is weird?
Which of these does NOT belong in a discussion of Builder Capstone: Design an Agent for Your Life?
1. AI agent
2. Too many tools — if your agent needs 10 tools, it's probably 3 agents.
3. No stop condition — always set a cap on steps, time, or cost.
4. Goal too vague ('manage my life') — break it down until each agent does one thing.
What is the key insight about "Why design-only" in the context of Builder Capstone: Design an Agent for Your Life?
1. AI agent
2. Agent suggests recipes that share ingredients so nothing goes bad.
3. Building comes later — Creators track dives into code. For now, the skill is thinking in agent-shaped ways.
4. outline
What is the key warning about "Define the guardrails first" in the context of Builder Capstone: Design an Agent for Your Life?
1. AI agent
2. Agent suggests recipes that share ingredients so nothing goes bad.
3. outline
4. Before an agent runs, spell out what it's allowed to read, write, and delete.
What is the key insight about "Start small" in the context of Builder Capstone: Design an Agent for Your Life?
1. Your first agent should save 20 minutes a week, not replace your job. Small wins build trust.
2. AI agent
3. Agent suggests recipes that share ingredients so nothing goes bad.
4. outline
Which statement accurately describes an aspect of Builder Capstone: Design an Agent for Your Life?
1. AI agent
2. Pick a task you do every week that you'd rather not. Not coding. Something from your real life — sorting receipts, clipping news, replying t…
3. Agent suggests recipes that share ingredients so nothing goes bad.
4. outline
What does working with Builder Capstone: Design an Agent for Your Life typically involve?
1. AI agent
2. Agent suggests recipes that share ingredients so nothing goes bad.
3. When you're ready to actually build — wire up tools, pick a framework, write code — head to the Creators track.
4. outline
Which best describes the scope of "Builder Capstone: Design an Agent for Your Life"?
1. It is unrelated to agentic workflows
2. It applies only to the opposite beginner tier
3. It was deprecated in 2024 and no longer relevant
4. It focuses on No code. Just design. Pick a real task you do every week and draft a complete agent spec — goal, too
Which section heading best belongs in a lesson about Builder Capstone: Design an Agent for Your Life?
1. The spec template
2. AI agent
3. Agent suggests recipes that share ingredients so nothing goes bad.
4. outline
Which section heading best belongs in a lesson about Builder Capstone: Design an Agent for Your Life?
1. AI agent
2. A worked example
3. Agent suggests recipes that share ingredients so nothing goes bad.
4. outline
Which section heading best belongs in a lesson about Builder Capstone: Design an Agent for Your Life?
1. AI agent
2. Agent suggests recipes that share ingredients so nothing goes bad.
3. Common design mistakes
4. outline

← Back to interactive lesson