// Create or schedule a context farmer. Checks existing farmers and offers to build new ones or schedule existing ones.
End of day review - compare planned vs actual, update task statuses. Part of chief-of-staff system.
Delegate a task by forking a terminal session to a new terminal window. Use this when the user requests 'delegate' or 'create a new terminal' or 'new terminal: <command>' or 'fork session: <command>'.
Manually trigger a context farmer subagent. Usage - /farm <name> (e.g., /farm slack)
Quick capture - classify and file natural language input into the vault. Part of chief-of-staff system. Use for capturing tasks, ideas, project notes, or people notes.
Initialize a new Second Brain vault from a template repo — validate privacy, create folders, push, and onboard the user.
Generate daily plan from due tasks and active projects. Part of chief-of-staff vault system.
| name | create-farmer |
| description | Create or schedule a context farmer. Checks existing farmers and offers to build new ones or schedule existing ones. |
| user-invocable | true |
Check what already exists before asking the user anything:
Glob for .claude/agents/*-farmer.md/schedule (the schedule skill) with action list to see what's already running — or use RemoteTrigger directly if availableAsk what source to farm. Then check if an MCP server is already connected — use ToolSearch to look for tools matching that service name. If nothing found, search for an official remote-hosted MCP server and help them connect it.
Use ToolSearch to discover all tools for the service. Test 1-2 read-only tools to verify connectivity and understand data shape.
Ask what to monitor (channels, senders, calendars, keywords, URLs) and any custom classification rules beyond vault defaults.
Create .claude/agents/<name>-farmer.md. Read an existing farmer (e.g., slack-farmer.md) as a structural reference.
Frontmatter:
---
name: <name>-farmer
description: Farms context from <source> into the vault
model: sonnet
permissionMode: acceptEdits
---
Rules:
tools field — MCP tools and ToolSearch inherited from parentmcpServers — doesn't work for remote MCPs; ToolSearch handles discoverypermissionMode: acceptEdits-farmer — matches SubagentStop hook for auto-pushBody must include:
| Tool | Purpose | table with bare names. Read/search tools only.All farmer-created files must include source: farmer/<name> and farmed: <timestamp> in frontmatter.
Add the farmer's read-only MCP tools to .claude/settings.json under permissions.allow. Only add read/search/list tools — never write/send/delete.
Add a section to context/watchlists.md for the new source's filters.
After building, ask if they want to schedule it now. If yes, follow the scheduling flow below.
Use /schedule to create a cloud scheduled trigger. The prompt should be /farm <name>.
Key details to confirm:
Farmers must run as subagents via /farm <name>, not inline prompts — this gives isolated context and triggers the SubagentStop hook for auto-push.
/loop 30m /farm <name> — active session only./farm <name> — on demand.