day-next-plan

Carry unresolved items from a prior day into schedule, carry, or drop decisions.

39|5|Updated Oct 15, 2025
One-click install
npx skills add https://github.com/mpazik/Binder --skill day-next-plan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: day-next-plan
Source: https://github.com/mpazik/Binder/tree/main/examples/journal/skills/day-next-plan
Command: npx skills add https://github.com/mpazik/Binder --skill day-next-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents your next day from starting with a messy, uncertain backlog by carrying unfinished items forward with forced decisions.

Core Features & Use Cases

  • Carry-forward review: Reviews the source day’s unfinished items (anything not in achievements) and decides for each item whether to move it, schedule it later this week, or drop it.
  • Zombie-task enforcement: Flags tasks left unfinished for 3+ consecutive days and requires a commitment (schedule, carry with intent, or kill).
  • Week plan pull + add-ons: Pulls relevant items from the week plan that haven’t appeared on recent day plans, then collects additional appointments/errands/personal tasks.

Quick Start

Ask it to plan your target day using the carry-forward source day summary and your week context, resolving every unfinished and zombie task into a concrete decision.

Frequently Asked Questions about day-next-plan

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I carry forward unfinished tasks to the next day in a local journal workflow?

Carry forward unfinished tasks by reviewing prior day entries not listed in achievements, then resolving each item into schedule, carry, or drop decisions for the target day. This enforces task triage and updates rescheduled day entries in one coordinated workflow.

What is the best way to handle zombie tasks that remain unfinished for multiple days?

Zombie-task enforcement flags tasks left unfinished for three or more consecutive days, requiring an explicit commitment to schedule, carry with intent, or kill them. This prevents indefinite backlog accumulation in your daily planning workflow.

How do I pull unresolved week plan items into my daily planning routine?

Pull unresolved week plan items by cross-referencing the week context with recent day history. The workflow identifies relevant week plan entries that haven't appeared on recent day plans and collects them as add-ons alongside personal tasks and appointments.

Do I need binder-backed journal scripts to automate daily planning?

Yes, the workflow requires reading binder-backed day and week entries via journal scripts to access local-first day history and week context. This environment setup provides the data continuity needed for unresolved item resolution.

How does daily planning automation prevent a messy backlog from starting my next day?

Daily planning automation prevents a messy backlog by forcing decisions on every unfinished item from the source day. By resolving leftovers into concrete schedule, carry, or drop actions, the target day starts with a focused, actionable plan.

What are the limitations of using a local-first journal for task triage?

Local-first journal task triage depends entirely on reading existing binder-backed day and week entries. If prior day summaries or week context files are missing or unupdated, the carry-forward review and zombie-task enforcement cannot accurately resolve the backlog.