Goals, architecture, decisions, risks, interfaces, schedule and the work itself โ kept as plain Markdown and JSON next to the code, reviewed in pull requests, and rendered by small web tools that read straight from this repo.
Goals, risks, rationale and the schedule change together as a project evolves, so they live together, right beside the code. Keeping them current takes minutes, which makes it cheap to start small, scope tightly and see when scope drifts.
Everyone working on the project, people and AI agents alike, reads the same goals, plan, risks and decision log: plain text in the repo, searchable with grep, with the history of how each one got there.
The project data is nearly all Markdown. The tools here are optional viewers: use them, use your own, or add and drop areas as the project needs. The data stays yours and outlives any tool.
Locally, in each tool from the dashboard, or straight in the Markdown: by you or your agent.
Changes to a risk or a decision go through the same pull request, review and history as the code they affect.
The tools are published separately from your data: each opens a file in your repo from its ?src= link.
In your repo, list the tools and add the ones you want. That gives you a docs/ directory with a Markdown file per tool, and a Makefile with a target per tool (e.g. make adr) unless you pass --no-makefile.
There is no software to install: every tool is web-based and improved independently.
You (or an AI agent) can edit the Markdown directly; people usually prefer to view and edit it through the dashboard. Every tool also generates cards, links and badges to include in your GitHub Pages or reports.
# 1. view the tools {{item.name}} @pritzlaff/project list # 2. add the ones you want (--no-makefile: leave the Makefile alone) {{item.name}} @pritzlaff/project add adr risks # view and edit them in the dashboard {{item.name}} @pritzlaff/project dashboard # generate cards, badges and the dashboard into _site/ {{item.name}} @pritzlaff/project dashboard-build