What is Plansmith
Plansmith turns a business requirement into a tree of dev-ready Specs, then pushes them to your issue tracker.
You describe what the business needs in plain English. A planning agent researches what it already knows about your work, asks you the questions it still needs answered, and writes the result as a plan: a tree of Specs, each one specific enough for a developer to build from.
Then you push the plan to Linear, Jira or Radial, and your team works where they already work.
What it is for
The gap Plansmith fills is between "we should do this" and "here is a ticket someone can pick up". That gap is usually crossed by one person writing tickets late at night, and it is where most of the ambiguity in a project survives: the ticket says what to build but not what done means, and nobody notices until review.
A Spec written here carries its acceptance criteria with it. That is the point.
What it is not
It is not an issue tracker. Yours stays the plan of record, and Plansmith is where the plan gets good before it lands there.
It is not a project management tool. There are no burndown charts, no sprint boards and no status reports. Plansmith stops at the Spec; your team executes downstream.
It does not write your code. It can read your codebase to ground what it writes, but the output is a plan, not a pull request.