PRODUCT
The planning agent, end to end.
Plansmith is a planning agent for the people who decide what gets built. It reads your team's code and business context, interviews you about the requirement, and produces scored Specs in build order that push to Linear, Jira, Asana, or Radial in one click.
Three things make a plan good. Context. Clarity. Collaboration.
Context
Context is your competitive advantage.
Two kinds. Three levels.
A plan is only as good as what it knows. Plansmith plans with both kinds of context: the code your product runs on and the knowledge your company runs on.
Connect it once at company, project, or plan level, and every plan after gets smarter. That's an advantage no generic AI can copy.
- Code context: the agent reads your repos on GitHub, GitLab, or Bitbucket. Read access only. It never changes a line.
- Business context: documents, links, help centers, and anything that speaks MCP: Notion, Confluence, Google Drive, your wiki.
Company
- Brand-guide.pdfUploaded documentDocument
- Product glossaryPasted textPasted
Project
- acme/webappGitHub · Read onlyRepo
- Pricing-FAQ.pdfUploaded documentDocument
- help.acme.com/billingWebsiteWebsite
Plan
- Discovery notesPasted textPasted
Clarity
See it clicked before it's coded.
Some things you have to click, not describe. Ask, and the agent builds a clickable prototype: screens you can walk through, buttons that respond. It's a sketch to react to, not the product; your dev team builds from the Specs.
Point at any part of it and say what should change. Click the exact button or card you mean, type one line, and the agent gets that element with your instruction. No more describing which one you meant.
One public link shows the prototype and nothing else. Anyone can open it and pin a comment to the exact spot they mean. No account, no login. Send a prototype, not a meeting.
Readiness
Rough. Shaping. Ready.
The agent scores every Spec: Rough needs thinking, Shaping needs answers, Ready is safe to hand off. Say "this isn't ready" and it tells you what's missing.
Effort reads Low, Med, or High: your dev team sees the size before they commit. "Needs first" links set the build order, so the first ticket picked up is one a developer can actually start.
Together
Plan it together.
Invite your team into any Plan. Questions get settled where the work lives, not in a thread nobody can find later. The plan gets good in the open, not in a doc only you can see.
- Comment on any document. Select a passage and settle it in place.
- Suggest an edit instead of asking for one. Whoever maintains the document accepts it or turns it down.
- Mention a teammate and they hear about it, in their Inbox or their email.
- When a Spec changes, everyone sees the new version. Nobody works from a stale copy.
- Stakeholders pin feedback on the prototype through a public link.
- Only planners need seats. Developers and prototype reviewers never need one.
- Maya@Sam, can we make the monthly-plan limit explicit?
- SamYes. I accepted your edit to AC3.
New agent. Same workflow.
Plansmith reads context from GitHub, GitLab, and Bitbucket repositories, from documents and transcripts you upload, and from any source that speaks MCP. When the Plan is Ready, one click pushes it to Jira, Linear, or Radial as nested issues carrying dependencies, estimates, and workflow states.
Context in
what the agent readsNotion, Confluence, Google Drive, your internal wiki: any source that speaks MCP.
Handed off to
where your dev team worksOne click. Nested issues, dependencies, estimates, and workflow states.
Read access only on your code. Nothing reaches your issue tracker until you push.
Explore the connectorsWhere the plan gets good.
Start with your business requirements. Review the Specs and prototype, resolve open questions, and hand off a plan your dev team can build.