About design-workflow
A stateful interview skill that turns decisions about recurring activities into implementable workflow specifications. It uses dependency-aware question rounds and keeps specifications in `workflows/*.md`, with contextual notes in `NOTES.md`.
Key features
- 01Dependency-aware interview rounds
- 02Identify recurring loops worth specifying
- 03Create and update workflow specifications
- 04Keep user context in NOTES.md
- 05Define completion by implementability
Use cases
- 01Specifying a recurring personal or work activity
- 02Turning interview decisions into an implementation-ready workflow
- 03Maintaining workflow documents as decisions change
Install
Copy the command and run it in a terminal.
npx skills add https:/After installing, type/design-workflowin Claude Code to confirm it loaded.
Bundled files
References and scripts installed along with SKILL.md.
apm.ymlagents/openai.yamlreferences/interview.mdDetails
From the project READMERun a stateful interview whose output is workflow specifications, following the interview method: dependency-aware question rounds with recommended answers, aimed at the vocabulary and goal below. Create and update specifications as decisions are resolved; remove an obsolete specification only when its replacement and useful history are preserved.
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 the lens to find loops worth specifying, and propose ones the user hasn't noticed.
A workflow is the specification of one loop, made real. You run a workflow on a loop: the loop is its running instantiation. Workflows live in workflows/*.md and are the source of truth.
Vocabulary
A shared language, reached for only when a workflow calls for it: never a checklist. Mandate nothing structural: a workflow needs no AI, no checkpoint, and no schedule unless the grilling shows it does.
- Trigger: what fires each run, an event (a new email, a new issue) or a schedule (every morning). Event-triggering is usually the more efficient.
- Checkpoint: a human-in-the-loop point where the user is asked to verify or decide. Some workflows have none and run autonomously; some use no AI at all.
- Push right: defer the checkpoint as far as it will go. Do maximal work before involving the human, so they are asked once, late, with everything prepared.
- Brief: what a checkpoint presents, a tight, decision-ready summary (what was produced, why, and a link down to the asset itself), never the raw output. The user reads a brief, not a draft. Speed of review is imperative.
Definition of done
A workflow specification is done when an implementer agent could build it without asking a single question. Grill until then; nothing is done while a question remains.
The workspace
workflows/*.md: one specification per workflow.NOTES.md: raw notes on the user's world, the tools they use, the channels they process, and their own terminology for both. When it is empty or thin, interview them about their world before specifying anything. Sharpen fuzzy terms into canonical ones as they surface, and record them here.