v0.1.0

daiku v0.1.0 is the first release. It merges zumen (planning), tomo (building) and their shared core, kiso, into one tool with one workspace. This release completes planning change 5-merge-zumen-tomo-and-kiso-into-daiku, stories S-0039 to S-0043.

go install github.com/btdstudio/daiku/cmd/daiku@v0.1.0

Two loops, one workspace

• Plan loop (from zumen): intake → [research] → [explore] → [synthesis] → spec → architecture → breakdown → publish. Ends in tickets under plan/specs/<change>/tickets/.
• Build loop (from tomo): ticket → requirements → design → tasks → implement → test → review → security → ship. Takes one ticket into one repo and ends in a pull request.
• Rooms appear when first used. daiku init writes only the root; change new creates plan/, and build new creates build/. A workspace can be plan-only, build-only or both.

Highlights

• Tickets from anywhere: build a planned ticket in place, a native N- ticket from the inbox, or a PM item pulled as X-<pm-id>. A pulled ticket's references to tickets planned elsewhere are warnings, not errors.
• One build per repo in implement through ship, worked out from STATE.json; --force overrides and is logged.
• Status board: bare daiku status shows the active change, every open plan, and every open build by repo with its lock holder. daiku status <plan-change> lists a plan's tickets and their build phase.
• Plan overviews gain a generated Builds section, kept current by each build's transitions.
• daiku check also lints each room's docs for the other loop's terms.
• daiku commit and daiku pr run in the active build's repo, and the PR links its ticket.

Compatibility

zumen and tomo workspaces aren't converted; daiku refuses them with a clear message. Go 1.22 or later, standard library only.

What's Changed

• [S-0039] daiku repo and core with loops, X- ids and room scaffolding by @btdstudio in #1
• [S-0040] Plan loop, root-only init and the plan room by @btdstudio in #2
• [S-0041] Build loop, the build room and tickets in the inbox by @btdstudio in #3
• [S-0042] Status board, initiative view and overview build section by @btdstudio in #4
• [S-0043] Checks and the first daiku release by @btdstudio in #5

New Contributors

• @btdstudio made their first contribution in #1

Full Changelog: https://github.com/btdstudio/daiku/commits/v0.1.0