agentleFS
eugenezhangco-speceugenezhangco-spec/athena/.claude/skills/eng-update/SKILL.md

update

Skill0 starsChanged 7 months agoMITView on GitHub

Save all session decisions, conclusions, and context to memory and STATUS.md so the team stays current across instances. Use when you say /update, "save this", "update yourselves", or at the end of any significant session.

65 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use end, create and 9 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.
  • torarnvSkill

    end

    Wrap up a work session. Updates memory files, logs decisions and lessons, appends to the session log.

    Also in 3 projects that use this

  • MicrosoftSkill

    create

    Also in 4 projects that use this

  • bitwize-music-studioSkill

    tutorial

    Provides interactive guided album creation for new users. Use when the user is new to the plugin or asks for a walkthrough of the album creation process.

    Also in 3 projects that use this

  • MicrosoftSkill

    note

    Use this skill to record progress, partial findings, hypotheses, and page-anchored evidence while investigating a long document. Call Note aggressively — any time you read a page and confirm, narrow, or update your understanding of the user's question. Triggers include "jot that down", "save this finding", "note that page 7 says X", or (more often) implicit internal signals — you just learned something and want it recoverable later. Notes persist in the session and Review can select among them. Never paraphrase notes back from memory; write them as you go.

    Also in 4 projects that use this

  • kv0906Skill

    inbox

    Quick capture mode (with content) or batch processing mode (no content). GTD-style routing of inbox items to proper folders. Use "/inbox thought to capture" or "/inbox" to process.

    Also in 4 projects that use this

  • jholhewresSkill

    backup

    Backup and restore — files, databases, and system backups

    Also in 3 projects that use this

  • +2 more from microsoft

The file

Show its rules and text

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 63 edited versions we read keep these.

  • 12

    Distinctive

    This author's own choices. Worth a look.

  • 6

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When this skill is triggered, perform ALL of the following steps:

    line 9
  2. Distinctive:

    Read the current content

    line 25
  3. Distinctive:

    Update with new information from this session

    line 26
  4. Distinctive:

    If a new memory is needed (new topic not covered by existing files), create it

    line 27
  5. Distinctive:

    Update MEMORY.md index if new files were created

    line 28
  6. Very specific:

    Read context/ACTION-ITEMS.md and perform ALL of the following:

    line 39
  7. Distinctive:

    Follow-ups from code review or testing

    line 48
  8. Distinctive:

    medium: Should be done but not urgent

    line 65
  9. Very specific:

    Update the Updated date on any item that was discussed or modified

    line 71
  10. Very specific:

    If an item is now blocked, move to "Blocked" and fill in Blocked by

    line 72
  11. Distinctive:

    Check for duplicate or overlapping items.

    line 80
  12. Very specific:

    Read context/STATUS.md and update:

    line 84
  13. Distinctive:

    Add any new sections needed

    line 90
  14. Very specific:

    Check context/inbox/ for unprocessed files.

    line 94
  15. Distinctive:

    Read and analyze each file

    line 95
  16. Distinctive:

    Update STATUS.md with new information

    line 98
  17. Very specific:

    If significant decisions were made this session, create or update files in context/decisions/ with:

    line 103
  18. Distinctive:

    After updating, provide a brief summary:

    line 112

“Common” is measured: kept by at least 6 in 10 of the 63 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

/update — Team State Sync

When this skill is triggered, perform ALL of the following steps:

Step 1: Review the conversation

Scan the current conversation for:

  • Decisions made (technical, architectural, scope, business)
  • New context learned (from documents, verbal context, or Q&A)
  • Action items identified (including casual mentions like "we should also fix X", "don't forget to Y", "we'll need to Z eventually")
  • User's knowledge growth (new concepts now understood)
  • Open questions that still need answers
  • Changes to project direction or priorities
  • Completed work that may resolve existing action items

Step 2: Update memory files

For each relevant memory file in the memory directory:

  • Read the current content
  • Update with new information from this session
  • If a new memory is needed (new topic not covered by existing files), create it
  • Update MEMORY.md index if new files were created

Memory types to check:

  • user_[name]_profile.md — Did the user demonstrate new knowledge or preferences?
  • project_[name]_status.md — Did the project status, phase, or timeline change?
  • project_[stakeholder]_context.md — Did we learn anything new about a key stakeholder or their expectations?
  • project_technical_decisions_[phase].md — Were any technical decisions made or refined?
  • feedback_*.md — Did the user give any feedback on how the team should operate?

Step 3: Update ACTION-ITEMS.md

Read context/ACTION-ITEMS.md and perform ALL of the following:

3a: Capture new action items

Scan the conversation for anything that implies work to be done. This includes:

  • Explicit requests ("we need to build X")
  • Casual mentions ("we should also fix Y", "don't forget Z", "eventually we'll want W")
  • Open questions that need follow-up ("need to check with [person] about X")
  • Bugs discovered during the session
  • Technical debt identified
  • Follow-ups from code review or testing

For each new item, assign the next available ID from the next_id counter, increment the counter, and add it to the Open section using the standard format:

### [AI-NNN] Title
- **Status:** open
- **Priority:** critical | high | medium | low
- **Category:** feature | bug | debt | ops | research | docs
- **Source:** [Session date, inbox file name, verbal context, plan file, casual mention, etc.]
- **Created:** YYYY-MM-DD
- **Updated:** YYYY-MM-DD
- **Notes:** [Context about what this is and why it matters]

Priority guidelines:

  • critical: Blocks other work or affects production
  • high: Important for current phase, should be done soon
  • medium: Should be done but not urgent
  • low: Nice to have, do when convenient

3b: Update existing items

  • Move items that were worked on this session to "In Progress" (or "Done" if completed)
  • For completed items: set Status: done, add Completed: YYYY-MM-DD, move to "Done (Recent)"
  • Update the Updated date on any item that was discussed or modified
  • If an item is now blocked, move to "Blocked" and fill in Blocked by

3c: Staleness check

  • Flag any open items with Updated date older than 30 days → move to "Stale Review Queue"
  • Trim "Done (Recent)" — move items completed more than 3 sessions ago to "Archive"
  • Prune Archive items older than 90 days (unless they have historical significance noted)

3d: Deduplication

  • Check for duplicate or overlapping items. If found, merge them (keep the lower ID, note the merge)

Step 4: Update STATUS.md

Read context/STATUS.md and update:

  • Last updated date
  • Current Status section if phase or timeline changed
  • App Build Status table if any development work was done
  • Engineering Team Decisions section if new decisions were made
  • What's Coming Next section if priorities shifted
  • Add any new sections needed

Step 5: Process inbox (if applicable)

Check context/inbox/ for unprocessed files. If any exist:

  • Read and analyze each file
  • Brief on contents
  • Move to appropriate folder (requirements/, communications/, archive/*, etc.)
  • Update STATUS.md with new information
  • Extract any action items and add to ACTION-ITEMS.md (per Step 3a)

Step 6: Log decisions

If significant decisions were made this session, create or update files in context/decisions/ with:

  • The decision
  • Why it was made
  • Who was involved
  • Date
  • Impact on the build

Step 7: Confirm

After updating, provide a brief summary:

  • What was saved/updated
  • Action items: N new, N updated, N completed, N total open
  • Any open items that need attention next session
  • Current project state in one sentence

When to trigger automatically

This skill should also run automatically (without being asked) when:

  • A significant decision point is reached
  • New context from inbox has been processed
  • A build phase or milestone is completed
  • The session is clearly winding down
  • User says anything like "save this", "remember this", "update yourselves", "don't forget"

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.