agentleFS
rakaarwakyrakaarwaky/agents-arwaky/skills/productivity/weekly-review-planning/SKILL.md

weekly-review-planning

Skill0 starsChanged 7 days agoMITView on GitHub

Weekly reset: commitments, stalled work, next-week plan. Use when running a weekly review of completed work and commitments, finding stalled projects and waiting items, or planning next week across calendar, tasks, and notes.

11 other projects use a version of this, 10 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use github.

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.
  • NVIDIASkill

    github

    Interact with GitHub using the gh CLI restricted to REST API only (no GraphQL). Use when the user wants to work with GitHub issues, pull requests, repos, releases, or Actions — especially in sandboxed environments where the GraphQL endpoint may be blocked. Trigger keywords - github, gh, pull request, PR, github issue, github actions, workflow, release, gh api.

    Also in 5 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 11 edited versions we read keep these.

  • 2

    Distinctive

    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. Very specific:

    Run a bounded weekly reset across the user's chosen systems.

    line 18
  2. Distinctive:

    Default to drafts and recommendations, not mutations: No task, event, or note is changed without explicit approval in step 7.

    line 22
  3. Distinctive:

    Capacity comes from the calendar, not the task list: Before proposing next week's plan, estimate fixed calendar load first.

    line 24

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

Weekly Review and Planning

Run a bounded weekly reset across the user's chosen systems. This is a concrete recurring task, not a generic productivity methodology — the weekly-review Automation Blueprint schedules it as a cron job.

Global rules

  • Default to drafts and recommendations, not mutations. No task, event, or note is changed without explicit approval in step 7.
  • Silence from others is not completion. A waiting item without a reply stays open; do not infer closure.
  • Capacity comes from the calendar, not the task list. Before proposing next week's plan, estimate fixed calendar load first.
  • The review covers both the completed week and the planning horizon. Gaps in coverage are stated explicitly in section 7 of the report.
  • Every stalled flag must trace to a record. Vague "feels stalled" is not a valid flag; name the record, event, or thread.

Routing

StepReferencePurpose
Review steps 1–7: systems, calendar, inboxes, projects, waiting, plan, applyreferences/review-steps.mdThe seven-step procedure with "Done when" criteria and pitfalls.
Report output shapereferences/output-shape.mdThe seven-section report structure and section-level rules.

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.