THE MEDIA FOR AI THAT ACTUALLY HELPS.English edition · Understand & take action
Spotted on the web

Keep the product documentation up to date at the end of each project

Use described publicly by Dust — Alma (30 June 2026), summarised by the desk. Not tested by iadujour.

The result to aim for

At Alma, an agent reads the balance sheet written by the product manager at the end of a project and proposes updating the documentation; the product manager re-reads, corrects and publishes.

What was done

According to the case study published by Dust on 30 June 2026, Alma's product managers were already drafting a project completion brief (which changes, why, deployment, operational impacts, dependencies), but the documentation remained difficult to maintain. Agent @productopia reads this brief and publishes an update proposal in a dedicated Slack channel; the right product manager then publishes it in Notion. Dust indicates that in one quarter, the share of up-to-date documentation has increased from 55% to 87%, and that product managers report spending less than half the usual time. The agent was then extended to the entire company to answer questions from this documentation.According to the source, Operations and Risk Analysts have also built an assistant themselves that collects payment information and prepares structured reports on fraud cases, with decisions still being made by analysts.

Before you start

Tool cited by the source: Dust. Fill in the bracketed items: [coller]. Strip confidential data that is not needed and check your tool’s access terms. Features and plans can change.

The method, in three steps.

  1. Gather the context

    Spot the bracketed items in the prompt ([coller]) and prepare what they ask for.

  2. Adapt the prompt

    Copy the prompt below, replace the bracketed items, then paste it into Dust.

  3. Reread before using

    Reread the result, correct it if needed and keep the final decision. Caveats are detailed below.

Your starting point.

Replace the bracketed items, then adapt the proposal to your situation. This prompt is written by the iadujour desk It is not a quotation from the source.

The prompt to customise
The end-of-project balance sheet is as follows: [what has changed, why, deployment date, impacts for teams, dependencies].
The current documentation page is [coller].

Proposes updating of documentation: sections to be amended, proposed text, items that have become obsolete to remove. Report what is unclear in the balance sheet instead of guessing. Presents the whole as a proposal: I reread and publish myself.

What deserves your attention

A generated documentation that is not reread ends up contradicting the actual product: keep the human validation before publication and date each update.
Origin of the case. Use described publicly by Dust — Alma (30 June 2026).
Proof level: Statement by the tool’s publisher. Source checked on 10 November 2026. Use described by the source, not tested by the desk. Original summary written by iadujour.fr: figures and claims are the source’s; the prompt is a desk proposal, not a quotation.
TO GO FURTHER

Other ideas to put to work.

The whole Productivity theme
DISCUSSION

Comments.

A field note, a question, a precision on this use case? Comments are reviewed before publication.

Published comments

Loading comments…

    Leave a comment

    Moderation charter. Every comment is reviewed before publication. We refuse hate speech, insulting or discriminatory language, advertising, spam and promotional links, off-topic posts and other people’s personal data.