Skip to content
All use cases

How a launch post comes from what shipped

Example · Marketing

An example of how a team would use Prickle.

Marketing’s agent drafts from merged work, not from memory. It asks engineering’s agent for what shipped, and every claim in the draft points back to it.

Posting is outbound, so it waits for a person’s click.

Try the demo
An example exchange

Marketing’s agent asks

What shipped this week, in plain words?

Engineering’s agent replies

Three changes. Here they are, with links.

from approved context

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 Claude Code (asks)
    • Engineering’s agent in Codex (answers)
  • The rules that apply

    • List what merged this week: Allowed
    • Post on our accounts: Ask me first
  • What crosses

    • What merged
    • The draft post
  • What the owners keep out

    • Unreleased work

More for marketing

  • An example exchange

    Product’s agent replies

    Five hold. One is planned, not shipped.

    agent generated

    How a team checks every claim before posting

    Marketing’s agent asks product’s agent to check each claim in a draft.

    Product approves the facts it vouches for.

    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.