agentleFS
Sign inStart free
nuffinnuffin/hermes-task-framework/skills/task-aware-project-work/SKILL.md

task-aware-project-work

Skill2 starsChanged 45 days agoMITView on GitHub

Load canonical root and subsystem task context before continuing project work.

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 4 are distinctive, and 2 are 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.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use when continuing a task by name/hash, returning to project work tied to a task, or before creating project artifacts that may already …

    line 24
  2. Very specific:

    Read TASK.md, root MEMORY.md, and recent root CHANGELOG.md.

    line 29
  3. Very specific:

    If a hierarchical subsystem is missing, load compact-directory-memory and create the complete pair before source changes.

    line 33
  4. Distinctive:

    Never start implementation before loading task context.

    line 40
  5. Distinctive:

    Search actual repositories before concluding an artifact was deleted.

    line 41
  6. Distinctive:

    Do not duplicate a project or subsystem because another session used a different path.

    line 42

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

Task-Aware Project Work

Use when continuing a task by name/hash, returning to project work tied to a task, or before creating project artifacts that may already exist.

Protocol

  1. Resolve the task with task_api.py describe <identifier>.
  2. Read TASK.md, root MEMORY.md, and recent root CHANGELOG.md.
  3. Detect .hermes-task.json.memory_layout or memories/.
  4. Identify the target subsystem and read its full MEMORY plus recent CHANGELOG.
  5. Resolve project/repository paths from task context and verify existing artifacts before creating anything.
  6. If a hierarchical subsystem is missing, load compact-directory-memory and create the complete pair before source changes.

Legacy TASK_MEMORY.md is not canonical. Use it only as archaeological evidence when canonical files are absent.

Pitfalls

  • A ticket is not a task-framework task.
  • Never start implementation before loading task context.
  • Search actual repositories before concluding an artifact was deleted.
  • Do not duplicate a project or subsystem because another session used a different path.

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