CCPM Project Management
automazeio/ccpm
Runs a spec-driven workflow from PRD to epic to GitHub issues to parallel agents, with status, standup and blocked-work reports from bundled scripts.
Plan and track execution of a task. An agent skill from mattolson/agent-sandbox.
Install Plan Task
$ npx skills add mattolson/agent-sandbox --skill plan-task -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mattolson/agent-sandbox plan-task --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/mattolson/agent-sandbox.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/plan-task .claude/skills/plan-task && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "plan-task" agent skill from https://github.com/mattolson/agent-sandbox/tree/main/.agents/skills/plan-task into .claude/skills/plan-task/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plan-task", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/mattolson/agent-sandbox/tree/main/.agents/skills/plan-taskType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add mattolson/agent-sandbox --skill plan-task -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mattolson/agent-sandbox plan-task --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mattolson/agent-sandbox.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/plan-task .agents/skills/plan-task && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "plan-task" agent skill from https://github.com/mattolson/agent-sandbox/tree/main/.agents/skills/plan-task into .agents/skills/plan-task/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plan-task", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mattolson/agent-sandbox --skill plan-task -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mattolson/agent-sandbox plan-task --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mattolson/agent-sandbox.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/plan-task .cursor/skills/plan-task && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "plan-task" agent skill from https://github.com/mattolson/agent-sandbox/tree/main/.agents/skills/plan-task into .cursor/skills/plan-task/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plan-task", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/mattolson/agent-sandbox.git --path .agents/skills/plan-task--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add mattolson/agent-sandbox --skill plan-task -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mattolson/agent-sandbox plan-task --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mattolson/agent-sandbox.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/plan-task .gemini/skills/plan-task && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "plan-task" agent skill from https://github.com/mattolson/agent-sandbox/tree/main/.agents/skills/plan-task into .gemini/skills/plan-task/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plan-task", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install mattolson/agent-sandbox plan-taskInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add mattolson/agent-sandbox --skill plan-task -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mattolson/agent-sandbox.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/plan-task .github/skills/plan-task && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "plan-task" agent skill from https://github.com/mattolson/agent-sandbox/tree/main/.agents/skills/plan-task into .github/skills/plan-task/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plan-task", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mattolson/agent-sandbox --skill plan-task -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mattolson/agent-sandbox plan-task --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mattolson/agent-sandbox.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/plan-task .opencode/skills/plan-task && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "plan-task" agent skill from https://github.com/mattolson/agent-sandbox/tree/main/.agents/skills/plan-task into .opencode/skills/plan-task/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plan-task", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
plan-task- GitHub stars
- 208
- Token cost
- ~1.4k tokens
- SKILL.md length
- 563 words
- Files
- 1
- Skills in repo
- 6
- Repo updated
- First seen
- Licence
- MIT
At a glance
Plan and track execution of a task. An agent skill from mattolson/agent-sandbox.
- Works in 3 steps: Planning → Execution → Completion
- Starting implementation of a task defined in a milestone plan
- SKILL.md covers Inputs, Output, Lifecycle and Task Document Template, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Plan Task is an agent skill from mattolson/agent-sandbox. Plan and track execution of a task. Use when starting implementation of a task defined in a milestone plan.
Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Product & Project Management, covering Project management. The repository describes itself as: Secure local dev environment for collaboration with AI coding agents. The licence is MIT.
When your agent uses it
- Starting implementation of a task defined in a milestone plan
- Tasks that involve Project management
Example prompts
- “/plan-task”
Workflow steps
3 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit c5b65e7. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Plan Task loads about 1.4k tokens when it runs. Until then it costs about 29 tokens; SKILL.md has 563 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from mattolson/agent-sandbox at commit c5b65e7, republished under its MIT licence (© mattolson). 563 words, ~1,406 tokens.
Download SKILL.mdSave it as
.claude/skills/plan-task/SKILL.md (or your agent's skills folder).- name
- plan-task
- description
- Plan and track execution of a task. Use when starting implementation of a task defined in a milestone plan.
Task Planning and Execution
Part of the three-tier planning system. See /plan for an overview.
This skill guides implementation of a single task, from initial planning through completion. It maintains an execution log that captures problems, decisions, and learnings along the way.
Inputs
Before starting, read:
- The milestone plan containing this task
docs/plan/learnings.md- to incorporate lessons from previous work- Any relevant decision documents in
docs/plan/decisions/
Output
Two files in docs/plan/milestones/{milestone}/tasks/{task}/:
task.md- The plan and final outcome (living document, update as things change)execution-log.md- Running log updated during implementation (captures the journey)
The task plan is a living document. Update scope, approach, and checklist as things evolve. The execution log preserves history, so there's no need to treat the plan as a snapshot.
Lifecycle
A task moves through three phases:
Phase 1: Planning
Before writing code, understand what we're building and how. Planning is iterative - expect to refine the approach through discussion before it's finalized.
This phase requires your approval before proceeding to execution.
1.1 Context Review
- Review the task's summary, scope, and acceptance criteria from the milestone plan
- Review applicable learnings from previous tasks
- Confirm understanding of what "done" looks like
1.2 Codebase Exploration
- Identify the files and systems involved
- Understand existing patterns and conventions
- Note integration points with other code
1.3 Approach Design
- Outline the implementation approach
- Identify changes needed (new files, modifications, deletions)
- Consider edge cases and error handling
- Flag uncertainties that need resolution
Capture the plan in the task document. Review and iterate until the approach is solid, then get explicit approval before proceeding to implementation.
Phase 2: Execution
During implementation:
- Keep the implementation steps checklist in
task.mdcurrent as steps are completed - Maintain the execution log in
execution-log.md
When to Update the Log
Update the execution log whenever:
- A new issue is encountered - describe the issue and its solution
- A key decision is made - capture the choice and rationale
- A lesson is learned - note insights that apply to future work
- 10 minutes have passed since the last update - review and capture any salient information
Do not let updates accumulate. Frequent, small updates are more valuable than infrequent summaries.
Show full SKILL.md (211 more words)Show less
What to Capture
- Issues and solutions: Problems encountered and how they were resolved
- Decisions: Technical choices and their rationale
- Scope changes: Anything that changed from the original plan and why
- Observations: Things noticed that might be relevant later
Checkpoints
At natural breakpoints, review progress:
- Is the approach still sound?
- Have we discovered anything that changes the plan?
- Are there decisions that should be recorded formally in
docs/plan/decisions/? - Does the implementation steps checklist need updating (new steps, changed steps, removed steps)?
Phase 3: Completion
When the task is done:
3.1 Acceptance Verification
- Verify each acceptance criterion is met
- Confirm tests are passing
- Ensure the PR is ready for review
3.2 Learning Capture
Review the execution log and extract learnings from this task:
- What would we do differently next time?
- What worked well that we should repeat?
- What did we learn that applies to future tasks?
Consolidate and distill insights from the execution log entries into docs/plan/learnings.md.
3.3 Cleanup
- Update the milestone plan if this task revealed new information
- Create decision documents for any significant decisions made
- Note if downstream tasks are affected
Task Document Template
Create at docs/plan/milestones/{milestone}/tasks/{task}/task.md:
# Task: {identifier} - {name}
## Summary
{From milestone plan}
## Scope
{From milestone plan, updated if changed}
## Acceptance Criteria
{From milestone plan}
- [ ] {Criterion 1}
- [ ] {Criterion 2}
## Applicable Learnings
{Lessons from previous work that apply to this task}
## Plan
### Files Involved
{List of files to create, modify, or delete}
### Approach
{How we're going to implement this}
### Implementation Steps
- [ ] {Step 1}
- [ ] {Step 2}
- [ ] {Step 3}
### Open Questions
{Uncertainties to resolve during implementation}
## Outcome
### Acceptance Verification
- [x] {Criterion 1 - verified}
- [x] {Criterion 2 - verified}
### Learnings
{What we learned from this task - also append to docs/plan/learnings.md}
### Follow-up Items
{Anything discovered that affects other tasks or the milestone plan}Execution Log Template
Create at docs/plan/milestones/{milestone}/tasks/{task}/execution-log.md.
Entries are in reverse chronological order - newest at the top, so the latest activity is always visible first.
# Execution Log: {identifier} - {name}
## {Timestamp} - Latest entry
{Entry describing what happened}
**Issue:** {If applicable - describe the problem}
**Solution:** {How it was resolved}
**Decision:** {If applicable - what was decided and why}
**Learning:** {If applicable - insight for future work}
## {Timestamp} - Previous entry
{Earlier entry}© mattolson, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .agents/skills/plan-task of mattolson/agent-sandbox.
Open the folder on GitHubat commit c5b65e7
Compare with similar skills
Plan Task next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Plan Task this skillmattolson/agent-sandbox | 208 | — | ~1.4k | Automated safety check: Pass | MIT | |
| CCPM Project Managementautomazeio/ccpm | 8.4k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Uvastral-sh/claude-code-plugins | 314 | 2 repos | ~980 | Automated safety check: Pass | Apache-2.0 | |
| Project Managementkunchenguid/firstmate | 7.6k | — | ~2.1k | Automated safety check: Pass | MIT | |
| Hivemind Goalsactiveloopai/hivemind | 1.6k | — | ~1.7k | Automated safety check: Notes | Apache-2.0 | |
| Ichartjswanghetommy/ichartjs | 352 | — | ~3.4k | Automated safety check: Pass | Apache-2.0 |
Similar skills
- Official
Uv
astral-sh/claude-code-plugins
Guide for using uv, the Python package and project manager. An agent skill from astral-sh/claude-code-plugins.
Project Management
kunchenguid/firstmate
Agent-only procedure for Firstmate project management. An agent skill from kunchenguid/firstmate.
Hivemind Goals
activeloopai/hivemind
Create, track and update team goals via the Deeplake virtual filesystem at memory/goal/.
Ichartjs
wanghetommy/ichartjs
Plan, validate, render, explain, and safely edit iChart.js visualizations from tabular, project, or diagram data.
Hivemind Goals
activeloopai/hivemind
Create, track and update team goals in Hivemind via the hivemind CLI.
More from mattolson/agent-sandbox
Operating In Agent Sandbox
mattolson/agent-sandbox
Read this when you are an AI coding agent running inside an Agent Sandbox container.
Plan
mattolson/agent-sandbox
Entry point for the three-tier planning system. An agent skill from mattolson/agent-sandbox.
Plan Milestone
mattolson/agent-sandbox
Break a milestone into discrete tasks. An agent skill from mattolson/agent-sandbox.
Plan Project
mattolson/agent-sandbox
Create a project plan for a new initiative. An agent skill from mattolson/agent-sandbox.
Add Agent
mattolson/agent-sandbox
Add a new AI coding agent to Agent Sandbox. An agent skill from mattolson/agent-sandbox.
Related
Categories
Questions about Plan Task
What does Plan Task do?
Plan and track execution of a task. An agent skill from mattolson/agent-sandbox. Plan Task is an agent skill from mattolson/agent-sandbox. Plan and track execution of a task.
When should I use Plan Task?
Plan Task fits situations like: starting implementation of a task defined in a milestone plan; tasks that involve Project management.
How do I install Plan Task in Claude Code?
Run `npx skills add mattolson/agent-sandbox --skill plan-task -a claude-code`. Or copy the skill folder (.agents/skills/plan-task in mattolson/agent-sandbox) into .claude/skills/plan-task in your project. Claude Code loads it when a task matches its description.
How do I install Plan Task in Codex?
Run `npx skills add mattolson/agent-sandbox --skill plan-task -a codex`. Or copy the skill folder (.agents/skills/plan-task in mattolson/agent-sandbox) into .agents/skills/plan-task in your project. Codex loads it when a task matches its description.
Can I use Plan Task in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mattolson/agent-sandbox --skill plan-task -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/plan-task, .gemini/skills/plan-task, .github/skills/plan-task and .opencode/skills/plan-task in your project.
What does Plan Task need to run?
SKILL.md names no scripts, command-line tools or credentials: Plan Task is instructions for the agent only.
Does Plan Task access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Plan Task safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Plan Task use?
Plan Task is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Plan Task use?
About 1.4k tokens (SKILL.md is roughly 5.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Plan Task?
Skills that share tags, products or a category with Plan Task: CCPM Project Management (automazeio/ccpm, 8.4k stars), Uv (astral-sh/claude-code-plugins, 314 stars), Project Management (kunchenguid/firstmate, 7.6k stars) and Hivemind Goals (activeloopai/hivemind, 1.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Plan Task?
mattolson (a GitHub user) maintains it in mattolson/agent-sandbox, which has 208 GitHub stars. The repository holds 6 skills in this directory. The repository was last updated on October 1, 2026.
Source: mattolson/agent-sandbox on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.