agentleFS
Sign inStart free
ozgurkarahanozgurkarahan/ai-agent-memory/.claude/skills/plan-week/SKILL.md

plan-week

Skill8 starsChanged 4 months agoMITView on GitHub

Plan the upcoming ISO week: resolve active week (TZ Europe/Paris), lift carry-over from prior week's 'Seed for W+1' block, aggregate open `- [ ]` todos from project + meeting pages, draft a Monday plan grouped by topic. Trigger: 'plan week', 'Monday plan', '/plan-week'.

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When the user says "plan week", "Monday plan", or "/plan-week":

    line 8
  2. Very specific:

    Update touches: [] frontmatter with topic slugs touched.

    line 19

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

Plan Week

When the user says "plan week", "Monday plan", or "/plan-week":

Resolve the memory root

Resolve WIKI_ROOT using memory/schema.md, then schema.md, then the pointer in AGENT.md. Stop with the missing path if none contains both schema.md and index.md. All paths below are relative to WIKI_ROOT.

  1. Resolve active ISO week (TZ Europe/Paris) → ops/weekly/2026-W{NN}.md. If missing, create the minimal weekly skeleton defined by the ingest skill.
  2. Lift carry-over from prior week's ### Seed for W{NN} block.
  3. Find open - [ ] todos recursively under wiki/, prioritizing pages updated in the last 14 days.
  4. Optionally use any connected work-data source available to the agent for the next 7 days of calendar, flagged mail, or open collaboration threads. Skip this step when no such tool is available.
  5. Draft ## 🎯 Monday plan grouped by ### [[topic]]. Show diff. User confirms.
  6. Update touches: [] frontmatter with topic slugs touched. Bump date_updated.

Anti-patterns:

  • ❌ Do not write to ops/activity.jsonl — planning ≠ work.
  • ❌ Do not auto-resolve todos.
  • ❌ Topics must be slugs in index.md — else group under ### unmapped.

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