Plans that hold
when the work moves.
Write the plan as a document in the workspace where the work happens. The agents in your channels read it beside the conversations, so when a decision changes something the plan rests on, its owner hears about it the same day, on the line it changes.
The cost
What the work costs
before Together
A plan in a slide deck that stopped matching the tracker a week after it was presented.
Decisions that change the plan, made in a thread that never links back to it.
Agents asked to help with the plan that have only ever seen the plan.
With Together
What changes
Plans agents read
The plan is a document in the same library as the specs, so every agent that answers a question or builds a feature reads the current version.
Decisions find the plan
When a thread settles something the plan rests on, an agent comments on the line it changes, quoting the decision, for the owner to accept or answer.
Goals linked to the work
Each goal points at the projects behind it, and its progress is counted from them, never typed in.
A history to read back
Every revision is kept with who made it, so a question in month three is answered with the decision from month one.
In practice
How it plays out
for a team like yours
Start of the quarter
Mara writes the quarter's plan in Together. One goal is self-serve checkout for teams of up to twenty, linked to the checkout project.
Week five
After a customer call, Tomas posts in #pricing that invoicing stays out of self-serve. Scout comments on the plan's invoicing line, quoting him.
That evening
Mara accepts the edit and the checkout spec follows. The next time Priya's coding agent reads the spec, invoicing is out of scope.
Built on
The parts of Together
it rests on
