agentleFS
MarcusJellinghausMarcusJellinghaus/mcp-tools-py/.claude/skills/plan_update/SKILL.md

plan_update

Skill21 starsChanged 3 months agoMITView on GitHub

Update implementation plan files based on discussion

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Update the implementation plan files in pr_info/steps based on our discussion.

    line 12
  2. Very specific:

    Update the plan by modifying the different files in folder pr_info/steps Please do targeted changes.

    line 16
  3. Distinctive:

    Only put those decisions that we discussed, no invented decisions.

    line 20
  4. Distinctive:

    Ensure consistency across all step files

    line 26
  5. Distinctive:

    Update the summary if scope changes

    line 27

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

Update Plan Files

Update the implementation plan files in pr_info/steps based on our discussion.

Instructions

Update the plan by modifying the different files in folder pr_info/steps Please do targeted changes.

Please log the decisions from our discussion in pr_info/steps/Decisions.md. Only put those decisions that we discussed, no invented decisions. (For each decision that you log, consider whether you discussed it with me and when I said so)

Guidelines:

  • Make minimal, focused changes
  • Preserve existing structure where possible
  • Ensure consistency across all step files
  • Update the summary if scope changes

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.