Dots project follow-up workflow
Keep one current view of decisions, owners and deadlines.
Set up the inputs
Replace the bracketed fields with actual sources, destinations and timing. Connect the relevant plugins or provide the files directly. Keep the first run focused on one project so feedback is easy to apply.
What a useful result looks like
A design approval moves by two days. The update shows the old date, new date, affected implementation milestone and the person who can unblock it.
Run it once, then repeat
Paste the task brief below and request one complete result. Open the source links, check the dates and owners, and revise the format. For recurring work, have the dot confirm the schedule and destination after the first result meets your needs.
Improve the brief over time
When you edit an output, state the reusable preference behind the edit. Keep project facts in the named source documents. Update the brief when the responsibility changes, and review its end date when the project closes.
Copy this task brief
Maintain the status of [project] through [end date]. Sources of truth: [plan], [issue board], [named conversation channels]. On conflicts, prefer [primary source] and show the conflicting source beside it. Create a tracker with milestone, owner, due date, current status, next action and source link. Each update must separate: newly added, changed, completed and waiting on a decision. Check at [frequency, time, time zone]. Confirm the recurring task. Notify me in [channel] when a milestone slips, a dependency blocks the next step, or a decision needs me. Keep routine unchanged checks quiet. For each decision, give the options and your recommended next step. Start with a baseline tracker and list the information you still need.Download Markdown ↓