Scott Farrar Puts AI Household Wins on the Wall

Key Takeaways

• Scott Farrar connects Obsidian Markdown files to a physical DAKboard wall display so his family sees household progress without opening an app.
• A custom script extracts four distinct feeds from Farrar's database: active to-do items, upcoming travel dates, micro-tasks, and completed wins.
• Claude Code runs daily audit checks against open files, actively tracking vendor lag like follow-ups pending since September 24th.
• Farrar prevents chore exhaustion by logging closed tickets in a visible "recent wins" feed, spotlighting fixes like same-day water heater repairs and iPad updates.
• The workflow runs on Scott Farrar's Household Project Management Lifecycle.

Scott Farrar's Household Project Management Lifecycle

• Step 1: Capture in Backlog Idea File: Log loose, unvetted thoughts or raw physical observations (such as earthquake readiness, paint peeling, or breaker box handwriting) into an ideas backlog Markdown file without promoting them to active status.
• Step 2: Initialize Project File and Checklist: Promote an idea to a dedicated project Markdown file using Claude instructions (claude.md) to collect relevant context, estimate costs, assign priority levels, and generate an actionable checklist of next steps and blocking items.
• Step 3: Grounded Execution and Agent Accountability: Use Claude Code in new chat sessions to reference the project file, prompt external actions (e.g., drafting specific emails to vendors or agents), and track waiting periods with explicit reminder dates.
• Step 4: Project Closure and Wall Display Broadcast: Close the project file once items are completed, transfer the resolution to the 'recent wins' column, and run an automated script that surfaces the win on the household DAKboard wall display.

When This Works (and When It Doesn't)

Farrar's lifecycle works when domestic management suffers from invisible drag. When household chores sit in your head, small tasks feel like emergencies. Pushing updates through local Markdown files gives an AI coding agent clean text to parse, making domestic operations run like engineering sprints. “It really has moved me forward on so many projects that I have actually run out of pending fires,”▶ 22:19 (play from 22:19) Farrar notes.

This system breaks down if you do not want to maintain local developer tools for domestic life. If running terminal commands, maintaining custom Python scraping scripts, or configuring Obsidian plugins feels like a second job, the backlog will rot in your file tree. It also fails if your partner dislikes seeing project management boards outside of work hours.

What to Do With This

Take your most delayed administrative nightmare this week, such as shopping for commercial office insurance or auditing SaaS seat licenses.

First, make a single Markdown file titled office-insurance-2025.md. Second, feed your current policy and vendor quotes into Claude Code along with a system prompt that outlines your budget caps and policy minimums. Third, instruct the agent to generate three comparison columns and draft the exact rejection emails for the two vendors you cut. Once you sign the policy, move the completed file into an archive folder, log the annual cost savings in a plain text file, and put the completed task in a public channel or a common room screen. Closing tickets visibly trains your brain to stop tracking resolved problems.