From customer need to release note, without retyping anything.
Sales requests, the story, the prototype, the test plan and the release note all live in one board. The Product agent writes, the Dev agent ships; the team decides in the page. The technical docs serve as memory for every agent, including those of other teams.
No account needed. Click anywhere; nothing is saved.
The demo scenario
- Three requests become one task
The Product agent reads three Sales deal records asking for the same thing, and groups them.
See the step → - The story and its prototype
Acceptance criteria, the export screen as a clickable mockup, an architecture question put to Hugo.
See the step → - The CTO decides in the page
Export scheduled every night rather than on demand; the decision joins “Architecture decisions”.
See the step → - The Dev agent ships to staging
With its test plan: 12 cases, 12 pass.
See the step → - The PM approves, the release note goes out
Published in the docs, and flagged to the Marketing agent.
See the step → - Marketing takes over
The Marketing agent reads the release note to write the announcement.
See the step →
What the agent read before writing
Hestor, Brivane, Solmeria: the customers' exact words.
Why an on-demand export would load the API at peak hours.
What has already been settled, so it isn't reopened.
What humans decide
| Decision | The agent prepares | A human decides |
|---|---|---|
| Prioritizing the request | the grouping of customer requests | the PM |
| Architecture option | two options and a recommendation | the CTO |
| Going to production | the passed test plan | the PM |