DEV Community: jerry23t

How I track a small feature from backlog to live inside the repo

jerry23t — Thu, 29 Oct 2026 09:28:05 +0000

How I track a small feature from backlog to live inside the repo

Last Friday I shipped a small API integration. Nothing dramatic — one card, a few stage moves, a short client note. What I wanted was not another SaaS board. I wanted the delivery state to sit next to the code, so a teammate (or an agent) could git pull and see the same truth I was looking at.

That is what dsh-delivery-board is for: an in-repo delivery board. Stages, handoffs, a local kanban + calendar Timeline, and a weekly Markdown report all project from one file — delivery.json by default. It runs as a standalone CLI today; it also plugs into DeepSeek Harness if you use that.

Setup for one customer, one lite pipeline

I keep a scratch directory for the walkthrough. The lite template is enough for a small feature: Backlog → Doing → Review → Live.

npx github:jerryxff26-alt/dsh-delivery-board init ACME lite

That writes delivery.json in the current directory. Commit it when you want the team to share the same board through git.

Create the card where work starts

Positional CLI works (title, stage, optional owner). JSON works too.

npx github:jerryxff26-alt/dsh-delivery-board card "API integration" backlog Ada
# or:
# npx github:jerryxff26-alt/dsh-delivery-board card '{"title":"API integration","stage":"backlog","owner":"Ada"}'

When Ada starts coding:

npx github:jerryxff26-alt/dsh-delivery-board move "API integration" doing

One cross-stage move → one handoff line in the audit log. Same-stage owner tweaks are recorded as decisions, not as fake “Doing → Doing” handoffs.

Why the handoff log only records moves that actually happened

This is the part I care about most for a weekly paste.

If the card jumps from Doing to Live (skipping Review on purpose — hotfix, already reviewed elsewhere), the audit writes one line: Doing → Live. It does not invent intermediate hops. The README puts it plainly: handoff audit logs only actual stage moves; intentional skips are not padded into a fake path.

So when I generate the client weekly report later, the handoff section matches what people remember happening — not a reconstructed waterfall.

Open the local board when I want eyes on the timeline

npx github:jerryxff26-alt/dsh-delivery-board open

That starts a loopback board on 127.0.0.1 (unguessable capability path; treat the URL as private). Drag the card into Review, then Live. Saves go back to the same delivery.json. There is a calendar Timeline view: bars follow created → each real handoff → shipped / archived / today, with due markers and light/dark themes.

Silent walkthrough of the live board (v0.3.0 UI). MP4 if you prefer download.

A quick text board without the browser:

npx github:jerryxff26-alt/dsh-delivery-board board

Friday: the weekly that is not a blank page

npx github:jerryxff26-alt/dsh-delivery-board weekly
# or pin the week start:
# npx github:jerryxff26-alt/dsh-delivery-board weekly 2026-10-20

You get Markdown: pipeline snapshot, shipped this week (terminal stage or archived in the window), handoffs that actually fired, open risks, risks resolved this week, and optional Next bets if you passed notes. I paste that into the client thread and stop rewriting history from Slack.

Need a read-only snapshot for someone without the CLI?

npx github:jerryxff26-alt/dsh-delivery-board html

What this is (and is not)

It is delivery context for one repo: stages, owners, AC/DoD, soft WIP warnings (never hard-block), handoff audit, Timeline. It is intentionally not a rebuild of Jira, Linear, or Notion. If your org lives in those tools, keep them; this keeps the slice that should travel with the code.

Optional DeepSeek Harness path (skill-backed /delivery):

dsh plugin --profile web add github:jerryxff26-alt/dsh-delivery-board

Standalone works without DSH. Until the package is on npm, the GitHub install string above is the reliable path; after publish, npx dsh-delivery-board … is the same shape.

dsh-delivery-board v0.2.0 — a standalone CLI delivery board that lives in your git repo

jerry23t — Wed, 28 Oct 2026 00:36:12 +0000

Why another board — and why it should live in git

If delivery state lives only in Slack threads and a SaaS board nobody opens, humans and coding agents drift. Who owns the card? What does "done" mean? What shipped this week?

dsh-delivery-board keeps stages, owners, handoffs, soft WIP hints, a weekly Markdown client report, and a local kanban + calendar Timeline in one in-repo file (delivery.json by default). Views are projections of that same state — reviewable in PRs, offline-friendly, and intentionally not a Jira/Linear replacement.

This post is about v0.2.0: the board now runs as a standalone CLI. You do not need DeepSeek Harness (dsh) installed. (The optional DSH plugin path still works unchanged.)

Distinct from the earlier Dev.to post that introduced the project mainly as a DSH plugin. Here the headline is: CLI-first, works alone.

30-second standalone quickstart

npx github:jerryxff26-alt/dsh-delivery-board init '{"customer":"ACME","template":"governance"}'
npx github:jerryxff26-alt/dsh-delivery-board card '{"title":"API integration","stage":"analyze","owner":"Ada"}'
npx github:jerryxff26-alt/dsh-delivery-board open    # loopback board + Timeline; Ctrl+C to stop
npx github:jerryxff26-alt/dsh-delivery-board weekly

