BotCurrent↗
← Back to examples

Official recipe · Research across apps

Assemble a strategy-grounded quarterly kickoff deck

Source-backed example. Practical decision guidance is proposed and untested; this is not a full implementation guide.

The problem

Quarterly kickoff preparation requires connecting strategy, previous results and backlog choices so the team can discuss priorities with shared context.

Agent job

Combine strategy documents, prior results and the backlog into an OKR kickoff deck.

Expected output

A quarterly kickoff presentation for review.

Where this framing comes from
  • Core problem: Editorial purpose framing
  • Agent job: Editorial purpose framing
  • Expected output: Editorial purpose framing
  • Relevant job roles: Editorial purpose framing
  • Benefit type: Editorial purpose framing
Editorial framing and outcome limits

Describes the task’s purpose and intended output; measured benefit, safe unsupervised operation and successful delivery are not established by this framing.

Editorial synthesis based on the linked source. This framing does not add evidence of successful delivery or results.

Case-specific decision guidance · untested

Case-specific decision guidance and first checks are original proposals. The linked source supports the attributed task; this added guidance has not been executed.

Read the attributed source evidence and original caveats below ↓

Why use this

  1. A team preparing a quarterly kickoff may have strategy documents, prior results and a backlog that tell different stories about priorities. Turning those materials into slides can hide unresolved choices behind a coherent narrative.

  2. A source-linked deck outline could expose where proposed objectives follow from strategy and where a decision is still needed. Reviewers could then discuss trade-offs before presenting tentative work as committed plans.

Why an agent / simpler alternative

Useful judgment

Connect priorities with prior results and backlog candidates while surfacing contradictions.

Simpler alternative

Use a standard deck template when objectives and evidence have already been agreed.

Unsuitable when

Leadership expects the agent to choose strategy or commit owners and targets.

Proposed inputs

  1. Name

    Planning evidence pack

    Owner

    Planning owner

    Minimum scope

    Current strategy, prior-period results and dated backlog snapshot

    Quality check

    Confirm versions, measurement periods and status labels.

  2. Name

    Kickoff brief

    Owner

    Meeting owner

    Minimum scope

    Audience, review purpose and existing approved objectives

    Quality check

    Distinguish approved decisions from discussion options.

Access and setup — proposed or unknown

Proposed minimum
  1. Read-only planning copies; separate draft presentation destination.

Compatibility unknowns
  1. Unknown: exact runtime, source connectors and slide-generation compatibility.

External actions requiring approval
  1. Sharing the deck, assigning commitments or changing backlog priorities.

Expected deliverable and review checks

Proposed artifact

Draft kickoff deck with evidence references, proposed objective links and decision slides.

Critical checks
  1. Results preserve units, periods and source definitions.

  2. Unapproved objectives, owners and targets remain explicitly tentative.

Missing output evidence

No inspected deck, accepted OKRs or demonstrated planning outcome is supplied.

Failure signals and proposed responses

  1. Signal

    An old strategy draft conflicts with the latest approved document.

    Why it matters

    The narrative may justify obsolete priorities.

    Proposed response

    Use the approved version and expose unresolved conflicts.

  2. Signal

    A backlog idea becomes a committed key result.

    Why it matters

    The deck could imply authorization that never occurred.

    Proposed response

    Relabel it as a candidate and request the owner’s decision.

Effort and cost — unknown

Setup work
  1. Collect authoritative planning versions and agree deck purpose.

Ongoing review
  1. Validate metrics, priority links and presentation claims.

Unknowns
  1. Unknown: slide tooling costs, source cleanup and stakeholder review effort.

First check — proposed, unexecuted

Status

proposed_unexecuted

Synthetic fixture

A fictional strategy prioritizes reliability; the backlog includes an unapproved feature and last-quarter results use a different reporting period.

Acceptance checks
  1. The feature remains a discussion option.

  2. Metric-period mismatch is flagged rather than normalized silently.

Stop conditions
  1. A target, priority or owner must be invented.

Limits

  1. Editorial planning proposal; narrative coherence does not validate strategy or commitments.

Tasks: Documents & files

Useful for: Project managerProduct managerBusiness owner

Editorial relevance from the title and source-supported actions; not evidence of the operator’s occupation.
Perplexity ComputerIndependent testing: No

Editorial candidate. This is source-backed reporting or a documented workflow. BotCurrent has not independently tested this task. A proposed Canadian adaptation is not evidence of a Canadian deployment or compliance certification.

Original source

https://www.perplexity.ai/en-GB/hub/blog/computer-in-slack-from-shared-context-to-finished-work ↗

Attributed to: Perplexity

Official recipe
Original action type
cross_app_investigation
What the source supports
Combine strategy documents, prior results and backlog into an OKR kickoff deck.
Source outcome limits
This official recipe describes a procedure; it does not prove successful execution or independently reproduced results.
Evidence attribution caveat
This official recipe describes a procedure; it does not prove successful execution or independently reproduced results.
Source approval description
Not specified.
Named tools
Computer; Slack; strategy documents; backlog
Model or version
Unknown
Publication date
2026-04-01
Source last checked
2026-10-14
Demonstrated in Canada
Unknown
Canadian availability
unknown; not inferred from general product availability
Proposed Canadian adaptation
Proposed: Confirm Canadian service access, applicable privacy requirements, and English/French needs before any pilot.
Recommended approval boundaries
Approve access scope; review changes and outputs before external sharing or consequential action.