Ready to write with your agents?
Free. No setup. Sign in with Google.
Start freeBlog
Writing on spec-driven development, coding agents, and collaborative docs from the team building Squire Docs.
-
July 19, 2026
Let your coding agent draw the architecture
Point a coding agent at a system (even one it has to research, like Claude Code's own internals) and it draws the architecture as live diagrams right in the document.
-
July 12, 2026
Squire Docs vs. Google Docs vs. Notion vs. Proof
A direct comparison of four ways people and AI edit the same document, and the one question that separates them: does the document live in your repository?
-
July 5, 2026
Sharing specs with product managers for review
When specs live in the repo, getting a PM's review means copying the spec out and reconciling changes back by hand. Squire Docs removes the copy.
-
June 28, 2026
Using a Squire Docs document as your Kiro spec
A short tutorial for keeping your Kiro spec as a living Squire Docs document, so your PM can edit it and your agent can read it, with two-way markdown sync to the repo.
-
June 21, 2026
Spec-driven development with Claude, Squire Docs, and Spec Kit
How we combine Claude, Squire Docs, and Spec Kit into a design-to-merged pipeline where the written spec is the source of truth and agents implement against it.
-
June 14, 2026
Why I built Squire Docs
Specs and design docs are where software decisions get made, but the tools split humans from their coding agents. Squire Docs is one place where both write together.