Turn it into action

Where it goes next.

You've worked out what should change. Push it somewhere it can happen — a ticket, a doc, or a real pull request — without ever leaving Statecraft.

Where it lands

Send it where work happens.

Open the change as an issue in the tracker your team already lives in, or export a plain doc you can drop in anywhere else.

  • A Notion, Linear, or GitHub issue
  • Or a Markdown doc for Confluence, Jira, email
  • A clear, shareable description of the change
Or straight to code

Or open a real PR.

When it's ready to build, Statecraft can write the change and open a pull request against your repo — real code a developer reviews, not a description of it.

  • Statecraft writes the change as code
  • Verified against your own typecheck and lint
  • Opens a pull request against your repo
  • Review and merge like any other

Not a dead-end mockup. Close the loop, your way.