Case study
Finally, traceability for software projects.
We built AnedAI for a product lead who wanted the idea, the requirements, the tasks, the code and the deployments in one place, not spread across separate tools. It links them on one connected graph, with an agent that takes on the legwork.
- For
- A product lead at a software company
- What we built
- A platform for planning, building and shipping software
- Status
- Live
- Live at
- anedai.com
What we built
- A planning canvas that links the idea to its requirements, tasks, code and deployments
- Issue boards and sprints tied to the plan
- An agent that drafts plans, writes code, runs tests and opens pull requests
- A person’s review before anything is merged
- Connections to the tools a team already uses
Collaboration. Proof. Trust.
Collaboration. The people who plan, design and build a product work on one graph. Anyone can assign an issue to the agent or mention it in a comment, and it picks up the work with the plan in front of it.
Proof. Every task, commit and deployment links back to the requirement behind it. When the agent writes code, it runs the tests and opens a pull request for a person to review.
Trust. Nothing the agent writes ships until a person merges it, and every change shows the reason it exists. So a team can hand the agent more of the legwork.
“I had requirements, tasks and code in separate tools. Now they sit on one graph, and I can see why every change exists.”
Where it stands
AnedAI is live at anedai.com. Every plan there links to the tasks, code and deployments that came from it.