taskboard

name	taskboard
description	Inspect or update a compact task board with stable task IDs, priorities, owners, and verifier-backed completion.

Run OmA taskboard.

Input: $ARGUMENTS

Protocol:

1. Parse requested action:
   • status
   • sync
   • next
   • rebalance
   • close <task-id>
   • verify <task-id>
   • set-priority <task-id> <p0|p1|p2|p3>
2. Maintain a compact task ledger for the active workflow:
   • task id (stable, short, deterministic)
   • priority (p0, p1, p2, p3; default p2)
   • summary
   • owner / lane
   • status (todo, ready, in-progress, blocked, done, verified)
   • dependency
   • worktree or path scope when relevant
   • baseline branch/commit anchor when relevant for the active lane
   • lane health note when workspace audit marks dirty, untrusted, or needs-review
   • verification evidence pointer
3. Null-safe priority policy:
   • if a task has no priority, assign p2 instead of leaving it empty
   • preserve explicitly assigned priority during sync unless user asks to change it
4. Deterministic queue policy for next and rebalance:
   • include only dependency-ready tasks
   • prefer lane-safe tasks first (clean + trusted + ready)
   • then sort by priority (p0 -> p1 -> p2 -> p3)
   • break ties by stable task id (ascending)
5. Prefer updating existing task IDs instead of inventing new ones mid-loop.
6. Keep ordering stable and write only high-signal notes; avoid volatile chatter or duplicated diffs.
7. If team-plan or team-prd output exists, align the board to those artifacts.
8. Never mark a task verified without evidence from team-verify; if lane scope, trust status, or evidence is unclear, keep the task blocked or call out the ambiguity explicitly.
9. Before mutating the shared board, read .omg/state/session-lock.json.
   • if the current orchestration session owns the lock, write/update .omg/state/taskboard.md
   • if another session owns the lock, do not overwrite the shared board; write .omg/state/sessions/[session-slug]/taskboard.md instead and flag the merge requirement
10. Delegated/worker/subagent turns must not write the shared board directly.
11. If scope or evidence is unclear, call it out instead of fabricating a board.

Suggested taskboard.md shape:

Taskboard

Task ID	Priority	Status	Owner	Dependency	Worktree	Baseline	Lane Health	Summary	Evidence
T1	p1	ready	oma-executor	-	root	main@abc1234	clean	add config parser	pending verify

Response:

• Keep it concise and operator-facing.
• Include Board Summary, Priority Queue, Ready Tasks, Blocked Tasks, Verification Queue, Baseline Drift Risks, and Next Command.