start_genspecLABSCO 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.
Setup effort
Build from source — git clone https://github.com/iamhenry/GenSpec-MCP.git
USE CASES
01
Getting a new project documented from a pile of stories
Start the whole run in one call and answer at each checkpoint. README first, then roadmap, then architecture — each phase reads what you approved before it.
02
Writing just the README and deciding about the rest later
Begin at the first phase alone. You get a project overview and setup instructions out of the stories, and the run continues only when you say so.
03
Adding a roadmap to a project that already has a README
Enter at the roadmap phase rather than regenerating everything. Milestones are drafted against the README that already exists.
04
Writing the architecture doc once the plan is agreed
The last phase reads both earlier documents, so the technical write-up describes the project you settled on rather than the one you started from.
4 tools
Listed in project docs. Your client may show a different list.
generate_readmegenerate_roadmapgenerate_architectureBEFORE YOU INSTALL
What to know first
Tools you get
4 tools named in the project's documentation.
Requires
Node.js 18.0.0 or later
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
git clone https://github.com/iamhenry/GenSpec-MCP.git
cd GenSpec-MCP
npm install
npm run buildMCP Clients
Any MCP client
ANY MCP CLIENT · JSON
{
"mcpServers": {
"genspec": {
"command": "node",
"args": [
"<YOUR_GEN_SPEC_MCP_CLONE>/dist/index.js"
]
}
}
}
