Document a front-desk process

01 / WHAT TO TRY

Start with the right material.

Publisher description excerpt: “Document a business process — flowcharts, RACI, and SOPs. Use when formalizing a process that lives in someone's…” Source ↗

Suggested preparation

• Current administrative process notes
• Team roles
• Approved policies and exceptions

These are Fieldwork’s preparation notes. Follow the source’s full input checklist for the specific task.

The intended handover

An SOP with owners, steps, exceptions, and a review date.

This is a source-inspected starting point. Fieldwork has not run-tested this skill or measured time savings.

02 / CHECK THE FIT

Your platform. Your context.

Platforms

Claude

Publisher documents a Claude/Agent Skills setup. Review the complete pack and its current installation instructions.

Australian and worldwide use

Geography-neutral workflow. Set Australian spelling, AUD, dates and business context explicitly; local compliance is not supplied by this label.

Setup type: Connected apps

No named business app was detected in the inspected instructions.

Dependencies

• The source references app or connector access; install/configure the complete plugin and confirm permissions.

Public instructions do not imply free access to Claude, ChatGPT, paid apps, API usage or generation services.

03 / SET IT UP

Keep the complete workflow.

1. In Claude Code, add the publisher’s marketplace:
2. claude plugin marketplace add anthropics/knowledge-work-plugins
3. Install the full plugin so supporting files and connectors stay together:
4. claude plugin install operations@knowledge-work-plugins
5. Start a fresh session, supply the listed inputs, and use the starter prompt. For Cowork or chat, use Customize → Plugins and follow the current official guide. Connector access depends on your setup; uploaded files can support the selected draft workflow.

Pinned source snapshot; review publisher release and installation notes.

Replace the brackets and supply the required inputs. This prompt is Fieldwork’s example, not a tested guarantee or a replacement for installation.

Use process-doc to document our [administrative process]. Here are the current steps and owners: [notes]. Identify missing decisions instead of inventing practice policy. Include exception handling and a review checklist. Exclude clinical protocols and patient identifiers.