Shipped First logged 25 October 2026

Project Roadmap

A private Mac app that reads every roadmap across my GitHub repositories, lets me capture and order the next work, and copies a ready-made brief for the next agent session.

extra databases: 0
between automatic refreshes: 90 s

What it is

Project Roadmap is where I choose the work. It reads the roadmap file in every one of my GitHub repositories and lays it out as a board: ideas and later, build next, in progress. There's a release pipeline view with open pull requests, merge conflicts and check results, and a button that copies a brief for an agent to start the next session.

Capture is the main job. Pick a project, type the improvement, save, and it's committed to that project's roadmap and read back to check it landed.

What I had to steer

The rule was that there's no second task list. Roadmaps live in their own repos as plain Markdown, and the app is just a window onto them. It never edits my local project folders, it never invents work from chat history, and an open pull request isn't treated as proof that something has shipped.

What I wired together

A small Node server bound to localhost, wrapped in a native Swift window and installed as a login service. The GitHub CLI handles reads and commits, with file checks so two sessions can't overwrite each other. It parses each roadmap's sections, checkboxes and hidden IDs, and reads local checkouts only to spot unpushed differences.

Where I pushed it

Building the tool changed how every other project is run. It rolled out the same record rules, roadmap, status and session notes, across all my repos, which is why this site's own records look the way they do.

The build log

Entry 01 25 October 2026

One place to choose the work

At some point I had more agent sessions than I could hold in my head. Plans lived in roadmap files, status notes, open pull requests and chat transcripts, and I couldn’t answer a simple question: what should I build next?

Project Roadmap answers it. It reads the roadmap from every repository I own and puts the items on one board. I can move an item from ideas to build next, write the outcome I want and copy a session brief that names the repo, the file, the task and the handoff the agent has to leave.

Saving is the careful part. A new item becomes a commit to that project’s roadmap, then the app reads the file back to check it. If another session changed the file first, the save is refused and my draft is kept. It runs locally, only answers on my own machine and needs no subscription.

The bigger result was the record standard that came with it. Every project now has the same brief, roadmap, status and session notes, so any agent can pick any project up cold.