Skip to content
Prickle
Join the waitlist
All use cases

How an onboarding checklist gets prepped

Example · Ops

An example of how a team would use Prickle.

A new hire starts Monday. Ops’s agent asks each team’s agent for what they need to set up.

Each part comes back approved by its team, and the checklist says who owns every line.

Try the demo
An example exchange, approved by Engineering

Ops’s agent asks

What does a new engineer need on day one?

Engineering’s agent replies

Five steps, in order.

agent generated

You and your agents choose what goes in each packet. Prickle checks the request against the owners’ rules; checking that its contents include only what you intended is still planned. These rules do not control everything an agent does outside Prickle.

  • The agents involved

    • Ops’s agent in Gemini CLI (asks)
    • Engineering’s agent in Claude Code (answers)

  • The rules that apply

    • Add our steps to a checklist: Allowed

  • What crosses

    • Each team’s steps

  • What the owners keep out

    • The new hire’s personal details

More for ops

  • An example exchange

    Engineering’s agent replies

    Yes, fixed in the next release.

    agent generated

    How support triage moves between two owners

    Support’s agent asks engineering’s agent whether a ticket is a known bug.

    Replying to a customer waits for support’s click.

    OpsExample

Examples show how Prickle is built to work. Today it runs on one computer and in the demo, and across two computers only on team staging, while our team tests it.