org-agent-contrib/org-skill-gtd.org

SKILL: Getting Things Done (GTD) (Universal Literate Note)

• Overview
• Phase A: Demand (PRD)
  • 1. Purpose
  • 2. User Needs
  • 3. Success Criteria
    • Commitment Scanning
    • PSF-State Transition Verification
    • Stalled Project Identification
• Phase B: Blueprint (PROTOCOL)
• Phase B: Blueprint (PROTOCOL)
  • 1. Architectural Intent
  • 2. Semantic Interfaces (Lisp Signatures)
    • Function: `gtd/capture-task`
    • Function: `gtd/clarify-task`

Overview

This skill defines the GTD Execution Hub, the single source of truth for all commitments. It governs how the agent perceives priorities and tracks progress through the PSF Consensus Loop using the `org-gtd` v4.0 DAG architecture.

Phase A: Demand (PRD)

1. Purpose

Define the interfaces for task perception, project tracking, and commitment management.

2. User Needs

• Allen-Sovereign Methodology: Frictionless capture and rigorous clarification.
• DAG Structure: Support for `org-gtd` v4.0 dependency graphs (:TRIGGER:, :BLOCKER:).
• Shadow Orchestration: Tracking of `:PSF-STATE:` properties for engineering projects.
• Institutional Memory Integration: Extraction of learnings before project completion.

3. Success Criteria

TODO Commitment Scanning

TODO PSF-State Transition Verification

TODO Stalled Project Identification

Phase B: Blueprint (PROTOCOL)

Phase B: Blueprint (PROTOCOL)

1. Architectural Intent

The GTD Execution Hub will be implemented as a collection of functions operating on the `org-gtd` v4.0 DAG. It will provide a consistent interface for task capture, clarification, and execution status monitoring. Key elements include:

• Capture and Clarify: Functions to create, process, and integrate new tasks into the DAG.
• Dependency Management: Functions to navigate and update dependencies based on `:TRIGGER:` and `:BLOCKER:` properties.
• PSF-State Tracking: Functions to monitor and report on `:PSF-STATE:` transitions.
• Completion Review: Functions to summarize completed projects and extract lessons learned.

The system should be modular and extensible, allowing for easy integration with other PSF components and external data sources.

2. Semantic Interfaces (Lisp Signatures)

Function: `gtd/capture-task`

Capture a new task and integrate it into the appropriate context.

:signature `((description string) (context keyword) &optional (project org-id)) :returns org-id` :description "Capture a new task described by DESCRIPTION and add it to CONTEXT. If PROJECT is specified, link the new task as a subtask of PROJECT."

Function: `gtd/clarify-task`

Process a newly captured task, adding details and dependencies.

:signature `((task-id org-id) (details alist)) :returns org-id` :description "Clarify a task, adding details and dependencies specified in the DETAILS alist. Example: '((:priority \