Skip to content

Commit 345b146

Browse files
Copilotrdmueller
Copilot
and
rdmueller
authored
feat: Add GTD (Getting Things Done) semantic anchor (#75)
Agent-Logs-Url: https://github.com/LLM-Coding/Semantic-Anchors/sessions/358a40cd-737b-420d-a397-c4796f81adc8 Co-authored-by: rdmueller <1856308+rdmueller@users.noreply.github.com>
1 parent 5e550f1 commit 345b146

4 files changed

Lines changed: 143 additions & 0 deletions

File tree

‎docs/anchors/gtd.adoc‎

Lines changed: 54 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,54 @@
1+
= GTD — Getting Things Done
2+
:categories: development-workflow
3+
:roles: software-developer, team-lead, product-owner, educator
4+
:related: para-method, todotxt-flavoured-markdown, definition-of-done
5+
:proponents: David Allen
6+
:tags: personal-productivity, task-management, organization, stress-free, inbox-zero
7+
:tier: 3
8+
9+
[%collapsible]
10+
====
11+
Full Name:: Getting Things Done (GTD)
12+
13+
Also known as:: GTD, GTD by David Allen, GTD Methodology
14+
15+
[discrete]
16+
== *Core Concepts*:
17+
18+
Capture:: Collect everything that has your attention — tasks, ideas, commitments — into trusted external "inboxes" so nothing is held in your head
19+
20+
Clarify:: Process each captured item: Is it actionable? If yes, define the next physical action. If no, trash it, incubate it, or file it as reference
21+
22+
Organize:: Place clarified items into the right lists — Next Actions, Projects, Waiting For, Someday/Maybe, Calendar — so they are retrievable at the right moment
23+
24+
Reflect:: Review your system regularly (Weekly Review) to keep it current, complete, and trusted
25+
26+
Engage:: Choose which actions to take based on context, time available, energy, and priority
27+
28+
Two-Minute Rule:: If an action takes less than two minutes, do it immediately rather than deferring it
29+
30+
Projects List:: Any desired outcome requiring more than one action step is a "project" tracked on a dedicated list with at least one next action
31+
32+
Contexts:: Next actions are tagged by context (e.g., @computer, @phone, @errands) to batch work efficiently
33+
34+
Trusted System:: All commitments are stored externally so the mind is free to focus on doing rather than remembering
35+
36+
Key Proponent:: David Allen ("Getting Things Done: The Art of Stress-Free Productivity")
37+
38+
[discrete]
39+
== *When to Use*:
40+
41+
* Managing a high volume of tasks, projects, and commitments across work and personal life
42+
* Reducing mental load and anxiety caused by open loops (unfinished commitments)
43+
* Setting up a reliable personal productivity and task management system
44+
* Improving focus by clarifying next actions rather than vague to-do items
45+
* Onboarding teams or individuals to structured workflow management
46+
* Combining with note-taking systems such as P.A.R.A. or todo.txt
47+
48+
[discrete]
49+
== *Related Anchors*:
50+
51+
* <<para-method,P.A.R.A. Method>>
52+
* <<todotxt-flavoured-markdown,todo.txt-flavoured Markdown>>
53+
* <<definition-of-done,Definition of Done>>
54+
====

‎docs/anchors/gtd.de.adoc‎

Lines changed: 54 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,54 @@
1+
= GTD — Getting Things Done
2+
:categories: development-workflow
3+
:roles: software-developer, team-lead, product-owner, educator
4+
:related: para-method, todotxt-flavoured-markdown, definition-of-done
5+
:proponents: David Allen
6+
:tags: personal-productivity, task-management, organization, stress-free, inbox-zero
7+
:tier: 3
8+
9+
[%collapsible]
10+
====
11+
Vollständiger Name:: Getting Things Done (GTD)
12+
13+
Auch bekannt als:: GTD, GTD nach David Allen, GTD-Methodik
14+
15+
[discrete]
16+
== *Kernkonzepte*:
17+
18+
Erfassen (Capture):: Alles, was die Aufmerksamkeit beansprucht – Aufgaben, Ideen, Verpflichtungen – wird in vertrauenswürdige externe „Eingangsboxen" gesammelt, damit nichts im Kopf gehalten werden muss
19+
20+
Klären (Clarify):: Jeden erfassten Eintrag verarbeiten: Ist er umsetzbar? Wenn ja, die nächste konkrete Handlung definieren. Wenn nein, löschen, zurückstellen oder als Referenz ablegen
21+
22+
Organisieren (Organize):: Geklärte Einträge in die richtigen Listen einordnen – Nächste Aktionen, Projekte, Warte-auf, Irgendwann/Vielleicht, Kalender – damit sie zum richtigen Zeitpunkt abrufbar sind
23+
24+
Überprüfen (Reflect):: Das System regelmäßig überprüfen (Wöchentliches Review), um es aktuell, vollständig und vertrauenswürdig zu halten
25+
26+
Handeln (Engage):: Entscheiden, welche Aktionen basierend auf Kontext, verfügbarer Zeit, Energie und Priorität ausgeführt werden
27+
28+
Zwei-Minuten-Regel:: Wenn eine Aktion weniger als zwei Minuten dauert, sofort erledigen statt verschieben
29+
30+
Projektliste:: Jedes gewünschte Ergebnis, das mehr als eine Handlungsschritt erfordert, ist ein „Projekt" mit mindestens einer nächsten Aktion
31+
32+
Kontexte:: Nächste Aktionen werden nach Kontext getaggt (z.B. @computer, @telefon, @besorgungen), um Aufgaben effizient zu bündeln
33+
34+
Vertrauenswürdiges System:: Alle Verpflichtungen werden extern gespeichert, damit der Geist frei ist, sich auf das Handeln zu konzentrieren statt auf das Erinnern
35+
36+
Schlüsselvertreter:: David Allen („Getting Things Done: The Art of Stress-Free Productivity")
37+
38+
[discrete]
39+
== *Wann zu verwenden*:
40+
41+
* Verwaltung einer hohen Anzahl von Aufgaben, Projekten und Verpflichtungen in Beruf und Privatleben
42+
* Reduzierung mentaler Belastung und Stress durch offene Schleifen (unerledigte Verpflichtungen)
43+
* Aufbau eines zuverlässigen persönlichen Produktivitäts- und Aufgabenmanagementsystems
44+
* Verbesserung der Konzentration durch Klärung konkreter nächster Aktionen anstelle vager To-do-Einträge
45+
* Einführung von Teams oder Einzelpersonen in strukturiertes Workflow-Management
46+
* Kombination mit Notizsystemen wie P.A.R.A. oder todo.txt
47+
48+
[discrete]
49+
== *Verwandte Anker*:
50+
51+
* <<para-method,P.A.R.A. Method>>
52+
* <<todotxt-flavoured-markdown,todo.txt-flavoured Markdown>>
53+
* <<definition-of-done,Definition of Done>>
54+
====

‎skill/semantic-anchor-translator/references/catalog.md‎

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -305,6 +305,11 @@ Source: https://github.com/LLM-Coding/Semantic-Anchors
305305

306306
## Development Workflow
307307

308+
### GTD — Getting Things Done
309+
- **Also known as:** GTD, GTD by David Allen, Getting Things Done Methodology
310+
- **Proponents:** David Allen
311+
- **Core:** Five-step workflow — Capture (collect all open loops into trusted inboxes), Clarify (define next physical action or discard), Organize (sort into Next Actions/Projects/Waiting For/Someday/Calendar lists), Reflect (weekly review), Engage (act based on context/time/energy); Two-Minute Rule; context tagging (@computer, @phone); trusted external system frees mental RAM
312+
308313
### Definition of Done
309314
- **Also known as:** DoD, Done Criteria
310315
- **Proponents:** Ken Schwaber, Jeff Sutherland

‎website/public/data/anchors.json‎

Lines changed: 30 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1408,6 +1408,36 @@
14081408
"filePath": "docs/anchors/grasp.adoc",
14091409
"tier": 3
14101410
},
1411+
{
1412+
"id": "gtd",
1413+
"title": "GTD — Getting Things Done",
1414+
"categories": [
1415+
"development-workflow"
1416+
],
1417+
"roles": [
1418+
"software-developer",
1419+
"team-lead",
1420+
"product-owner",
1421+
"educator"
1422+
],
1423+
"related": [
1424+
"para-method",
1425+
"todotxt-flavoured-markdown",
1426+
"definition-of-done"
1427+
],
1428+
"proponents": [
1429+
"David Allen"
1430+
],
1431+
"tags": [
1432+
"personal-productivity",
1433+
"task-management",
1434+
"organization",
1435+
"stress-free",
1436+
"inbox-zero"
1437+
],
1438+
"filePath": "docs/anchors/gtd.adoc",
1439+
"tier": 3
1440+
},
14111441
{
14121442
"id": "gutes-deutsch-wolf-schneider",
14131443
"title": "Gutes Deutsch nach Wolf Schneider",

0 commit comments

Comments
 (0)