A project needs an outcome before it needs a dashboard. This small example creates a plain-text plan that a teammate can review without installing a service.
Create the directory
mkdir atlas-project
cd atlas-project
Create plan.txt with these contents:
Outcome: publish the support handover guide
Owner: the person coordinating the release
Next step: ask support which questions are missing
Check the plan
Open the file and check that the next step can actually be performed. “Finish the project” is not a useful next step: it repeats the outcome without explaining what comes first.
Review changes
Keep the plan with the project's other files. When the outcome changes, update this file rather than leaving a second version in a chat message.