A personal productivity coach inspired by David Allen's Getting Things Done® methodology, implemented as Claude Code slash commands.
Three skills that map to how GTD actually works:
| Command | When to use | What it does |
|---|---|---|
/gtd-setup |
First time, or starting fresh | Brain dump, source sweep, batch clarify, organize, first review |
/gtd |
Daily | CPORD audit scorecard + interactive coaching |
/gtd-review |
Weekly | Get Clear, Get Current, Get Creative — the full weekly review |
Clone this repo, then symlink or copy the commands:
# Global (available in all projects)
cp -r .claude/commands/gtd*.md ~/.claude/commands/
# Or project-level (one project only)
cp -r .claude/commands/ your-project/.claude/commands/cd ~/my-gtd # or any directory
/gtd-setup # initialize + first brain dump
That's it. The setup walks you through everything.
After setup:
- Run
/gtddaily for a quick audit - Run
/gtd-reviewweekly to stay current
All data is plain markdown in the current directory:
.gtd — sentinel file (presence = initialized system)
inbox.md — raw, unprocessed captures
next-actions.md — concrete next actions, grouped by @context
projects.md — outcomes requiring 2+ actions
waiting-for.md — delegated items (who + what + when)
someday-maybe.md — uncommitted ideas
calendar.md — time-specific actions and events
reference/ — non-actionable info to keep
reviews/ — weekly review logs (YYYY-MM-DD.md)
No database. No app. Just files you can edit anywhere.
CPORD maps GTD's five steps into a loop:
| Step | GTD Term | What You Do |
|---|---|---|
| C | Capture | Collect what has your attention into inbox.md |
| P | Clarify | Process each item — actionable? next action? 2-minute rule? |
| O | Organize | Put it where it belongs — the right list, the right context |
| R | Reflect | Weekly review — update all lists, ensure every project has a next action |
| D | Engage | Simply do — pick by context, time, and energy |
Daily loop: Capture → Clarify → Organize → Do → Capture
Weekly loop: Reflect → Capture → Clarify → Organize → Do
/gtd produces a scorecard each run:
CPORD Audit — March 25, 2026
─────────────────────────────
Capture: 8/10 — inbox has 2 items
Clarify: 6/10 — 5 vague items need next actions
Organize: 9/10 — all items in proper homes
Reflect: 4/10 — last review was 12 days ago
Engage: 7/10 — 8 next actions ready to go
─────────────────────────────
Overall: 7/10
Top 3 actions to improve your system:
1. Do a weekly review — it's been 12 days
2. Clarify "website redesign" into a project with next actions
3. Process the 2 inbox items
The very next physical, visible activity. "Call Dr. Smith to schedule appointment" — not "Doctor stuff."
The test: Can you do this right now with 5 minutes and the right context?
During Clarify: if it takes less than 2 minutes, do it now.
Every Project must have at least one Next Action or it's stuck. You don't "do" projects — you do next actions that move projects forward.
Group next actions by where you are or what you need:
@computer @calls @errands @home @office @waiting @agendas
Define your own as needed.
bin/morning-briefing.sh reads your GTD files, pulls cards from Trello, and sends a daily email via AWS SES.
See bin/.env.example for configuration.
Inspired by Getting Things Done® by David Allen.
MIT