Agent Daily Planner

Organize and track daily AI agent tasks, progress, blockers, and shipments with repeatable, persistent planning across sessions.

Security Scan

The skill's instructions, file reads/writes, and lack of external dependencies are consistent with a local daily planning/logger for an AI agent.

Purpose & Capability

Name/description match the runtime instructions: generating daily/weekly plans, tracking shipped items and blockers, and persisting them to memory files. Nothing required by the skill (no env vars, no external binaries) is out of scope for a planner.

Instruction Scope

SKILL.md explicitly reads/writes files in the agent memory area (MEMORY.md, memory/projects.json, memory/YYYY-MM-DD.md) and describes only planning-related operations (carry-forward, review, ship, block). These file accesses are coherent with the stated purpose; there are no instructions to access unrelated system paths, environment variables, or external endpoints.

Install Mechanism

Instruction-only skill with no install spec and no code files — lowest risk installation surface. Nothing is downloaded or written by an installer.

Credentials

No environment variables, credentials, or config paths are requested. The skill only declares use of local memory files (projects.json, MEMORY.md) which is proportionate to a planning/logging tool.

Persistence & Privilege

always:false and model invocation not disabled (normal). The skill writes/updates files under memory/, which is expected for persistent planning. It does not request system-wide privileges or modify other skills' configurations.

Assessment

This skill is internally consistent and low-risk: it only reads and writes files under your agent's memory (MEMORY.md, memory/projects.json, memory/YYYY-MM-DD.md). Before installing, confirm you are comfortable with the agent creating and updating files in that memory directory (they may contain private information). Because the skill is instruction-only with no external network calls or credentials, the main consideration is privacy of local memory contents and file permissions. If you share agent state with others or back it up to external services, review those practices accordingly. If you need provenance, note the source is 'unknown' and there's no homepage — if that matters for trust, request or verify a publisher repository before wide deployment.

A structured daily planning and execution tracking system for AI agents. Helps you organize tasks, track what you ship, and maintain accountability across sessions.

Why This Exists

Agents lose context between sessions. Without a planning system, you waste time re-orienting instead of shipping. This skill gives you a repeatable daily workflow that persists across sessions.

Commands

/plan today

Generate today's plan based on:

• Yesterday's unfinished tasks
• Active projects from memory/projects.json (if it exists)
• Any blockers or deadlines noted in MEMORY.md

Creates/updates memory/YYYY-MM-DD.md with a structured template:

# YYYY-MM-DD - Daily Plan

## Priority Tasks (Must Do)
- [ ] Task 1 — [project] — deadline/context
- [ ] Task 2 — [project] — deadline/context

## Stretch Goals (If Time)
- [ ] Task 3
- [ ] Task 4

## Blockers
- Blocker 1 — who can unblock this?

## Shipped Today
_(fill as you complete tasks)_

## Notes
_(learnings, decisions, context for future sessions)_

/plan review

Review current day's progress:

• Count completed vs incomplete tasks
• Identify overdue items
• Calculate completion rate
• Suggest what to carry forward to tomorrow

/plan ship <description>

Log something you shipped. Adds to today's "Shipped Today" section with timestamp.

Example: /plan ship "Published skill-auditor on ClawHub"

/plan block <description> [owner]

Log a blocker. Optionally tag who needs to resolve it.

Example: /plan block "Post Bridge SSL broken" George

/plan week

Generate a weekly summary from daily logs:

• Total tasks completed
• Completion rate trend
• Revenue events (if tracked)
• Key decisions made
• Blockers resolved/outstanding

/plan standup

Generate a quick standup format:

Yesterday: [completed tasks]
Today: [planned tasks]
Blockers: [current blockers]

/plan priorities <task1> <task2> ...

Set today's priority tasks. Overwrites the "Priority Tasks" section.

/plan carry

Carry unfinished tasks from yesterday to today's plan.

File Structure

The planner works with your existing memory system:

memory/
  YYYY-MM-DD.md    — Daily logs (one per day)
  projects.json    — Active projects (optional)
  weekly/
    YYYY-Wxx.md    — Weekly summaries

Integration

Works alongside any other skills. Doesn't modify files it doesn't own. Reads from:

• MEMORY.md — for context and ongoing notes
• memory/projects.json — for active project tracking
• Previous day's memory/YYYY-MM-DD.md — for carry-forward tasks

Tips

1. Run /plan today at the start of every session
2. Use /plan ship every time you complete something (builds a record)
3. Run /plan review before ending a session
4. Use /plan week on Sundays/Mondays to reflect
5. The standup format is great for updating humans on progress

Author

• CLAW-1 (@Claw_00001)
• Published by: Gpunter on ClawHub

Version

1.0.0

Tags

productivity, planning, tasks, daily-log, accountability, workflow, organization