add-task

/add-task Skill

Properly add tasks to ALL relevant locations, preventing entropy.

Usage

/add-task #acme Call client about user insights
/add-task #phoenix Review contract - backlog
/add-task #content Ship newsletter - waiting
/add-task Fix personal website - someday

---

Syntax

/add-task [#project] <description> [- timeline]

Parameters:

• #project (optional): Project tag - #acme, #phoenix, #content, or omit for cross-project
• description: What the task is
• timeline (optional): backlog, waiting, someday - defaults to "this week"

---

Flow

Phase 1: Parse Input

Extract from user input:

• Project scope: Project name from vault, Personal (no tag), or Cross-project
• Task description: The actual task
• Timeline: This Week (default), Backlog, Waiting On, Someday

Phase 2: Determine Files to Update

Scenario	Files Updated
Project + This Week	PROJECT/_BACKLOG.md (Current Sprint) + TODO.md (This Week)
Project + Backlog	PROJECT/_BACKLOG.md (Next Up) only
Project + Waiting On	PROJECT/_BACKLOG.md + TODO.md (Waiting On section)
Project + Someday	PROJECT/_BACKLOG.md (Future Features) only
Cross-project/Personal	TODO.md only (appropriate section)

Phase 3: Update Project _BACKLOG.md (if applicable)

If task has a project tag, add to project's _BACKLOG.md:

File location: ../my-vault/03_PROJECTS/{{Project}}/_BACKLOG.md

Section mapping:

• This Week → ## Current Sprint
• Backlog → ## Next Up
• Waiting On → ## Current Sprint (with waiting note)
• Someday → ## Future Features

Format:

- [ ] {{Task description}}

Update *Last updated:* timestamp at top of file.

Phase 4: Update TODO.md (if applicable)

If task is for "This Week" or "Waiting On", add to master TODO:

File location: ../my-vault/00_SYSTEM/TODO.md

Section mapping:

• This Week → ## This Week under ### #{{project}} heading
• Waiting On → ## Waiting On section