agentleFS
SchepetkovSchepetkov/claude-skills-game-UE/skills/agent-workflow/SKILL.md

agent-workflow

Skill2 starsChanged 17 days agoLicence not identifiedView on GitHub

Working discipline for a coding agent on a long project with a human author — the retro after every significant task (rounds of corrections, causes, and the skill/rule/hook/tool change that prevents them), the task journal (scripts/journal.py, sqlite) with rounds-per-area statistics, Claude Code auto-memory hygiene (small index, expiring state notes, lessons promoted into skills, claims checked against git), speaking up about broken process, independent review by a second model, and measured skill optimization. Use when a significant task is finished or accepted, when the human sent work back more than once, when memory or CLAUDE.md feels stale or contradictory, before committing to a spec or architecture, or when asked "why does this keep happening / how do we work faster".

20 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use agent-agent, agent-analyze-code-quality and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 16 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

The licence could not be identified — read it at the source. We count its rules but don't quote them. Read them on GitHub.

“Common” is measured: kept by at least 6 in 10 of the 16 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

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.