T

istosandClaude Fable 5 9d2dbb017d Enrich the task template for new cards (task 07)

Merge the highest-value slots from a fuller development-task template
into bench's lean one: an optional Depends on header line, an Affected
areas line in Context, Out of scope bullets in What to build, edge-case
and Given/When/Then guidance in Acceptance, and a Risks slot in Notes.
Each slot says who consumes it and is marked deletable — empty
boilerplate is worse than absence.

The load-bearing contracts are unchanged: exact Status values, the Open
questions heading the NOT READY gate keys off, Acceptance as the review
target, and the template staying off the board. Organisation process
(staging, sign-offs, approvals, contacts) is deliberately absent; a new
contract test pins both the gained slots and what must not grow back.
CLAUDE.md's Task file format section documents the Depends on line.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

2026-07-29 22:37:36 +02:00

manager

Merge branch 'task/02-start-cleanly-when-bench-is-the-project'

2026-07-29 21:54:06 +02:00

plans

Bench 1: the task board extracted as its own distribution

2026-07-29 17:57:07 +02:00

reference

Bench 1: the task board extracted as its own distribution

2026-07-29 17:57:07 +02:00

tasks

Enrich the task template for new cards (task 07)

2026-07-29 22:37:36 +02:00

tests

Enrich the task template for new cards (task 07)

2026-07-29 22:37:36 +02:00

.gitignore

Bench 1: the task board extracted as its own distribution

2026-07-29 17:57:07 +02:00

CLAUDE.md

Enrich the task template for new cards (task 07)

2026-07-29 22:37:36 +02:00

install.py

Start cleanly when bench is the project itself

2026-07-29 19:55:57 +02:00

README.md

Bench 1: the task board extracted as its own distribution

2026-07-29 17:57:07 +02:00

start.sh

Bench 1: the task board extracted as its own distribution

2026-07-29 17:57:07 +02:00

stop.sh

Bench 1: the task board extracted as its own distribution

2026-07-29 17:57:07 +02:00

update.sh

Bench 1: the task board extracted as its own distribution

2026-07-29 17:57:07 +02:00

README.md

Bench

A live kanban for coding-agent work: task files in stage directories are the only source of truth; a stdlib-only board narrates everything that happens to them — agents working in git worktrees, PRs opening on review, CI and Copilot state on the cards, drives of the app from a task's own branch, and an archive that is never a delete.

Install into a repo

git clone <this repo> .task-manager && rm -rf .task-manager/.git
./.task-manager/start.sh        # wires the project (idempotent) and serves

Commit .task-manager/ into the host repo — core is vendored on purpose, so clones work offline and updates show up in the host's own diffs.

Update

# in manager/local/.env:  BENCH_SOURCE=<this repo's git url>
./.task-manager/update.sh              # latest
BENCH_REF=v1 ./.task-manager/update.sh # a specific release tag

Updates replace manager/core/ and the top-level scripts wholesale and touch nothing else — tasks, plans, reference, and everything under manager/local/ (your driver, commands, prompt overrides, settings, state) survive every update. Then python3 .task-manager/install.py and restart the board.

The three-layer law

Core knows about tasks, worktrees, PRs and events. It knows nothing about any particular app (drivers do: local/driver/start), agent vendor (adapters do: core/adapters/), or project (local/ does). Full docs in CLAUDE.md; the adapter contract in manager/core/adapters/README.md.