agentleFS
aidvggaidvgg/operator-os/.claude/skills/daily-log/SKILL.md

daily-log

Skill4 starsChanged 11 days agoMITView on GitHub

Discover and run the canonical daily-log workflow for Claude Code. Trigger when the user says: plan my day; plan the day; let's plan my day; let's plan the day; daily plan; daily planning; /standup; standup; daily standup; /eod; eod; log my day; end of day; close the day; /weekly; weekly review; weekly retro.

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 3

    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 the canonical daily-log skill before responding.

    line 27
  2. Distinctive:

    Read the live ledger, carry-over, owner files, working-tree evidence, and horizon output required by that skill before asking for generic …

    line 28
  3. Distinctive:

    Never invent tasks. The plan may contain only Sam-stated tasks, carried work, and standing declared contracts.

    line 30

“Common” is measured: kept by at least 6 in 10 of the 4 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
<!-- GENERATED by scripts/sync-agent-adapters from ai/AGENT_ROUTES.json. DO NOT EDIT. -->

daily-log discovery adapter

From the repository root, read ai/AGENT_ROUTES.json and skills/daily-log/SKILL.md in full. Determine the matching mode from the registry, then execute the canonical skill exactly.

This adapter owns no workflow policy. Do not restate, shorten, or improvise the canonical procedure. The routing projection below is generated from structured action ids in the registry.

Generated routing projection

daily-log

Canonical workflow: skills/daily-log/SKILL.md.

/plan

Aliases: plan my day, plan the day, let's plan my day, let's plan the day, daily plan, daily planning.

Platform exception: Claude Code owns /plan as its built-in plan-mode command. Use a natural-language planning alias for the daily log.

First-turn contract for /plan only:

  • Read the canonical daily-log skill before responding.
  • Read the live ledger, carry-over, owner files, working-tree evidence, and horizon output required by that skill before asking for generic intake.
  • Surface known commitments and conflicts first, then ask only for missing day-specific tasks or hard stops.
  • Never invent tasks. The plan may contain only Sam-stated tasks, carried work, and standing declared contracts.

Capability fallbacks for /plan only:

  • Without calendar read access, ask Sam for fixed events after loading repository context, then continue planning.
  • Without calendar write access, continue planning and state that no calendar blocks were synced. Never invent event IDs.
  • Without repository write access, produce the exact plan draft and state that it was not logged.

/standup

Aliases: /standup, standup, daily standup.

Capability fallbacks for /standup only:

  • Without calendar read access, omit the optional next calendar item and continue the repository-backed standup.

/eod

Aliases: /eod, eod, log my day, end of day, close the day.

Capability fallbacks for /eod only:

  • Without repository write access, produce the exact end-of-day update and accountability diff, state that it was not logged, and do not claim files changed.

/weekly

Aliases: /weekly, weekly review, weekly retro.

Capability fallbacks for /weekly only:

  • Without repository write access, produce the exact weekly review draft, state that it was not logged, and do not claim files changed.

On a semantic match, read the canonical workflow before responding and execute only the matched mode. Do not substitute a generic intake checklist or borrow another mode's first-turn behavior.

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.

Reviews can't be read right now.

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.