Plansmith documentation
Turn a business requirement into a tree of dev-ready Specs, then push it to your issue tracker.
Start with the five-minute quickstart, or wire up the CLI, the MCP server and the API.
Quickstart
From a business requirement to a plan in your issue tracker, in about five minutes.
Connect your issue tracker
Linear, Jira and Radial, and what re-pushing does to edits.
API Reference
A versioned JSON API at api.plansmith.co/v1.
Where to go
Plan your first project
What Plansmith is for, the four words it uses, and how a plan comes together.
Install the CLI
Read and push plans from your terminal or from CI.
Add Plansmith to your agent
Connect the MCP server to Claude Code, Cursor or Claude.ai in one config block.
Enterprise
What an Enterprise plan includes, and where Plansmith runs.
How the docs are organized
Start here is what Plansmith is and how to get a plan out of it. Plan the work covers the conversation, sub-plans, prototypes and sharing. Give the agent context is what it reads: documents and your code. Teach it how your team works is how you shape what it writes. Ship the plan is the push. Run your workspace is members, billing and the audit log. Enterprise is where Plansmith runs, including against a Git server inside your own network, and what an Enterprise plan includes.
The Developers tab covers the CLI, the MCP server and the API, and the Changelog records what shipped.
Every page here has a markdown twin: add .md to any docs URL and you get the page as plain
markdown. There is a full-site index too, and an agent index.