Tag
7 posts
GTD maps cleanly onto a developer workflow once you stop trying to run your life out of GitHub issues. This guide covers the issue-tracker boundary, markdown files as projects, coding agents as delegates on your waiting-for list, and a weekly review that measures shipped work instead of started work.
The two-minute rule is GTD's simplest instruction and its most misunderstood one. This explainer covers where David Allen's rule came from, why the math behind it holds, the mornings where it quietly wrecks your priorities, and the voice-capture twist that makes deferring nearly as cheap as doing.
A GTD inbox works when three things hold: few capture points, a fixed processing routine, and a daily emptying cadence. This walkthrough covers the physical and digital setup, the clarify-first processing rules, and the weekly review that keeps the system trusted.
The GTD weekly review is the habit that keeps the rest of the method alive. This guide walks the clear, current, and creative phases with realistic timing, the checklist that actually gets used, and the fixes for the failure modes that kill the review in the first month.
A weekly review template you can paste into any markdown editor, built on the GTD review sequence: inbox sweep, projects review, next actions, waiting-for, calendar look-ahead, and a shutdown step, plus timing guidance and the mistakes that make reviews slip.
GTD was designed for paper in 2001 and translated poorly to the first generation of task apps. In 2026, AI task managers close the gap. This guide covers the five-step GTD workflow, the digital traps to avoid, and the tools that actually respect the method.
Inbox zero with AI is a state of mind, not a count. This playbook covers the daily ritual, the confidence thresholds, and the review cadence that keeps the inbox actually calm instead of loud in a different way.
