This file outlines the project to design, implement, and document a comprehensive, integrated workflow for Atomic Notes (Zettelkasten) and GTD using Org-mode, with the ultimate output being an agent skill.

Atomic Notes (Zettelkasten) & GTD in Org-mode Project

Goal:* To design, implement, and document a comprehensive, integrated workflow for Atomic Notes (Zettelkasten) (knowledge management) and Getting Things Done (GTD - task management) using Org-mode. The ultimate output of this project will be an agent skill.*

Key Integrations:*

Emacs:* Primary access and powerful Org-mode features.
Android Tools:* Ensure seamless access and functionality via Markor and Orgzly (revived).

Strategic Importance:* This system will become the primary coordination method for our work, outside of direct chat communication. It will centralize task tracking, knowledge capture, and project management.

Workflow Details & Current Setup (as provided by Amr):*

Org-mode File Front Matter:* For each Org-mode file, there must be a basic front matter. At minimum, this must include a `#+TITLE:`, an `#+AUTHOR:`, and a `#+CREATED:` date. Short descriptive comments within a `#+BEGIN_COMMENT` / `#+END_COMMENT` block are also highly recommended.
Inbox File:* `memex/inbox.org`. All new captured items will go here. No other files in the inbox collection are to be used for general inbox capture.
GTD.org Structure:* Contains four top-level `*` headings:
- `* Actions`: For standalone actionable items.
- `* Projects`: Contains `*` headers for each project, with `***` headers for actionable items within those projects.
- `* Incubate`: For placeholders for future projects.
- `* Habits`: Tracks recurring personal habits, potentially to be used as a heartbeat for the new AI agent.
:CREATED: Property:* All items in `memex/inbox.org` and `GTD.org` must include a `:CREATED:` property in their `:PROPERTIES:` drawer. The date format is `[YYYY-MM-DD Day HH:MM]`.
:LOGBOOK: Drawer:* All task items must include a `:LOGBOOK:` drawer AFTER the `:PROPERTIES:` drawer (not nested inside). State changes are logged as `- State "NEW" from "OLD" [timestamp]`. This tracks the full history of state transitions for each task.
Org-Todo States:* Items will use the following `org-todo` keywords to indicate status: `NEXT`, `TODO`, `WAIT`, `DONE`, `CNCL`. It is understood that these states are used to make tasks appear in Amr's Emacs and Orgzly agendas, serving as a direct mechanism for communicating required actions.
Authorship & Assignment:* Confirmed use of `:AUTHOR:` (for original creator) and `:ASSIGNED:` (for current responsible individual). It is noted that filtering by `:ASSIGNED:` is possible in Emacs, with potential uncertainties for Orgzly.
User Interaction Requirements (Emacs, Orgzly, Markor):*
- Ability to follow status of actionable items in Org-zly and Emacs agendas.
- Ability to read and write Org-mode files in Emacs and Markor.
- Ability to find out and manipulate `TODO` items in Org-zly and Emacs agendas.
Agent-User Coordination Mechanism:* The agent will place items requiring Amr's attention as `TODO` (general planned items) and `NEXT` (immediate, high-priority actions) in his agenda.
Automatic `NEXT` Promotion:* A critical feature to integrate is the automatic promotion of a `TODO` item to `NEXT` in `org-gtd` once the preceding `NEXT` item (within a sequential Project) is marked `DONE`. This behavior specifically applies to interdependent or sequential items that constitute a `Project`. Standalone `NEXT` items (e.g., under `* Actions`) are `NEXT` by default and do not trigger subsequent promotions. This behavior must be accounted for in the agent skill.

Initial Scope:*

Ensure all items I create or modify adhere strictly to the `:CREATED:` property format and `org-todo` states.
Implement the proposed `:AUTHOR:` and `:ASSIGNED:` properties for collaborative items.
Defining specific Org-mode structures for Atomic Notes (Zettelkasten) notes (unique IDs, linking, tags), building upon existing GTD structure.
Establishing workflows for daily capture, processing, and review aligned with Amr's system.
Exploring and configuring Markor and Orgzly for optimal mobile interaction with Org files.
Documenting the entire workflow for clarity and ease of use.

Information Needed from Amr:*

Confirmation or modification of the proposed `:AUTHOR:` and `:ASSIGNEE:` properties (e.g., preferred format for names, single vs. multiple assignees).
Specific requirements or desired features for mobile access/editing with tools like Markor and Orgzly.
Your vision for how this system will function as our "main coordination method"* in practice.
Any existing Org-mode Atomic Notes (Zettelkasten) practices you currently use or prefer.

Next Steps:*

Gather Amr's current practices and specific requirements.
Begin outlining core Org-mode structures for both Atomic Notes (Zettelkasten) and GTD.
Research best practices for mobile Org-mode synchronization and editing with Markor/Orgzly.