agentleFS
Sign inStart free
kayamankayaman/skills/project-context-sync/SKILL.md

project-context-sync

Skill3 starsChanged 8 months agoCC0-1.0View on GitHub

Enforces updating a shared status file after each work session so that every agent and collaborator starts with accurate project state. Use when ending a session, completing a milestone, changing project phase, or before handing off to another agent or team member.

  • Reads credentials

The file

We split this skill into the rules it gives an agent

10 rules. About 0 are common, 8 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈8

    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:

    Keep a single source of truth for project status by updating a shared context file at the end of every work session.

    line 8
  2. Distinctive:

    After completing a milestone or deliverable

    line 13
  3. Distinctive:

    When a project changes phase (e.g.

    line 14
  4. Distinctive:

    Before handing off work to another agent or team member

    line 15
  5. Distinctive:

    After merging a significant PR or cutting a release

    line 16
  6. Distinctive:

    If a task references a plan or issue, link to it so the next session can pick up without searching.

    line 53
  7. Very specific:

    If a release was cut, include the version: v0.2.0 released — CI setup + README.

    line 63
  8. Distinctive:

    Do not update rows for projects that were not touched in the current session.

    line 67
  9. Very specific:

    Keep the status table in the same Markdown format so it can be parsed by scripts or other agents.

    line 71
  10. Distinctive:

    Before ending a session, verify:

    line 75

≈ “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

Project Context Sync

Keep a single source of truth for project status by updating a shared context file at the end of every work session.

When to Use

  • End of any work session (chat, coding, planning)
  • After completing a milestone or deliverable
  • When a project changes phase (e.g. Phase A to Phase B)
  • Before handing off work to another agent or team member
  • After merging a significant PR or cutting a release

Status File

Maintain a context/status.md (or equivalent) at the repository root with at minimum:

ColumnContent
ProjectName of the project or workstream
PhaseCurrent phase (e.g. Phase A, Phase B, GA)
Last MilestoneMost recent completed deliverable with version or PR reference
Next Steps1-3 concrete, actionable items (see rules below)

Include a Last updated line immediately below the table with the date and a brief label (e.g. YYYY-MM-DD (topic-label)).

Rules

1. Update on Every Session End

The status file MUST be updated at the end of every work session that touches any tracked project. Skipping an update means the next session starts with stale context.

2. Next Steps MUST Be Specific and Actionable

Each next step MUST describe a concrete action that someone can start immediately.

Good:

  • "Create Prisma migration for topics table with title, created_at, user_id columns"
  • "Configure OPENAI_API_KEY in repo secrets via setup-gh-secrets.sh"
  • "Write Post 1 draft covering gateway evaluation criteria"

Bad:

  • "Work on topics"
  • "Set up keys"
  • "Continue blog"

3. Link to Plan Files When In Progress

If a task references a plan or issue, link to it so the next session can pick up without searching.

| AI Gateway | Phase A | Evaluation in progress | [confirm-gateway-choice](path/to/plan-file.md): Complete evaluation |

4. Update Phase and Milestone Accurately

  • Increment the phase only when its exit criteria are met.
  • The milestone field reflects what was completed, not what is in progress.
  • If a release was cut, include the version: v0.2.0 released — CI setup + README.

5. Touch Only Projects You Changed

Do not update rows for projects that were not touched in the current session.

6. Preserve the Format

Keep the status table in the same Markdown format so it can be parsed by scripts or other agents. Do not add free-form prose above the table or between the table and the Last updated line.

Checklist

Before ending a session, verify:

  • Every project touched in this session has an updated row in the status table
  • Last Milestone reflects the most recent completed deliverable
  • Next Steps contains 1-3 specific, actionable items (not vague descriptions)
  • Plan links are included for any in-progress tracked work
  • Last updated date and label are current
  • No untouched projects were modified

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