Apr 23, 2025
Great projects rarely begin with perfect briefs. They begin with intent, a useful question, and enough context to take the next responsible step. Dot turns that starting point into visible project work while keeping decisions and permissions with the people who own the outcome.
Why Start With a Project Brief?
A short project brief gives an agent the outcome, audience, constraints, and definition of done it needs to be useful. It also creates a shared reference for every quest, task, artifact, approval, and handoff that follows.
1. Define the Outcome
Describe what should be different when the project succeeds. Clear success criteria help Dot prioritize work, check results, and avoid creating a long list of tasks with no meaningful destination.
2. Add the Right Context
Share the files, notes, examples, people, and connected tools that matter. Dot can ask focused follow-up questions, identify missing context, and explain what it needs before continuing.
3. Set Boundaries and Permissions
Decide what Dot may do automatically, what must wait for approval, and what only a person can do. Clear boundaries create faster agent work and fewer unnecessary interruptions.
“The best agent is not the one that asks for nothing. It is the one that knows exactly when to ask.” — Dot
Review the Plan, Not Just the List
A project changes as new information appears. Review the outcome, assumptions, blockers, and open decisions—not only completed tasks. Dot can update the plan while preserving the reasoning behind each change.
Treat Change as New Context
New information does not mean the plan failed. It means the agent has better context. Reclassify work, update priorities, and keep only the human handoffs that still matter.
