CommunityProductivity & Collaborationgithub.com

BattlePlan

Daily execution plan from a task tracker (local CSV, Excel workbook, or Google Sheet). Groups open tasks by context and sub-context, estimates time, finds parallel threads, and writes ready-to-paste starting prompts per thread. Starts from yesterday instead of from zero — recaps the previous day's agent sessions and git commits, pre-fills the audit, and offers resume commands. Includes an end-of-day handoff (--close), an unattended morning draft (--draft), and task management (add, done, cancel, restore, sweep, batch import). USE WHEN plan my day, daily plan, battle plan, what should I work on, close the day, end of day handoff, morning draft, task overview, standup prep, prioritize tasks, add a task, mark task done, set up battleplan, configure task tracker.

What is BattlePlan?

BattlePlan is a Claude Code agent skill that daily execution plan from a task tracker (local CSV, Excel workbook, or Google Sheet). Groups open tasks by context and sub-context, estimates time, finds parallel threads, and writes ready-to-paste starting prompts per thread. Starts from yesterday instead of from zero — recaps the previous day's agent sessions and git commits, pre-fills the audit, and offers resume commands. Includes an end-of-day handoff (--close), an unattended morning draft (--draft), and task management (add, done, cancel, restore, sweep, batch import). USE WHEN plan my day, daily plan, battle plan, what should I work on, close the day, end of day handoff, morning draft, task overview, standup prep, prioritize tasks, add a task, mark task done, set up battleplan, configure task tracker.

Works with✓Claude Code~Codex CLI~Cursor
npx skills add https://github.com/juanmherrerav/agent-workday-skills/tree/main/skills/BattlePlan

Installed? Explore more Productivity & Collaboration skills: steipete/gemini, steipete/gh-issues, steipete/skill-creator · View all 6 →

Ask in your favorite AI

Open a new chat with this agent skill pre-loaded.

Documentation

What does BattlePlan do?

Reads every open task from a tracker, reconciles it with what actually happened since the last plan, and turns it into a short list of parallel work threads, each with a starting prompt a fresh agent session can pick up cold.

Step 0 — every invocation starts here

BP="${SKILLS_HOME:-$HOME/.claude/skills}/BattlePlan/Tools"
uv run --script "$BP/setup_tracker.py" check
  • success: false or no config → run Workflows/Setup.md first. Never invent a tracker, a tab name or a context.
  • Config lives at $BATTLEPLAN_CONFIG, else ${AGENT_SKILLS_CONFIG:-~/.config/agent-skills}/BattlePlan/config.json. It holds the owner, the tracker backend, the plans directory and the context hierarchy. The skill directory never holds personal data, so it can be shared and updated freely.

Routing

InvocationWorkflow
"set up battleplan", no config, new tracker, new contextWorkflows/Setup.md
/BattlePlan [context] [--mine] [--skip-audit] [--launch], --auditWorkflows/Plan.md
/BattlePlan --closeWorkflows/Close.md
/BattlePlan --draft (unattended), scheduling the draftWorkflows/Draft.md
--add, --done, --cancel, --restore, --sweep, batch-add, importing tasks from tickets or meetingsWorkflows/Tasks.md

The day loop

 evening                     scheduled (weekdays)          morning
 /BattlePlan --close  ──▶   /BattlePlan --draft   ──▶   /BattlePlan
 done, next step per        reads tracker + handoff +    opens the draft; you only
 thread, resume commands    sessions; writes a draft     confirm exceptions, then go

Each step works when the one before it was skipped: no handoff → the recap falls back to the previous workday; no draft → /BattlePlan builds the plan live. Files live in plans_dir:

FileWritten byHolds
YYYY-MM-DD-handoff-<host>.md--closeFirst line Closed: <ISO 8601 with offset> on <host>, then done, in flight (next step + resume command), carry-overs
YYYY-MM-DD-draft-<host>.md--draftPlan plus pre-filled audit proposals; nothing written to the tracker
YYYY-MM-DD-plan.md/BattlePlanThe confirmed plan, so --close can compare plan with reality

