plan-task

A guide for saving plans and task progress so coding work can continue across Claude Code sessions. A monorepo is one repository containing multiple projects; this input does not say whether one is used here.

In plain words
What is it for?
Creating or resuming task plans, recording progress, and keeping task information in a project’s task directory.
Why use it?
It reduces the chance of losing unfinished work, decisions, or task context when a session ends or work is resumed later.

Skill for Claude CodeCodex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/levnas/ccmemo/plan-task
Any agent
npx skills add LevNas/ccmemo --skill plan-task
Clone the repo
git clone --depth 1 https://github.com/LevNas/ccmemo

Made for: Claude Code, Codex.

Per session 65 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 821 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00065 $0.00821
Opus 5 $0.00032 $0.00411
Sonnet 5 $0.00013 $0.00164
Haiku 4.5 $0.00006 $0.00082

Measured yesterday against content hash 5421fee5dce6, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

plan-task scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/plan-task/SKILL.md · 84 lines

How it starts

The opening of the file, as written. The whole thing — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Plan & Task Persistence

Goal

Maintain plans and task progress across Claude Code sessions so that work can be resumed without losing context.

Execution

Delegate the plan/task work to a Sonnet subagent to minimize main context consumption.

  1. Determine the operation mode from user input or session context
  2. Prepare structured input fields for the subagent
  3. Spawn a subagent with the following configuration:
Agent(
  subagent_type: "general-purpose",
  model: "sonnet",
  description: "plan and task management",
  prompt: |
    You are a plan and task management agent. Read the procedure file and follow it precisely.

    ## Operation
    {mode}

    ## Input
    ### what(事実)
    {what}

    ### why(判断理由)
    {why}

    ### context(背景情報)
    {context}

    ### tags_hint(推奨タグ)
    {tags_hint}

    ## Instructions
    1. Read the procedure file at: {plugin_root}/skills/plan-task/procedure.md
    2. Execute the procedure section matching the operation mode: {mode}
    3. The project root is: {project_root}
    4. The tasks directory is: {project_root}/.claude/tasks/
    5. For setup, asset files are at: {plugin_root}/skills/plan-task/assets/
    6. Return: operation performed, files created/modified, current plan status, and knowledge candidates (if any)
)

Replace the placeholders:

  • {mode} — one of: session-start, create-plan, update-progress, revise-plan, pause, complete
  • {what} — the factual situation (e.g., "user wants to create a plan for Docker migration" or "three tasks completed, one blocker found")
  • {why} — why this operation is needed now (e.g., "new session started, need to check for incomplete work")
  • {context} — relevant background (current branch, related issues, recently modified files, active plan slug if known)
  • {tags_hint} — recommended tags for any knowledge entries that may be created (especially relevant for complete mode)
  • {plugin_root} — the plugin's installation path (shown in the skill loading message as "Base directory for this skill")
  • {project_root} — the project working directory

Read the full file on GitHub · 84 lines

Files

What ships with it

3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. yesterday First seen · 84 lines · 65 tokens per session scan A 5421fee5dce6

Subscribe to this mod's changes

plan-task is a skill published in the GitHub repository LevNas/ccmemo (3 stars, last pushed 16d ago), licensed MIT. It adds 65 tokens to every session and 821 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

design-sprint

Run a structured 5-day process to prototype, test, and validate product ideas with real users. Use when the user mentions "design sprint", "validate before we build", "rapid prototype", "test with users", or "should we build this". Also trigger when a team is stuck in endless debate over a high-stakes product…

wondelai/skills · 137 tokens

create-app

Guided journey from a raw app idea to a validated, cleanly architected first version that ships on a sustainable cadence. Orchestrates ten skills phase by phase - lean-startup, design-sprint, clean-architecture, domain-driven-design, clean-code, pragmatic-programmer, system-design, ios-hig-design, 37signals-way…

wondelai/skills · 217 tokens

create-business

Guided journey from raw idea to a validated, positioned, priced business with a chosen beachhead. Orchestrates ten skills phase by phase - jobs-to-be-done, mom-test, design-sprint, lean-startup, good-strategy-bad-strategy, blue-ocean-strategy, obviously-awesome, hundred-million-offers, monetizing-innovation…

wondelai/skills · 211 tokens

improve-website

Guided journey from a live website that underperforms to a prioritized, evidence-backed backlog of conversion, usability, message, and speed fixes - each shipped as a testable experiment. Orchestrates eight skills phase by phase - cro-methodology, ux-heuristics, refactoring-ui, web-typography, storybrand-messaging…

wondelai/skills · 225 tokens

f1-test-drive

Orchestrate F1 test drives to validate the Cyrus agent system end-to-end across issue-tracker, EdgeWorker, and activity rendering.

cyrusagents/cyrus · 33 tokens

issue-triage

Triage and categorize GitHub issues with priority labels. Use when user says "triage issues", "check issues", "review open issues", or during regular maintenance of GitHub issue backlog.

decebals/claude-code-java · 44 tokens