Summary
Project documentation as a reviewed sequence, not one long generation.
The value is the order it enforces: the roadmap is written knowing what the README committed to, and the architecture doc is written knowing both. You approve or rewrite at each handoff instead of finding the drift three documents later.
What it is
A documentation run for a project that has stories but no docs. It writes README, then ROADMAP, then SYSTEM-ARCHITECTURE, stopping after each one so you can approve it or send it back with edits.
What you get
- A README drafted from the user stories you hand in
- A roadmap of milestones, written against the README you already approved
- An architecture document, written once the README and roadmap are settled
- The full three-document run from a single call, or an entry at whichever phase you need
- The templates behind each document, readable as MCP resources
Requirements
Node.js with npx on your PATH. Nothing to sign up for — the documented config launches it as a local process.