Dev Flow

How it works

The mechanics of this kit, plainly — what runs and when, where the data lands, and what you look at.

• Dev digest runs weekday mornings · 8am and keeps the Dev Flow dashboard fresh. Weekday mornings — whose move it is, and what has gone stale.
• What is captured lands in the PR log record, which lives at Data/PR Log in your vault — yours to open, search, and edit like any other file.
• What is captured lands in the Dev log record, which lives at Data/Dev Log in your vault — yours to open, search, and edit like any other file.
• The Dev Flow dashboard reads from the record and shows, at a glance: open prs · reviews you owe · whose move · by repo · merged this week · every open pr · the dev log.

The wiring, in one breath: Dev digest writes to PR log · Incident capture writes to Dev log · PR log shown by Dev Flow · Dev log shown by Dev Flow · Dev Flow kept fresh by Dev digest · Incident capture given to Relay · Dev lookback given to Relay.

Make it yours

Nothing here is fixed. The pieces are ordinary agents, routines, records and dashboards, so anything you know about shaping those applies. Retire whatever earns nothing.

Things people usually change first

Say any of these in chat, or edit them on the kit’s page in the app.

• How many days count as stale, separately for reviews you owe and your own waiting work.
• Which repositories it watches.
• When the digest arrives, or turning the cards off and just keeping the board.
• What is worth putting on the dev log — some people log only incidents, some log every decision.

Your first run

Installing starts a short setup conversation — not a form. Answer roughly, correct later.

1. Its first weekday morning reads your repositories and fills the board with what is open and whose move it is — no setup beyond connecting GitHub.
2. It tells you only what has genuinely gone stale. A queue in good shape produces no card at all.
3. Mention an incident or a decision in passing and it lands on the dev log, in the words you used at the time.
4. It cannot see build status — there is no CI tool on the connector — so it never reports whether a build passed or main is green.

Watch the first pass, then tell it what you would have done differently — that correction teaches it more than any setup could.

The essentials

Learning, preferences and run costs work the same in every kit — so they are covered once, in the Kits guide.

Living with a Kit — the Kits guide →

← All kits