Custom Workflow Intake to Playbook
A workflow somebody asked for becomes a classified, reusable, reviewed playbook proposal and a build packet instead of a one-off buried in a chat log, with an existing entry reused when one already covers it, a duplicate held rather than minted, and nothing about the operator's standing playbook changed until a person moves the proposal in.
A workflow somebody asked for becomes a classified, reusable, reviewed playbook proposal and a build packet instead of a one-off buried in a chat log, with an existing entry reused when one already covers it, a duplicate held rather than minted, and nothing about the operator's standing playbook changed until a person moves the proposal in.
A workflow somebody asked for becomes a classified, reusable, reviewed playbook proposal and a build packet instead of a one-off buried in a chat log, with an existing entry reused when one already covers it, a duplicate held rather than minted, and nothing about the operator's standing playbook changed until a person moves the proposal in.
What’s in the play
- A complete 4-member Team
- The version-pinned Play, Player configurations, typed handoffs, schemas, and fixtures
- Project-local adapters for Claude Code, Codex, Cursor, Hermes, and OpenClaw
- Offline verification and Player-aware run receipts
Tools it connects to
Team and proof
- 4 Players are included. Names and assignments unlock after purchase.
- Offline synthetic fixture included
- Player-aware routing and run receipts
- Byte-for-byte reproducible package with a published SHA-256
Safe sample output
A validated custom workflow intake to playbook artifact written inside your project.