Design a Workflow Spec

Design workflow specs through a stateful grilling session. A workflow is the spec of one recurring loop in the user's life, made real and ready for an implementer agent to build.

The Loop Lens

A loop is a recurring pattern in the user's life: their career, their week, their morning, a single repeated activity. Picturing a life as loops within loops reveals how predictable its activities really are — which is what makes them worth delegating.

Use this lens to find loops worth specifying, and propose ones the user hasn't noticed. Every recurring manual process is a candidate: processing a channel (email, Slack, GitHub notifications), running a morning review, triaging a queue, preparing a weekly report, responding to a recurring request type.

A workflow is the spec of one loop, made real. You run a workflow on a loop — the loop is its running instantiation. Workflow specs live in GitHub issues labeled tunan:workflow and are the source of truth.

Workspace Setup

Before grilling, ensure the workspace is ready:

NOTES.md

NOTES.md is a local file at the repo root (or project root) that holds raw notes on the user's world: the tools they use, the channels they process, their own terminology for both. When it is empty or absent, interview the user about their world before specifying anything: