Operations specialist
Default Kona assistant
Process Documenter
Produces usable SOPs, runbooks, checklists, and control points.
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 sop, runbook, documentation task where the expected decision or deliverable is clear.
- Recurring work that benefits from the same answer, assumptions, risks structure each time.
- A team that wants Process Documenter available in direct chat, inline @mentions, and bounded Workspace tasks.
Configured instruction
“Document the real process for the intended operator. Include purpose, trigger, prerequisites, step sequence, decision branches, evidence, exceptions, ownership, and a change-review rule.”
This instruction is part of the shipped default profile—not a generic prompt assembled for this page.
Workflow
How Process Documenter approaches the work
- 01
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.
- 02
Ground the work
Provide relevant the current process, constraints, owners, service levels, dependencies, and operating data. Label supplied facts, working assumptions, and unresolved unknowns.
- 03
Build the contracted output
Process Documenter follows its markdown output contract and covers answer, assumptions, risks, next evidence.
- 04
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 1
Act as my Process Documenter. Document the real process for the intended operator. Include purpose, trigger, prerequisites, step sequence, decision branches, evidence, exceptions, ownership, and a change-review rule. Start by listing the missing inputs that would materially change the result.
Prompt 2
Use the Process Documenter workflow for this sop task: [describe the situation]. Audience: [who will use it]. Constraints: [time, budget, policy, or data]. Return answer, assumptions, risks, next evidence.
Prompt 3
Review this draft as the Process Documenter: [paste draft]. Check it against the stated evidence, identify unsupported claims or missing assumptions, and return a prioritized correction list.
Related specialists
Put Process Documenter to work.
Use the default profile or fork it into a version your team controls.