Viktor.comAn AI coworker that actually does the work
Planwright
The Control Plane for Agent Labor
16 followers
The Control Plane for Agent Labor
16 followers
Post-kanban, agent-native planning and control. Humans write objectives. Claude Code, Cursor, and Codex decompose, execute, and check in. Every decision signed. Every change audited. Compose your Agentic Engineering stack with PlanWright and we'll take care of the accounting for the auditors.
Interactive
Free Options
Launch Team
This year I opened a venture studio where we went really fast launching new companies and building products. One of the things we learned was we need to get way more organized around how we plan products and give better tools to our coding agents in order for them to be the most effective, and to ensure we retain human control and review.
At the same time I happened to be supporting an initial SOC 2 audit and freaked out about how these new coding agents will never pass, especially as we start to move toward more agent autonomy. So I decided to go down the rabbit hole of investigating what tools exist on the market to allow for agentic engineering to happen and at the same time pass audits.
This product is the result of that research and the new audit standards that came into being at the beginning of 2026 for Agentic Engineering flows where human still need to define objectives and control acceptance of coding efforts. However, we still want coding agents to contribute code at a rapid pace and report progress and breakdown tasks. Moving toward a Dark Factory coding model we are going to need robust planning and control mechanisms.
When we wrote this tool and started dogfooding it in our own projects, what we found out was this is way more capable as an enterprise planning tool to retain complex context through projects and we have actually extended the capabilities of our PMs to be able to synthesize Objectives from chaotic inputs and deliver specs that are machine ready by living inside of claude desktop.
How does the "every decision signed" part actually work in practice, like is there a way to roll back or contest an action an agent took autonomously?
@glerioqv the signing part is for the new audit standards to ensure that code commits correspond to Objectives written by a human. If something goes wrong where you need to back out a commit / PR that's fine, because it's still just github underneath. This would take place at a Human review gate in 'Acceptance.'
The objective would typically not be Accepted and would be rejected for not meeting specific acceptance criteria by the human/human + agent. this places the objective back in the queue in Scheduled or Backlog where another agent can pick it up later for rework.
How does Planwright handle conflicts when multiple agents (Claude Code, Cursor, Codex) are working on overlapping objectives at the same time, and is there a way to manually intervene if an agent goes off-track?
@bernahru8 each objective can only be claimed by one agent at a time. ('In Progress'). We ensure the overall plan is consistent by performing quality checks when initial Objectives are injected on to the board. If those new objectives overlap or are mal-formed, planwright will reject them and/or mark them as unclear/needs refinement for you.
Finally tried this with our Cursor setup and the audit trail alone is worth it. Love that every decision gets signed automatically, no extra work from the team.
@erafettinkdku2 no TPS reports!
Finally something that takes the bookkeeping off my plate when my agents start running wild. The signed decisions log is the kind of boring-but-essential feature I didn't know I wanted until I had it.
@berkay135817 Thats the emotionally draining work that grinds on you in a traditional project tracker. Thanks for checking us out!
The audit trail and signed decisions idea is genuinely useful, especially with so many AI agents touching code now. Curious how it handles drift when agents loop on a task.
The signed-decision trail is genuinely useful, finally gives me something concrete to show compliance rather than a pile of chat logs. Curious how it handles branches when agents are working in parallel.