plan-task
Skill4 starsChanged 5 months agoMITView on GitHub
Persist multi-step plans and task progress across Claude Code sessions. Use when starting work that may span multiple sessions, resuming incomplete plans, or updating task progress. Supports two modes: Git-tracked (shared via commits) and Issue-centric (issue tracker as primary source of truth, local scratchpad for sessions).
12 other projects use a version of this.
Adopted by
Most recently taken up by
- etr/groundworktheir own version, first seen Nov 8, 2026
- rumotion/ai-agent-project-templatetheir own version, first seen Nov 1, 2026
- griffinhilly/claude-code-synthesistheir own version, first seen Nov 1, 2026
- fitlab-ai/agent-infratheir own version, first seen Oct 27, 2026
- anaidenko/claude-notify-resumetheir own version, first seen Oct 15, 2026
- Yesterday-AI/ytstacktheir own version, first seen Oct 13, 2026
Used with
Projects with it also use ship, handoff and 1 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
AWSSkillship
Finalize dev work on an issue branch — update docs, push, and open a PR.
Also in 3 projects that use this
MicrosoftSkillhandoff
Compact the current conversation into a handoff document for another agent to pick up.
Also in 4 projects that use this
GoogleSkillcode-review
Adversarial systems, concurrency, memory-model, and architecture code review protocol. Use this skill whenever asked to review code, PRs, diffs, or branches in Filament.
Also in 3 projects that use this
Other versions12 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 12
- ModelEngine-Group/fit-framework★ 2.1ksame name
- mattolson/agent-sandbox★ 212same name
- fitlab-ai/agent-infra★ 87same name
- griffinhilly/claude-code-synthesis★ 67same name
- jezweb/vite-flare-starter★ 49same name
- etr/groundwork★ 45same name
- Yesterday-AI/ytstack★ 2same name
- anaidenko/claude-notify-resume★ 1same name
- NAVNAV221/ai-native-codebase★ 1same name
- rumotion/ai-agent-project-template★ 1same name
2 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository3 other files it gives its agents.
- recall-knowledgeSkill
- record-knowledgeSkill
- review-knowledgeSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 0 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 10 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 24
If a decision the plan needs is still open, settle it with the user now (with ccharness installed, ccharness:settle-decisions).
- Very specific: line 28
Put the agreed Verification and Out of Scope in the settled field below.
- Very specific: line 80
If the subagent returns knowledge candidates (typically from complete mode), invoke record-knowledge for each candidate using the …
“Common” is measured: kept by at least 6 in 10 of the 10 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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.
- Determine the operation mode from user input or session context
- For
create-planandrevise-plan, settle with the user first. The plan written in these modes is a spec: a record of decisions already made, which later sessions build from. The subagent cannot talk to the user, so do these in the main session before spawning it:- If a decision the plan needs is still open, settle it with the user now (with ccharness installed,
ccharness:settle-decisions). Do not leave it for the subagent to fill in. - Show the user how the work will be verified (Verification) and get their agreement before the plan is written. Prefer checks that already exist (tests, commands) and as few as will do.
- Collect what was considered and left out, with the reason (Out of Scope). If the conversation has none, ask the user; "none" is not an answer.
- For
revise-plan: the Out of Scope items are the ones of the current plan that still hold plus what the revision leaves out. If the current plan has no Out of Scope section and the conversation has none, ask the user. Agree the Verification again only if the revision changes it; otherwise pass the current one. - Put the agreed Verification and Out of Scope in the
settledfield below.
- If a decision the plan needs is still open, settle it with the user now (with ccharness installed,
- Prepare structured input fields for the subagent
- 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}
### settled(create-plan / revise-plan: agreed Verification and Out of Scope)
{settled}
## 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 forcompletemode){settled}— forcreate-planandrevise-plan: the Verification the user agreed to and the Out of Scope items, from step 2; for other modes, "n/a"{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
- Report the subagent's result to the user (operation performed, files modified, current status). If a
create-planorrevise-plansubagent returns what is missing instead of writing the plan, settle that with the user as in step 2 and spawn it again. - If the subagent returns knowledge candidates (typically from
completemode), invokerecord-knowledgefor each candidate using the structured fields provided
IMPORTANT: The procedure file path uses the plugin's base directory, NOT the project directory. Read the "Base directory for this skill" line from the skill loading message to determine the correct path.
Mode Selection Guide
| User signal | Mode |
| Session just started / post-compaction / resume | session-start |
| "plan ...", "let's plan ...", "create a plan for ..." | create-plan |
| "progress update", "update progress", signals a break | update-progress |
| "revise the plan", "the approach needs to change" | revise-plan |
| "taking a break", "that's it for today", "pausing" | pause |
| "plan is done", "all tasks complete", "wrap up" | complete |
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

