agentleFS
Sign inStart free
imMamdouhaboammarimMamdouhaboammar/matts-skills-into-chatgpt/skills/workflow-designer/SKILL.md

workflow-designer

Skill8 starsChanged 2 months agoMITView on GitHub

Specify recurring operational, review, or content workflows with explicit triggers, inputs, actions, and ownership. Use when designing repeatable team routines, approval loops, release checklists, or automated processes — even if the user says \"design a workflow for this\". Do NOT use for one-off coding tasks.

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Mandate Nothing Structural: Only add AI agents, schedules, or approval gates when the problem domain strictly requires them.

    line 16
  2. Distinctive:

    Action: Run a focused grilling round exploring:

    line 44
  3. Very specific:

    Action: Write the workflow contract to workflows/<name>.md detailing trigger, inputs, actions, checkpoint briefs, and outputs.

    line 55
  4. Distinctive:

    Key Point: Ensure an implementer agent could implement scripts or automations from the document alone.

    line 56

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Workflow Designer

Design and formalize repeatable human-in-the-loop and autonomous workflows by identifying cyclical operational loops, pushing checkpoints right, and defining unambiguous execution contracts.

Core Invariants

  1. Push Checkpoints Right: Defer human checkpoints as far downstream as possible; maximize autonomous work before requesting review.
  2. Actionable Decision Briefs: Checkpoints must present a tight, decision-ready brief with clear diffs and links—never raw, uncurated outputs.
  3. Mandate Nothing Structural: Only add AI agents, schedules, or approval gates when the problem domain strictly requires them.
  4. Self-Contained Spec Completeness: A workflow specification is complete only when an implementer agent can build it without asking clarifying questions.
  5. Durable Notes Separation: Distinguish between immutable workflow specifications (workflows/*.md) and evolving domain observations (NOTES.md).

Architecture & Map of Content (MOC)

[ Operational Habit / Team Routine ] ──► [ Loop Identification & Grilling ] ──► [ Workflow Formalization ] ──► [ Implementer Handoff ]
ComponentResponsibilityLocation
Workflow SpecificationExecutable contract (trigger, inputs, actions, checkpoints)workflows/*.md
Domain & Tools NotesObserved vocabulary, habits, tools, and channelsNOTES.md
Grilling ProtocolSocratic distillation of requirements and boundary edgesskills/grilling/SKILL.md

Step-by-Step Procedure (TWI)

Step 1: Identify Cyclical Loops & Document Baseline Notes

  • Action: Analyze the user's recurring tasks (daily, weekly, per-release) and record observed tools/channels into NOTES.md.
  • Key Point: Map the natural lifecycle from trigger to final delivery.
  • Why: Capturing the current baseline prevents designing theoretical workflows that mismatch daily reality.

Step 2: Conduct Socratic Grilling on Workflow Boundaries

  • Action: Run a focused grilling round exploring:
    • Trigger: Event-based (e.g. webhooks, new issue) vs. time-scheduled (e.g. cron).
    • Inputs & State: Exactly what artifacts must be ingested.
    • Actions: Discrete operational or agentic transformations.
    • Checkpoints: Minimal review gates pushed to the end.
  • Inline Checklist:
    • Triggers clearly specified with fallback polling intervals
    • Checkpoints provide decision-ready briefs
    • Failure paths and escalation owners defined

Step 3: Author Executable Workflow Spec

  • Action: Write the workflow contract to workflows/<name>.md detailing trigger, inputs, actions, checkpoint briefs, and outputs.
  • Key Point: Ensure an implementer agent could implement scripts or automations from the document alone.
  • Why: Ambiguity in workflow contracts causes brittle automation failures.

Anti-Rationalization Guardrails

Tempting RationalizationBinding RuleEngineering Rationale
"Ask the human to verify every intermediate step."Push checkpoints right; batch human reviews.Frequent interruptions cause human fatigue and destroy automation efficiency.
"Dump raw log files for the human checkpoint."Produce synthesized, decision-ready briefs.Humans review clean executive summaries 10x faster than raw debug logs.
"Assume an LLM agent is required for every workflow step."Use deterministic scripts where possible; AI only where judgment is needed.Deterministic scripts are faster, cheaper, and more reliable than LLMs for structured operations.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free