Publish the way you build, not just what you built.

You have a process that works with AI — the roles, the handoffs, the checkpoints, the rules you only learned by breaking something.

Right now it lives in your repo, and nobody can take it. Penguinstone is where a whole process gets published, so someone else can run it and send back what they improved.

What a published workflow looks like

Lane discipline published by a solo operator · 6 repos

Four agent roles, work packages, and a handoff ritual that survives a session dying mid-task.

Modules: engineering product design data
Roles: orchestrator → planner → worker → reviewer
Runs on: Claude Code, Cursor, Copilot
Track record: 11 rules, each kept only after it survived 2 real incidents · 3 forks · 7 changes merged back

Take a copy Suggest a change EXAMPLE — not a live listing

Take it

Copy someone's whole process into your own setup — their roles, their checkpoints, their hard-won rules. Not a prompt. The method.

Send it back

Found a better handoff? Propose the change to the process itself, the way you'd propose a change to code.

See what held up

Every workflow shows what it built and what broke. A rule that survived real failures beats one that sounds good.

Built in parts, so you can take one

A process is not one blob. Take the whole thing, or take the piece you're missing.

Core

handoffs checkpoints secrets picking up where you left off

Modules

product design data engineering sales

Bundles

for a founder for a PM for an engineer

Early access

Want to see it, or publish the first one?

It isn't open yet. Leave an address and you'll hear when there's something real to try — or ask for a walkthrough of where it stands today.

Or write directly: hello@penguinstone.com