Operations specialist
Default Kona assistant
Workspace Orchestrator
Turns ambiguous work into a sequenced, evidence-aware deliverable plan.
When to use it
A focused role with a visible finish line.
Best for: operators coordinating processes, projects, vendors, and repeatable delivery.
Expected outcome: an executable work plan with owners, dependencies, controls, and acceptance criteria.
- A focused workspace, task, orchestration task where the expected decision or deliverable is clear.
- Recurring work that benefits from the same outcome, workstreams, acceptance criteria structure each time.
- A team that wants Workspace Orchestrator available in direct chat, inline @mentions, and bounded Workspace tasks.
Configured instruction
“Clarify the outcome, identify the smallest useful workstream, route research/calculation/build steps to the right specialist, and return a concrete execution plan with assumptions and acceptance criteria.”
This instruction is part of the shipped default profile—not a generic prompt assembled for this page.
Workflow
How Workspace Orchestrator approaches the work
Frame the outcome
State the decision, audience, deadline, constraints, and what a useful an executable work plan with owners, dependencies, controls, and acceptance criteria looks like.
Ground the work
Provide relevant the current process, constraints, owners, service levels, dependencies, and operating data. Label supplied facts, working assumptions, and unresolved unknowns.
Build the contracted output
Workspace Orchestrator follows its workspace output contract and covers outcome, workstreams, acceptance criteria, assumptions.
Verify before use
Run the profile's quality checks, expose evidence gaps, and route high-impact low-risk conclusions to human review.
Capabilities
What the profile can use
- Knowledge grounding
- Structured deliverables
- Verification pass
- Current web research
- Analysis and code
- Editable workspace artifacts
Enabled tool families: web, code, canvas. Runtime availability still depends on account configuration, permissions, and the task.
Output contract
What a complete response must contain
The contract improves consistency; it does not make an answer automatically correct. Kona still marks assumptions, evidence gaps, and review requirements.
Prompt examples
Start with context and a decision
Prompt example
Act as my Workspace Orchestrator. Clarify the outcome, identify the smallest useful workstream, route research/calculation/build steps to the right specialist, and return a concrete execution plan with assumptions and acceptance criteria. Start by listing the missing inputs that would materially change the result.
Prompt example
Use the Workspace Orchestrator workflow for this workspace task: [describe the situation]. Audience: [who will use it]. Constraints: [time, budget, policy, or data]. Return outcome, workstreams, acceptance criteria, assumptions.
Prompt example
Review this draft as the Workspace Orchestrator: [paste draft]. Check it against the stated evidence, identify unsupported claims or missing assumptions, and return a prioritized correction list.
Put Workspace Orchestrator to work.
Use the default profile or fork it into a version your team controls.