<host> is an alias (mac, wsl, linux or $BATTLEPLAN_HOST_ALIAS), never the hostname, because these files may be shared across machines. Session IDs resume only on the machine that created them: show other hosts' next steps, never their resume commands.

Multi-machine: set plans_git_sync: true and put plans_dir inside a git repo. Commits touch only the file just written (git commit -- <path>) after fetch + merge --ff-only. Never stash, reset or clean: other sessions may hold uncommitted work in that repo. If the fast-forward fails, commit locally and say the push is pending.

Tools

ScriptDoes
setup_tracker.py check|initValidate the config and backend; init creates missing tabs with headers (idempotent)
pull_tasks.py [context] [--mine]Open tasks as JSON with computed urgency, deadlines, owner kind, dependencies, tickets
recap_sessions.py --tasks pull.json [--since auto] [--context X]Agent sessions + git commits since the last handoff, linked to tasks by ticket ID
manage_tasks.py add|batch-add|mark-done|mark-cancelled|batch-done|restore|sweep|list-tabsEvery tracker write; JSON out, --dry-run everywhere it writes
run_draft.sh --install|--check|--force|--uninstallSchedules the unattended morning draft (launchd / systemd user timer)
tracker.pyStorage backends (csv, xlsx, gsheets) and config loading; imported by the others

All scripts are uv run --script files with inline dependencies (PEP 723): no virtualenv to manage. Tests: uv run --with pytest --with openpyxl pytest tests/.

Non-negotiables

  • The recap proposes, the human confirms. Nothing is marked done from evidence alone.
  • Exact row references for writes. After a pull, archive with Tab!row refs in one batch-done call; never fall back to substring search when the row is known.
  • Confidential contexts ("confidential": true) get ticket IDs and short generic summaries only, in the tracker and in handoffs. manage_tasks.py rejects IPs, URLs and the context's forbidden_patterns.
  • Never launch threads without explicit confirmation.
  • Tracker commands run sequentially — Google Sheets allows ~60 reads/minute and each command reads every tab.

Dependencies

uv (brew install uv, or curl -LsSf https://astral.sh/uv/install.sh | sh). git for the recap's commit scan. Google Sheets backend only: a service-account JSON key with editor access to the sheet. Session recap reads Claude Code transcripts (~/.claude*/projects); with other agents it reports git activity and handoffs only.

Individual skills in this repo

This repo contains 2 individual skills — each has its own dedicated page.

CodeQuality

Code quality loop for any repo, seen through two lenses — a tool lens (linters, type checkers, security, dead-code and duplication scanners; fix by P0 security → P1 correctness → P2 maintainability) and a principle lens (SOLID + Clean Code smells; one principle at a time, propose → confirm → apply behind characterization tests). One manifest of free local tools, one scan, one fix loop, one mandatory Quality Improvement Report. USE WHEN improve code quality, analyze code, fix linting, reduce duplication, add types, security scan, test coverage, refactor, improve code design, apply SOLID, clean code refactor, reduce complexity, kill code smells, make code maintainable, refactor legacy code, single responsibility, dependency inversion, remediation sprint, install quality tools, quality baseline, smell report, refactoring roadmap, what should we fix first. NOT FOR the issue lifecycle, branches, PRs or merging (use IssueFlow; its Remediation workflow calls this skill to pick and scope the w

MeetingAnalysis

Turn meetings into structured summaries and tracked action items. Transcribes recordings locally (faster-whisper on CUDA, Apple Silicon or CPU), imports Google Meet / Gemini notes through connectors, or takes pasted notetaker transcripts; writes a summary with decisions and an action table; pushes only your own items to the BattlePlan tracker. Includes an unattended inbox ingest (drop a recording, get a summary) and a hard rule that recordings never land in a git repo. USE WHEN analyze meeting, meeting summary, transcribe meeting, transcribe recording, summarize this call, what happened in the meeting, import meeting notes, Gemini notes, Google Meet notes, import meetings to tracker, auto ingest meetings, meeting inbox, process recordings folder, set up meeting analysis.

Related Skills