task-management
Skill0 starsChanged 2 days agoMITView on GitHub
Manage tasks, discover work, and track implementation progress using Dirban (directory-as-state Kanban). Trigger whenever creating a new task, inspecting current tasks, claiming a task to work on, checking off acceptance criteria, or moving completed tasks.
17 other projects use a version of this.
Adopted by
Most recently taken up by
- cypher0n3/dotagentstheir own version, first seen Nov 16, 2026
- okazuki58/skillstheir own version, first seen Nov 15, 2026
- mondaycom/skillstheir own version, first seen Nov 10, 2026
- ishenli/investment-agenttheir own version, first seen Nov 8, 2026
- flonat/flonat-researchtheir own version, first seen Nov 3, 2026
- mondaycom/monday-claude-cowork-plugintheir own version, first seen Oct 28, 2026
Other versions17 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 17
- anthropics/knowledge-work-plugins★ 36ksame name
- MeisnerDan/mission-control★ 955same name
- flonat/flonat-research★ 150same name
- joelhooks/joelclaw★ 65same name
- ishenli/investment-agent★ 10same name
- mgonzalezbaile/personal-assistant★ 8same name
- mondaycom/skills★ 6same name
- jwilger/agent-skills★ 4same name
- cypher0n3/dotagents★ 3same name
- mondaycom/monday-claude-cowork-plugin★ 2same name
7 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository3 other files it gives its agents.
- AGENTS.mdAGENTS.md
- code-reviewSkill
- copywritingSkill
The file
We split this skill into the rules it gives an agent
11 rules. 0 are common, 10 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 15 edited versions we read keep these.
10
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 34
One Task per File: Every task is an isolated Markdown file.
- Distinctive: line 52
Check available priorities and workspace default anytime via CLI:
- Distinctive: line 62
If the tasks directory does not exist yet:
- Distinctive: line 71
Before starting work, check the board or inspect ready tasks:
- Distinctive: line 108
When designing a feature, breaking down work, or filing a bug:
- Distinctive: line 154
When all acceptance criteria are checked and verification passes:
- Distinctive: line 178
When an active task encounters blockers (e.g.
- Very specific: line 185
Invariant: Never use file paths in relationships.depends_on or relationships.blocks (e.g.
- Distinctive: line 187
Add an entry with timestamp and context to the task Markdown file:
- Distinctive: line 193
When reviewing, scheduling, and resuming work:
- Distinctive: line 235
When working with isolated Git worktrees across parallel or blocked tasks:
“Common” is measured: kept by at least 6 in 10 of the 15 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Task Management with Dirban
This repository uses Dirban (dirban), a zero-database, filesystem-driven Kanban engine.
In Dirban, the physical directory IS the task state.
1. Core Invariants & Lifecycle State Machine
- Directories are States & Tiers:
docs/tasks/00-backlog/— Reserved intake and capture pool (GTD capture / idea staging). The default destination for new, unscheduled, or blocked tasks waiting for planning.- Active Kanban Workflow Columns:
docs/tasks/01-todo/— Prioritized and refined tasks ready for execution.docs/tasks/02-doing/— The task you are currently implementing.docs/tasks/03-done/— Completed work with passing tests & criteria met.
docs/tasks/04-archive/— Reserved terminal tier for historical partitioned storage (04-archive/YYYY/).
- Lifecycle State Machine:
[New Task] ──(dirban new)──> 00-backlog/ ──(dirban ready)──> 01-todo/ ──(dirban start)──> 02-doing/ ──(dirban done)──> 03-done/ ──(dirban archive)──> 04-archive/YYYY/ ▲ │ ▲ └───────────────────(dirban block)───────────────────────┘ │ │ │ └────────────(dirban unblock)──► (dirban resume) ────────────┘ - Use Lifecycle Commands, Not Raw Moves: Never modify
status:directly in frontmatter or use rawmv/dirban movefor standard lifecycle transitions. Always use the dedicated lifecycle commands (ready,start,block,unblock,resume,done,archive). They enforce sequence guards, verify clean working trees, commit task state changes on the target branch, and manage Git branches/worktrees automatically (dirban moveis reserved for manual/administrative overrides only). - One Task per File: Every task is an isolated Markdown file. Always inspect only the task you are actively working on to keep token context minimal.
- Acceptance Criteria are Checkboxes: Track progress with standard Markdown
- [ ]and- [x]items. - Strict Transition Guards:
dirban ready <id>: Only promotes unblocked tasks from00-backlog/into01-todo/(unless--force).dirban start <id>: Requires the task to be in01-todo/(rejects00-backlog/tasks with a hint to rundirban ready <id>first) and requires a clean Git working tree. Commitschore(task): start <id>on the target branch before provisioning the task branch or worktree.dirban done [id]: Requires the task to be in02-doing/. Commits completion, squash-merges the task branch intomain(unless--no-merge), and cleans up the task worktree.dirban resume <id>: Resumes a blocked task directly from00-backlog/back into02-doing/, restoring its task branch or worktree.
2. Priority System
Dirban orders task priorities from highest to lowest urgency:
p0(Critical Blocker / Emergency): Highest urgency. Reserved for critical blockers or emergencies where other tasks must stop immediately to resolve this first. Not used for normal roadmap tasks.p1(High / Prerequisite First): Important foundational tasks or prerequisites that need to be completed before downstream tasks can proceed.p2(Normal / Default): The standard workspace default priority for regular feature tasks and roadmap work.p3(Low / Backlog / Later): Nice-to-have improvements, future phase items, or low-urgency follow-ups.
Check available priorities and workspace default anytime via CLI:
dirban priorities3. Standard Agent Workflows
A. Initializing a Workspace
If the tasks directory does not exist yet:
dirban initB. Finding & Picking Up Work
Before starting work, check the board or inspect ready tasks:
# 1. View current active board (static table)
dirban board --static
# 2. Recommends the next unblocked, highest-priority task ready to work on
dirban next
# 3. View a specific task's details & criteria
dirban view 26-001
# 4. If the task is still in 00-backlog/, promote it to 01-todo/ first
dirban ready 26-001
# 5. Start task execution (requires task in 01-todo/ and clean working tree;
# commits `chore(task): start <id>` before provisioning branch/worktree)
dirban start 26-001
# 6. Check active focus / current task anytime
dirban current
# Stream active task Markdown to stdout for agent prompting
dirban current --rawWorkspace Strategy Flags (dirban start <id>)
--checkout(default): Creates/checks outtask/<id>-<slug>branch in-place.--worktree: Creates an isolated Git worktree in../.<repo>.worktrees/<id>-<slug>.--current/--no-branch: Stays on the current branch without creating a task branch.--no-git: Pure filesystem move without Git operations.
(Note: dirban start requires the task to already be in 01-todo/ and requires a clean Git working tree. Tasks in 00-backlog/ must be promoted first via dirban ready <id>, or resumed via dirban resume <id> if previously blocked.)
C. Creating a New Task
When designing a feature, breaking down work, or filing a bug:
# Creates a new task in 00-backlog with auto-calculated ID and default priority
dirban new "Implement JWT token refresh"New tasks automatically default to the 00-backlog column and use the configured workspace default priority.
Optional Parameters
Override or customize task properties when needed:
--column=<col>: Target column (defaults to00-backlog).--priority=<p>: Priority level (defaults to workspace default; check options withdirban priorities).--tags=<t1,t2>: Comma-separated list of tags.--assignee=<user>: Assignee name.
Example with optional parameters:
dirban new "Fix critical token expiry bug" --column=01-todo --priority=p0 --tags=auth,securityThis creates a new .md file with frontmatter and an Acceptance Criteria section.
You can then open the file to add detailed criteria:
## Acceptance Criteria
- [ ] Add refresh token endpoint
- [ ] Implement Redis TTL expiration
- [ ] Unit tests for expired tokensD. Updating Progress & Criteria
As you complete individual criteria during coding:
# Toggle the 1st checkbox item
dirban check 26-001 1
# Or edit the markdown file directly to mark:
# - [x] Add refresh token endpointE. Completing & Archiving a Task
When all acceptance criteria are checked and verification passes:
# 1. Complete active task (auto-detects from current branch/worktree or 02-doing/;
# requires task in 02-doing/, commits completion, squash-merges into target branch, and removes worktree)
dirban done
# Complete a specific task ID
dirban done 26-001
# 2. (Optional) Archive completed tasks from 03-done/ into 04-archive/YYYY/
dirban archive 26-001
dirban archive allCompletion Options (dirban done [id])
--merge(default): Commits completion, squash-merges the task branch into the target branch, and cleans up any task worktree.--no-merge: Completes the task in03-done/on the task branch without merging intomain.--no-git: Pure directory move without Git operations.
F. Handling Blockers, Planning, Unblocking & Resuming
When an active task encounters blockers (e.g. waiting on dependency, upstream PR, or external input):
- Demote & Record Blockers:
dirban block <id> "<blocker reason or prerequisite task ID>"- Automatically normalizes task arguments to canonical task IDs (e.g.
26-001), adds entries torelationships.depends_on, and moves the task from02-doing/back to00-backlog/to free the active slot. - In Git/worktree mode, syncs the block commit back to the target branch and retains any existing worktree so work-in-progress is preserved until you resume.
- Invariant: Never use file paths in
relationships.depends_onorrelationships.blocks(e.g.docs/tasks/00-backlog/26-001.md). Always use bare canonical IDs (26-001) because physical file paths change continuously as tasks move between columns.
- Automatically normalizes task arguments to canonical task IDs (e.g.
- Record Rationale in
## Execution Journal: Add an entry with timestamp and context to the task Markdown file:## Execution Journal - 2026-11-07T21:00:00Z: [BLOCKED] Blocked by 26-001 (database migration needed).
When reviewing, scheduling, and resuming work:
- Inspect Backlog Plan:
# Formatted overview of Ready vs Blocked tasks dirban plan # Scriptable flags for agents dirban plan --unblocked dirban plan --blocked - Promote / Ready Unstarted Tasks into Active Queue:
- Promote unblocked task(s) from
00-backlog/into01-todo/:dirban ready 26-001 dirban ready 001 002 dirban ready all # Promotes all unblocked backlog tasks dirban ready 001 --to=01-todo - Prerequisite tasks in
relationships.depends_onresolve automatically once they reach03-done/or04-archive/. - Clear external blocker strings via:
dirban unblock <id> "<blocker string>" - Record unblocking in the task's
## Execution Journal:## Execution Journal - 2026-11-08T09:00:00Z: [UNBLOCKED] 26-001 merged; resumed work.
- Promote unblocked task(s) from
- Resume a Previously Blocked Task (
dirban resume):- Unlike
dirban ready(which promotes new/unstarted00-backlog/tasks into01-todo/),dirban resume(alias:continue) returns a previously blocked task directly from00-backlog/into02-doing/and reactivates its task branch or worktree:# Once prerequisites are done or external blockers are cleared via `dirban unblock`: dirban resume 26-001 # Optional flags: dirban resume 26-001 --sync # Rebases/merges latest main branch into the task branch/worktree dirban resume 26-001 --force # Resumes even if unresolved blockers remain
- Unlike
G. Git Worktree Management & Navigation
When working with isolated Git worktrees across parallel or blocked tasks:
# Audit active, blocked, completed, and orphaned task worktrees
dirban worktree
dirban worktree list
# Provision a worktree for a task
dirban worktree add 26-001
# Resolve the absolute directory path of a task worktree or main repo
dirban path 26-001
dirban path main
cd "$(dirban path 26-001)"
# Prune completed (03-done / 04-archive) or orphaned task worktrees
dirban prune
dirban prune --force4. CLI Command Cheat Sheet
| Intent | Command |
| Initialize Board | dirban init |
| Inspect Board | dirban board --static |
| Next Ready Task | dirban next |
| Backlog Planning | dirban plan [--unblocked|--blocked|-i] |
| Ready / Promote Task | dirban ready <id...> [--to=<col>] or dirban ready all |
| Block Task | dirban block <id> <reasons...> |
| Unblock Task | dirban unblock <id> [reason] |
| Resume Blocked Task | dirban resume <id> [--sync] [--force] (or continue) |
| Current / Focus Task | dirban current [--raw] or dirban focus |
| Start Work on Task | dirban start <id> [--checkout|--worktree|--current|--no-git] |
| Finish Task | dirban done [id] [--merge|--no-merge|--no-git] or dirban finish |
| Manage Worktrees | dirban worktree [list|add <id>|prune] |
| Prune Worktrees | dirban prune [--force] |
| Resolve Worktree Path | dirban path [id|main] |
| Check Priorities | dirban priorities |
| Get Next ID | dirban next-id |
| Create Task | dirban new "<title>" [options] |
| View Task | dirban view <id> |
| Move Column (Admin Override) | dirban move <id> <target-column> (manual/administrative override only) |
| Toggle Checkbox | dirban check <id> <index> |
| Update Metadata | dirban set <id> [--priority=...] [--assignee=...] [--tags=...] |
| Archive Tasks | dirban archive <id> or dirban archive all |
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

