agentleFS
iwe-orgiwe-org/dev-workspace/.claude/skills/weekly/SKILL.md

weekly

Skill11 starsChanged 2 days agoMITView on GitHub

Compose a weekly project digest from the workspace — what shipped, active plans and their staleness, open and recurring bugs, top backlog, new learnings, and graph health, ending with the single most leveraged next action. Read-only; prints without writing files. Use when the user asks for a "weekly digest", "status report", or a start-of-week review.

18 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use capture, decide and 2 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.
  • toneron2Skill

    capture

    Capture thoughts to inbox with automatic classification

    Also in 4 projects that use this

  • dirienSkill

    decide

    Three-agent adversarial debate protocol for strategic decisions. Two advocates steelman opposing positions while a moderator identifies risks and synthesizes a binding consensus. Use when choosing between alternatives, evaluating tradeoffs, or making high-stakes decisions.

    Also in 3 projects that use this

  • SentrySkill

    onboard

    Onboard a service to sentry-options. Use when integrating a new service, creating schemas, or setting up the multi-repo sentry-options workflow.

    Also in 3 projects that use this

  • SentrySkill

    review

    Fixture review skill.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 16 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read-only: this skill writes no files and changes no statuses.

    line 45
  2. Distinctive:

    Every number in the digest traces to a query, or to git where the workspace has it — no estimates.

    line 48

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

A read-only sweep of the graph that answers: what moved, what's stuck, what's next. Numbers come from frontmatter, and from git when the workspace is a git repository (git rev-parse --is-inside-work-tree) — never from memory.

Steps

  1. Shipped. Plans and bugs completed in the last 7 days: iwe find --filter '{type: {$in: [plan, bug]}, stage: done, completed: {$gte: <YYYY-MM-DD, 7 days ago>}}' --project completed. Releases cut: iwe find --filter '{type: release, date: {$gte: <YYYY-MM-DD, 7 days ago>}}' --project version,date. In a git repository, cross-check with git log --since '7 days ago' --oneline.
  2. In flight. Active plans (no stage, or approved) under ## Active in data/plans.md; flag any untouched for 14+ days as possibly stalled or silently done. Last touched is the last commit on the file (git log -1 --format=%cs -- data/plans/<key>.md) in a git repository, and otherwise the plan's generated.at, or the file's modification date when that is missing.
  3. Open bugs. Tickets under ## Open in data/bugs.md, split by reported_by (user-reported first), plus any with two or more affected_versions — those came back after a fix.
  4. Backlog head. ## High items in data/backlog.md, plus how long they've sat (created).
  5. Learnings. Learnings dated this week, one line each: iwe find --filter '{type: learning, created: {$gte: <YYYY-MM-DD, 7 days ago>}}' --project created.
  6. Graph health. iwe schema validate (report violations) and iwe stats. iwe stats prints a ## Broken Links section and a ## Orphans section only when there is something to list. Healthy means no violations, no ## Broken Links section, and no data/ document under ## Orphans: every document under data/ is reachable from a hub, the hubs from data/index.md, and data/index.md and data/log.md from the start page.
  7. Print the digest — shipped / in flight / bugs / backlog / learnings / health — and end with the single most leveraged next action, chosen from what the sweep showed, with a one-line justification.

Rules

  • Read-only: this skill writes no files and changes no statuses; if the sweep finds inconsistencies (a done plan still under Active, a fixed bug still under Open), report them as the next action instead of fixing silently.
  • Every number in the digest traces to a query, or to git where the workspace has it — no estimates.

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.