If/when the package is on the npm registry under dsh-delivery-board, the same commands work as npx dsh-delivery-board …. Until then, the GitHub install string above is the reliable path.

What you get

Stage pipeline + cards — owner, due date, acceptance criteria, Definition of Done
Handoff audit — stage moves record who handed what to whom
Weekly Markdown report — pipeline snapshot, shipped this week, handoffs, open/resolved risks, optional next bets
Soft WIP limits — warn when a stage is over; never hard-block
Local editable board — drag-and-drop on 127.0.0.1, saves back to the same file
Timeline view — calendar-axis bars per card (created → handoffs → shipped/archived), due markers, light/dark
Offline HTML snapshot — single read-only file teammates can open without the CLI

Optional: DeepSeek Harness plugin

Same domain model, skill-backed /delivery workflow for agent-led planning and moves:

dsh plugin --profile web add github:jerryxff26-alt/dsh-delivery-board

Tested with DSH 0.2.1-rc.2 (also compatible with 0.2.0-rc.2). No runtime dependencies.

Compared to alternatives (short)

Need	This project	Typical SaaS kanban	Markdown checklists alone
Lives in the git repo	Yes (`delivery.json`)	Usually remote	Yes, but unstructured
Handoff audit + weekly client report	Built-in	Custom fields / exports	Manual
Local editable UI + Timeline	Loopback board	Full web app	No
Works with AI coding agents	CLI for any shell; optional DSH skill	Often API / MCP	Prompt-only

Codebase-native delivery for DeepSeek Harness: stages, handoffs, and a weekly that writes itself

jerry23t — Mon, 26 Oct 2026 08:08:14 +0000

Why delivery state belongs next to the code

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.

What it actually does

Stage pipeline + cards — owner, due date, acceptance criteria, Definition of Done. Stages can evolve after init.
Handoff audit — moving a card across stages records who handed what to whom, with notes.
Weekly Markdown report — pipeline snapshot, shipped this week (terminal stage or archive), open risks, risks resolved in-window, and optional Next bets (Shape Up–ish framing without betting tables).
Soft WIP limits — optional per-stage wipLimit. Board and move responses warn when a stage is over; moves are never blocked.
Local board — /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.

How you work day to day

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.

Methodology without a PM suite

v0.1.5 deliberately fused only two lightweight ideas:

Kanban soft WIP — visibility when a lane is overloaded, zero ceremony.
Weekly shipped / risk burn-down / Next bets — the report answers what left the building, what risk closed, and what we're betting on next.

What we did not build: Timeline views, Gantt, hard DoR gates, Dual Track ceremony. Stay usable in-repo, not another SaaS.

Boundaries (said up front)

Board is single-machine (127.0.0.1); no realtime multiplayer.
State travels with git pull/push, not a hosted sync service.
Soft warnings over hard blocks — including WIP and gate checklists.

Feedback from people who run real BA → TL → build → test → go-live handoffs is especially welcome.

session-top v0.0.3 — archived sessions, --json, and cache mix (still not a live process monitor)

jerry23t — Mon, 21 Sep 2026 14:39:34 +0000

You know your Codex usage dropped.
Now find out which sessions did it — including ones you already archived.

session-top is a local TUI/CLI that reads Codex rollout JSONL and explains quota/token spend. Think htop for agent sessions, not a live process dashboard (that's abtop's job).

What's new in v0.0.3

Archived session discovery — after native codex archive, files live under archived_sessions/; v0.0.3 finds them
--json on overview / why / sessions for scripts and pipelines
Cache mix — cached vs uncached input when events provide it (absence ≠ zero)
Plan / credits / resets on the overview when Codex surfaces them — never an invented quota formula

Principles (unchanged)

100% local — no API keys, no telemetry
Numbers labeled OFFICIAL / OBSERVED / INFERRED
Complements live monitors; does not replace them

go install github.com/jerryxff26-alt/session-top/cmd/session-top@v0.0.3
session-top
session-top why --json
session-top sessions --json

MIT · Go · feedback welcome from people who live in agent CLIs.

Release: https://github.com/jerryxff26-alt/session-top/releases/tag/v0.0.3

DEV Community: jerry23t

How I track a small feature from backlog to live inside the repo

How I track a small feature from backlog to live inside the repo

Setup for one customer, one lite pipeline

Create the card where work starts

Why the handoff log only records moves that actually happened

Open the local board when I want eyes on the timeline

Friday: the weekly that is not a blank page

What this is (and is not)

Links

dsh-delivery-board v0.2.0 — a standalone CLI delivery board that lives in your git repo

Why another board — and why it should live in git

30-second standalone quickstart

What you get

Optional: DeepSeek Harness plugin

Compared to alternatives (short)

Links

Codebase-native delivery for DeepSeek Harness: stages, handoffs, and a weekly that writes itself

Why delivery state belongs next to the code

What it actually does

How you work day to day

Methodology without a PM suite

Boundaries (said up front)

session-top v0.0.3 — archived sessions, --json, and cache mix (still not a live process monitor)

What's new in v0.0.3

Principles (unchanged)