---
title: Getting Things Done (GTD) Workflow
category: Workflows
icon: ⚡
sort_order: 15
slug: gtd-getting-things-done
canonical_url: https://basaltnotes.com/guides/gtd-getting-things-done
markdown_url: https://basaltnotes.com/guides/gtd-getting-things-done.md
---
# Getting Things Done (GTD) in Basalt

Build a low-maintenance, date-free action queue using local Markdown notes, context boards, and universal capture.

---

## The GTD Philosophy in Basalt

Classical Getting Things Done (GTD) by David Allen relies on a fundamental distinction:

1. **The "Hard Landscape" (Calendar & Forge)**: Reserved exclusively for events, meetings, and commitments that *must* happen at a specific date and time.
2. **Next Actions (Context Queues)**: Discretionary tasks grouped by context (`@computer`, `@calls`, `@errands`, `@reading`) rather than artificial due dates.

In many systems, task managers force artificial due dates onto every item, creating visual noise, missed-deadline guilt, and continuous rescheduling overhead. Basalt allows you to operate a pure GTD workflow backed by standard Markdown files without changing your data architecture.

---

## 1. Quick Capture to a Dedicated Inbox

Instead of scattering tasks across dozens of daily notes, configure your quick-add target to write directly to a dedicated Inbox note:

1. Go to the **Tasks** page (`/app/tasks`).
2. In the task creator panel, click **Target: Daily Log** to open destination settings.
3. Switch the destination mode to **Dedicated Inbox Note (GTD Date-Free)**.
4. Set your target note path (for example, `GTD/Inbox.md` or `inbox.md`).
5. Tasks added with the quick creator will now append directly to your inbox note without requiring dates or generating calendar entries.

> **Tip**: You can also send thoughts, links, and snippets from mobile share sheets, browser extensions, or private inbound email directly into the **Capture Inbox** (`/app/capture`).

---

## 2. Setting Up Your Core GTD Notes

A standard Basalt GTD structure consists of four plain Markdown notes in your vault:

### `GTD/Inbox.md`
Your raw capture staging area. Capture thoughts, unprocessed ideas, and action candidates here during the day:
```markdown
# GTD Inbox

> Quick capture staging area. Triage unprocessed items regularly.

## Unprocessed Items
- [ ] Review launch telemetry feedback
- [ ] Research standing desk converters
- [ ] Ask finance about travel stipend
```

### `GTD/Next.md`
Your active, date-free Next Actions list organized by physical context headings or tags:
```markdown
# Next Actions

> Date-free next physical actions organized by context.

## @computer
- [ ] Draft client architecture review #focus
- [ ] Update build dependency lockfile

## @calls
- [ ] Call dentist to confirm appointment #calls

## @errands
- [ ] Pick up hardware package from parcel locker #errands

## @reading
- [ ] Read distributed systems consensus paper #reading
```

### `GTD/Waiting.md`
Tracks items delegated to others or blocked by external dependencies:
```markdown
# Waiting For

> Delegated actions and pending external responses.

## Delegated & Blocked
- [ ] Awaiting security audit report from third-party auditor #waiting
- [ ] Awaiting contract signature from vendor #waiting
```

### `GTD/Someday.md`
Incubating ideas and prospective projects that you are not actively committed to right now:
```markdown
# Someday / Maybe

> Non-active ideas and incubating projects for future review.

## Ideas & Exploration
- [ ] Explore WebAssembly SQLite compilation #someday
- [ ] Plan summer hiking trip #someday
```

---

## 3. Using the GTD Context Action Board

Switch between standard date-filtered views and the GTD Context view right on the Tasks page:

1. Open the **Tasks** page (`/app/tasks`).
2. In the top bar, click the **GTD Contexts** toggle.
3. Your tasks are dynamically organized into context buckets based on their `#tags` (e.g. `#calls`, `#errands`, `#focus`, `#waiting`, `#someday`) and section headings.
4. Artificial "overdue" alert styling is subdued, allowing you to choose actions based on your current physical context, energy level, and available time.

---

## 4. Building Dynamic Task Quarries

In addition to the built-in GTD view, you can use **Quarries** (`/app/quarries`) to build tailored views over your task catalog:

- **Next Actions Kanban**: Filter `rowType: tasks`, `status: Pending`, grouped by `section`.
- **Waiting For List**: Filter `rowType: tasks`, tag `#waiting`, sorted by recent updates.
- **Someday / Maybe Table**: Filter `rowType: tasks`, tag `#someday`.

Once saved, any Task Quarry can be selected directly from the **Filter & Task Quarries** dropdown on the Tasks page to instantly transform your task board into a focused custom queue.

---

## 5. The Low-Maintenance Weekly Review

GTD relies on a regular Weekly Review to keep your queues trustworthy:

1. **Empty Your Inboxes**: Process items in `Capture Inbox` and `GTD/Inbox.md`. Decide if each item is actionable, delegable, deferrable, or archival.
2. **Review Next Actions**: Check off completed items in `GTD/Next.md` and clarify new next physical steps.
3. **Audit Waiting For**: Follow up on items in `GTD/Waiting.md`.
4. **Use AI Intelligence**: Run the built-in `tasks-decisions` task or a custom Prompt Recipe on project notes or meeting transcripts to extract next actions automatically.

---

## 1-Click Starter Setup

To automatically create the four GTD notes (`GTD/Inbox.md`, `GTD/Next.md`, `GTD/Waiting.md`, `GTD/Someday.md`) and preconfigure the saved Task Quarries in your vault, click **Setup GTD** in the Tasks page filter panel or install the **GTD Next Actions** pack from the Pack Library (`/app/packs`).