Tasks
Every action that changes something goes through the task pipeline.
The Pipeline
Tasks live in five folders. Each folder represents a stage in the lifecycle.
| Folder | What Belongs Here | Who Moves It |
|---|---|---|
| backlog/ | Proposed tasks awaiting approval. Agents write here. | Agent proposes, human approves |
| ready-to-start/ | Approved tasks ready for execution. Green light from the human. | Human approves via /tasks |
| in-progress/ | Currently being worked on. One agent owns each task. | Agent picks up via /get-shit-done |
| waiting-for-review/ | Done but needs human verification before closing. | Agent completes, human reviews |
| done/ | Completed and verified. Symlinked to archive/tasks/. | Human approves final result |
Task Board
Task Board.md is a Kanban board powered by the Obsidian Kanban plugin. It gives you a visual overview of every task across all five stages.
The board uses literal items, not just links. This means the task title text lives directly on the board, not as a wikilink reference.
Critical rule: you must update both the task file AND Task Board.md every time a task moves. If you only update one, the board drifts out of sync with the folders. This is the single most common source of vault inconsistency.
Required Frontmatter
Every task file needs these properties. The title must start with an action verb.
| Field | Description |
|---|---|
parent_project / parent_idea | Which project or idea this task belongs to. Every task must trace back to something. |
assigned_to | Which agent owns execution. One agent per task. |
due | Target completion date. Optional but recommended for prioritization. |
status | Current stage: backlog, ready, in-progress, review, done. |
approved | Boolean. Only true after human explicitly approves via /tasks. |
source | Where this task originated. Daily note, capture, agent proposal, or manual. |
How Tasks Move
Every task follows this exact flow. No shortcuts.
- Agent proposes a task and places it in
backlog/ - Human reviews and approves via
/tasks. Task moves toready-to-start/ - Agent picks up and executes via
/get-shit-done. Task moves toin-progress/ - Agent completes work and moves task to
waiting-for-review/ - Human verifies the result. Task moves to
done/and gets archived
The Self-Improvement Loop
Every completed task is a learning opportunity. The system does not just finish work and move on. It extracts value from the process itself.
- Feedback from completed tasks gets saved for
/skill-evolution - Patterns that emerge across tasks trigger memory updates
- Repeated rejections get logged so agents stop proposing what you do not want
- Skills improve over time based on real execution data, not guesses