agentleFS
worldbankworldbank/geoPovLearn/.claude/skills/working-on/SKILL.md

working-on

Skill2 starsChanged 6 months agoMITView on GitHub

Set a tracking document as the source of truth for the current feature or task. Use when starting work on a feature, bug fix, or multi-step task that benefits from a persistent record of decisions, discoveries, and progress. Keeps the document updated as work proceeds.

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 6 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If in doubt, update the document.

    line 31
  2. Distinctive:

    Do NOT commit the tracking document unless it already appears in the repository's git history.

    line 35
  3. Distinctive:

    Keep updates concise — bullet points and short paragraphs are preferred over prose

    line 39
  4. Distinctive:

    Use timestamps or date headers when the document spans multiple sessions

    line 40
  5. Distinctive:

    When a section becomes stale or irrelevant, move it to an "Archive" or "Resolved" section rather than deleting it

    line 42
  6. Distinctive:

    If the document doesn't exist yet, create it with a sensible structure based on the task at hand

    line 43

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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

Working On

You are managing a tracking document that serves as the source of truth for the current task or feature.

The tracking document is: $path

Behavior

Once activated, treat the tracking document as a living record. Update it after:

  • Any decision is made (architectural, design, scope, naming, etc.)
  • A new problem, bug, or edge case is discovered
  • A new sub-feature or requirement emerges
  • An issue is raised or resolved
  • Any significant implementation work is completed
  • A key part of a conversation with the user that would be useful to recall later
  • Any time you commit files — a commit is a strong signal that the tracking document should also be reviewed and updated

If in doubt, update the document. It is better to over-document than to lose context.

Git Handling

Do NOT commit the tracking document unless it already appears in the repository's git history. If the file is not tracked by git, leave it out of any commits.

Guidelines

  • Keep updates concise — bullet points and short paragraphs are preferred over prose
  • Use timestamps or date headers when the document spans multiple sessions
  • Record the why behind decisions, not just the what
  • When a section becomes stale or irrelevant, move it to an "Archive" or "Resolved" section rather than deleting it
  • If the document doesn't exist yet, create it with a sensible structure based on the task at hand

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.