agentleFS
Sign inStart free
MfrostbutterMfrostbutter/skill-forge/skills/workflow-capture/SKILL.md

workflow-capture

Skill4 starsChanged 5 months agoMITView on GitHub

Maintain a durable, tagged journal of a complex workflow so it can later be distilled into a reusable skill. Use this whenever beginning a complex, multi-step workflow (design work, automation build, CAD, RAG pipeline, website work, or anything non-trivial you might want to repeat), even if the user does not say "capture" or "log". If the work has sequencing, corrections, or hard-won discoveries worth keeping, start a worklog. Also use on resume to read an existing worklog after a context reset.

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    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:

    If it exists, read it fully before doing anything.

    line 14
  2. Distinctive:

    If not, create the directory and a new WORKLOG.md with a one-line header naming the workflow and date.

    line 15
  3. Distinctive:

    Every entry carries exactly one tag:

    line 19
  4. Distinctive:

    Keep entries short. The lesson matters, not the prose.

    line 49
  5. Very specific:

    Before any compaction or /clear, write a CHECKPOINT entry: current state, open threads, next intended action.

    line 53

≈ “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 Capture

Maintain an append-only journal that survives compaction and /clear, capturing the signal (decisions, sequencing, corrections, dead ends) that should become a skill. Do not log keystrokes; the transcript already does that at the wrong altitude. Capture why, not just what.

At session start

  1. Determine the active workflow slug (kebab-case, e.g. figma-site-redesign).
  2. Look for _worklogs/YYYY-MM-DD-<slug>/WORKLOG.md.
    • If it exists, read it fully before doing anything. It is your memory.
    • If not, create the directory and a new WORKLOG.md with a one-line header naming the workflow and date.

Tag schema

Every entry carries exactly one tag:

  • DECISION: what was done and why -> a procedure step
  • SEQUENCE: X must precede Y -> ordered steps or preconditions
  • CORRECTION: user overrode you -> a hard rule
  • DEADEND: tried X, failed because Y -> a "do not do this" warning
  • CONVENTION: naming, structure, params, defaults -> reference material
  • DISCOVERY: tool quirk, API limit, gotcha -> environment notes
  • CHECKPOINT: state snapshot before clear or compaction -> resume anchor

Entry format

Append, never rewrite history.

## [YYYY-MM-DD HH:MM] TAG
One-line summary.
Optional result and fix or lesson.
Tags: comma, separated, keywords

When to append

Append an entry the moment one of these happens:

  • The user corrects or overrides something (CORRECTION).
  • An approach fails and you switch (DEADEND).
  • A non-obvious ordering constraint appears (SEQUENCE).
  • You set a reusable convention (CONVENTION).
  • A tool behaves unexpectedly (DISCOVERY).

Keep entries short. The lesson matters, not the prose.

Checkpoint and resume

Before any compaction or /clear, write a CHECKPOINT entry: current state, open threads, next intended action. On resume in a fresh window, read the worklog and continue from the last CHECKPOINT plus accumulated tags.

Why this matters

The context window is volatile and mostly noise. A durable tagged journal is the only thing that lets a workflow survive a context reset and later become a skill that makes the next run cheaper and more correct.

Download now (ZIP)

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. lombarddaniel14-coder/claude-skills★ 0same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repositoryOne other file it gives its agents.

Does it work?

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

Reviews can't be read right now.

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