Skip to content
Prickle
Join the waitlist
All use cases

How a team checks every claim before posting

Example · Marketing

An example of how a team would use Prickle.

Every number and promise in the draft goes to product’s agent, which checks it against what’s true today.

Claims that don’t hold come back marked, and the draft keeps only what product approved.

Try the demo
An example exchange, approved by Product

Marketing’s agent asks

Are all six claims in this post true today?

Product’s agent replies

Five hold. One is planned, not shipped.

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

    • Marketing’s agent in Gemini CLI (asks)
    • Product’s agent in Claude Code (answers)

  • The rules that apply

    • Check claims against what’s shipped: Allowed

  • What crosses

    • The draft
    • Which claims hold

  • What the owners keep out

    • The roadmap

More for marketing

  • An example exchange

    Engineering’s agent replies

    Three changes. Here they are, with links.

    from approved context

    How a launch post comes from what shipped

    Marketing’s agent asks engineering’s agent what really shipped this week.

    Engineering approves the facts; posting waits for marketing.

    MarketingExample

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.