If you ship ToB or agency work, you already know the Friday ritual: dig through chats and sheets for "what moved," "who owns it," and "what slipped." The model in your IDE sees the repo; your board lives somewhere else. Alignment dies in the gap.
I wanted the opposite: delivery context as a first-class citizen of the codebase. Humans and agents share one source of truth. Views (board, audit, weekly) are projections — not another product to keep in sync.
That's what dsh-delivery-board is: a skill-backed DeepSeek Harness (dsh) plugin.
wipLimit. Board and move responses warn when a stage is over; moves are never blocked./delivery Open the editable board serves a drag-and-drop UI on 127.0.0.1 that saves back to the same state. Offline HTML snapshot for teammates without DSH.
Install (web profile):
dsh plugin --profile web add github:jerryxff26-alt/dsh-delivery-board
Compatible with DSH engines.dsh >=0.2.0-rc.2 <0.3.0 (smoke path: 0.2.1-rc.2). Listed in awesome-dsh-plugin.
Normal path is the /delivery skill: ask for outcomes in plain language; the model reasons, tools persist.
/delivery Initialize a governance delivery board for ACME
/delivery Hand off the API card to Test, assign Morgan
/delivery Open the editable board
/delivery Prepare the client weekly report for the week starting 2026-10-20
Deterministic controls (no model) live under /delivery-admin so they don't intercept skill prompts.
Templates cover a ToB pipeline (Client Requirements → … → Live) and a governance pipeline (Plan → … → Live). Gates are checkable checklists stored in state — they do not hard-block moves.
v0.1.5 deliberately fused only two lightweight ideas:
What we did not build: Timeline views, Gantt, hard DoR gates, Dual Track ceremony. Stay usable in-repo, not another SaaS.
Feedback from people who run real BA → TL → build → test → go-live handoffs is especially welcome.