Decide what to build next,and tell your agents why,so they build the right thing.
We turn your strategy and goals into an ordered backlog, keeping everything Inwoven. Your AI coding agents read all three, so every change serves a goal you set.
Code is no longer the bottleneck.Deciding what's worth building is, and it always was.
WhyWhatHow
Yes, you will no longer be chiseling that code by hand, but you will be making amazing things. You will be steering intelligence that was only available in science fiction up until a few moments ago.
Paste this line into Claude Code, Codex or Cursor. Your agent writes your backlog files, adds an AGENTS.md block and installs the Inwoven skill in your repo.
Set up Inwoven in this repo: follow https://backlog.works/setup.md
With the skill, your agent reads an item's goal before it starts, keeps a lesson only when you approve it, and never adds work or reorders the backlog on its own.
We plan Inwoven in Inwoven every day, so a rough edge hits us before it hits you, and we fix the product. You can share your backlog with your team or with everyone, as we do here. Show your users what you build and why with one embed snippet, no separate roadmap tool.
A one-minute game: what serves the goal?
Drag the four items that move this goal to the top, then press Check the order. You'll see which you got right, and why.
Every item traces back to a goal
Inwoven ties each item to the goal it serves. This is the map behind the game above; its goal card shows the measure and the horizon.
Measurable goals in horizons. A measure says when each goal is met. Now, Next, Later is a roadmap by Janna Bastow.
Impact mapping. Who has to act differently, how, and the items that follow, by Gojko Adzic.
Wardley mapping. Where your product stands and which items move it, by Simon Wardley.
See who last touched each item
Each pill shows the person who changed an item last and how long ago. Its details name the agent, from the Co-Authored-By trailer on your commits.
Order your backlog from your phone
Give your agents a clear order and they can build while you cook, play or rest. When you have a minute, open Inwoven on your phone. It is a web page, so there is nothing to install.
Drag an item by its grip to reorder.
Swipe a card to mark it Done, send it to the top or delete it.
Tap a title or description to edit it.
Your backlog is a file in your repo
Inwoven keeps it as a markdown file in your GitHub repo. Without GitHub, we host it.
Every move from the board is one commit in your repo.
History lists each version, and you can download any of them.
Inwoven also keeps a backup copy, and every version on Pro. You can turn it off.
A read-only link. Anyone with it can read your backlog, without signing in.
An embed. One snippet puts the live backlog on your site. Choose how many items show, or let visitors play the game.
Email invites. Your team edits the backlog with you. A team holds up to 20 people.
Why not just a markdown file?
Each item keeps the goal behind it. Agents read why, and the lessons you approved, before they build.
Reorder by dragging, from a phone. Each move is one commit in your repo.
The file stays yours, in your repo. Download any version.
Who decides here
Pasha and Roma are the names in the Driver column of our backlog. We use Inwoven to decide what Inwoven does next.
Pasha Riaby
Co-founder
Husband, father and grandfather. Fintech hippie and payments bro. As product director, turned bare payments technology into a national real-time payments product people use every day: instant transfers to friends and frictionless grocery checkouts. It grew from beta to 200 banks and 10 million monthly users in 18 months. Then led card acquiring at Wise, the domain behind 40% of all money coming into Wise.
Started as a developer on an eXtreme Programming team, then spent more than five years owning a product end to end. Co-founded Starling & Cuttlefish, an organisational design consultancy.
I specialize in restructuring organizations to maximize their commercial success, bridging the strategy and execution gap.