Skip to content
SilktideHelp

From briefs to tasks

A strategy brief does not end with a conclusion. It ends with work.

Every recommendation becomes a task, and tasks in Presence are the same tasks as everywhere else in Silktide: they have a status, a priority, an effort estimate, an assignee, and a full history. The difference is where they came from, and that Silktide keeps watching what you do with them.

Nothing is imposed on you

Recommended tasks arrive as Proposed. They are visible, but they are not yet work anybody has agreed to do. That state exists because an AI strategist filling your backlog without permission would be intolerable, however good its reasoning.

You triage each one:

  • Accept. The task joins your workflow - it moves to Backlog and behaves like any other task from then on.
  • Decline. The task is cancelled. It is not deleted: it stays on record, which matters for what happens next.
  • Edit. Titles and descriptions can be rewritten before or after accepting. If the recommendation is right in substance but wrong about your CMS, your team, or your constraints, fix it and accept it.

You can triage from What to do on Overview, from the recommendation cards while reading a brief, or from the task list later. On the Tasks list, Suggestions awaiting review lifts proposed work out of the table so you can Accept or Decline it in place.

Declining is a real answer, not a failure to engage. A recommendation may be technically sound and still be wrong for you - out of budget, out of scope, or something you tried in 2024. Saying so is more useful than leaving it open forever, because a declined task is information.

Where the tasks live

Presence has a Tasks screen showing only tasks that came from AEO work: strategy briefs, commissioned briefs, and page-level AEO reports. Everything else in your account is filtered out, so it is a clean view of the AEO backlog.

Clicking "N of M tasks done" on a brief opens the same screen narrowed to that one brief's recommendations.

The full Tasks area in the main navigation shows everything, AEO or otherwise, and is where work usually gets managed day to day.

Working in your own tracker

Most teams do not want a second place to look at work. If you have connected Linear in Settings → Integrations, accepting a task creates an issue in your Linear workspace, into the team and project you nominate. Moving it back to proposed deletes that issue.

Two limits are worth knowing before you rely on it:

  • Proposed tasks stay in Silktide. Accepting is what publishes. That keeps untriaged suggestions off your team's board.
  • Publication is one-way. Later edits on either side stay on that side. Treat Silktide as where the recommendation was made and Linear as where the work is run.

Support for other trackers is planned. When it arrives it will work the same way, from the same integrations screen.

Closing the loop

This is the part that makes triage worth doing.

When you run the next edition of a brief, the strategist is told what happened to the last edition's recommendations: how many were completed, how many declined, how many still open. It uses that to:

  • Lead with what changed rather than re-describing a situation you already read about.
  • Connect work to movement. Where a number improved after related work landed, it says so - carefully, as correlation rather than proof, because nobody can demonstrate that an assistant changed its answer because of one page.
  • Carry forward the outstanding work instead of proposing it again as if it were new.
  • Respect your refusals. Something you declined will not simply reappear next edition. It can only come back if there is materially new evidence for it, and the brief has to say what that evidence is.

So the honest answer to "does any of this work?" is not a vendor's claim. It is the score on your own briefs, edition over edition, against work you can see you did.

Last updated

Was this page helpful?

From briefs to tasks | Silktide Help