skills/plan-task/SKILL.md
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).
npx skillsauth add LevNas/ccmemo plan-taskInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Maintain plans and task progress across Claude Code sessions so that work can be resumed without losing context.
Delegate the plan/task work to a Sonnet subagent to minimize main context consumption.
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 directorycomplete mode), invoke record-knowledge for each candidate using the structured fields providedIMPORTANT: 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.
| 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 |
testing
Review and maintain the knowledge base — find stale entries, orphan entries without connections, missing links between related entries, and generate topic summaries. Supports the "internalization" phase of knowledge management by surfacing knowledge for periodic review and reflection.
development
Record tacit knowledge — quirks, pitfalls, dependencies, decisions, root causes — as tagged Markdown entries in `.claude/knowledge/entries/`. Use this skill whenever discoveries are made during work, when the user shares undocumented system behavior, or at plan completion to capture lessons learned. Also use when Claude Code makes a mistake pointed out by the user — record what happened, why it was wrong, and what to do next time.
development
Maintainer-only workflow for handling GitHub Secret Scanning alerts on OpenClaw. Use when Codex needs to triage, redact, clean up, and resolve secret leakage found in issue comments, issue bodies, PR comments, or other GitHub content.
development
Maintainer workflow for OpenClaw releases, prereleases, changelog release notes, and publish validation. Use when Codex needs to prepare or verify stable or beta release steps, align version naming, assemble release notes, check release auth requirements, or validate publish-time commands and artifacts.