planner

Decompose goals into executable tasks and write them to ~/.claude/tasks.json.

Updated Apr 19, 2026
One-click install
npx skills add https://github.com/mgsystemsdev/POD --skill planner-mgsystemsdev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: planner
Source: https://github.com/mgsystemsdev/POD/tree/main/agent-system-base/.claude/skills/planner
Command: npx skills add https://github.com/mgsystemsdev/POD --skill planner-mgsystemsdev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill converts vague goals into concrete, executable tasks and records them in ~/.claude/tasks.json, enabling planning without immediate execution and easy hand-off to cron-driven workers.

Core Features & Use Cases

  • Decompose goals into 5–12 concrete, checkable tasks that fit within a single session.
  • Assign an action_type (claude_execute or log_only) to each task and generate a self-contained prompt when needed.
  • Append plans to ~/.claude/tasks.json with plan-YYYYMMDD-NNN IDs, preserving existing tasks.
  • Trigger on natural language prompts like plan this out, break this down, or schedule this work for later, including long-running or multi-session goals.
  • Use to schedule work for cron-based execution or to organize work that spans multiple sessions.

Quick Start

Ask Planner to decompose your goal into an executable task list and save it to ~/.claude/tasks.json for later execution.

Frequently Asked Questions about planner

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

FAQPage Schema
How do I break down a goal into actionable tasks for cron-based execution?▼

You can schedule work for cron-based execution by decomposing your goal into 5–12 concrete tasks and appending them to ~/.claude/tasks.json. The planner assigns plan-YYYYMMDD-NNN IDs to enable multi-session workers.

What is task decomposition and how does it work for multi-session planning?▼

Task decomposition splits a goal into 5–12 concrete, checkable tasks written to ~/.claude/tasks.json with plan-YYYYMMDD-NNN IDs. It operates in planning mode, presenting the plan for approval before any execution begins.

How do I append new task plans to an existing tasks.json file?▼

The system reads your existing ~/.claude/tasks.json and appends new plan entries with unique plan-YYYYMMDD-NNN IDs. This preserves existing tasks while adding newly decomposed items for scheduling.

Can I use natural language to schedule work for later execution?▼

Yes, you can trigger planning using natural language prompts like plan this out, break this down, or schedule this work for later. The system then generates a self-contained prompt for each claude_execute task.

Does planning mode support claude_execute and log_only task types?▼

Yes, planning mode assigns an action_type of either claude_execute or log_only to each decomposed task. It enforces a deterministic task schema and a single, self-contained prompt for every execute task.

What are the limitations of planning mode for long-running goals?▼

Planning mode is limited to decomposing goals into 5–12 concrete tasks that fit within a single session. It focuses on generating plans for approval and scheduling for cron-based workers, rather than executing the tasks directly.