Agent skill

Work

by cwinvestments in cwinvestments/memstack

A skill your agent uses when the user says 'plan', 'todo', 'copy plan', 'append plan', 'resume plan', 'priorities', or 'what's next'.

MITAuto-check passedAgent Workflows

Install Work

skills CLI

$ npx skills add cwinvestments/memstack --skill work -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install cwinvestments/memstack work --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/cwinvestments/memstack.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/work .claude/skills/work && rm -rf skills-src

Use ~/.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/

Paste into Claude Code

Install the "work" agent skill from https://github.com/cwinvestments/memstack/tree/master/skills/work into .claude/skills/work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "work", 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

$skill-installer install https://github.com/cwinvestments/memstack/tree/master/skills/work

Type 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.

skills CLI

$ npx skills add cwinvestments/memstack --skill work -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install cwinvestments/memstack work --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/cwinvestments/memstack.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/work .agents/skills/work && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "work" agent skill from https://github.com/cwinvestments/memstack/tree/master/skills/work into .agents/skills/work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "work", 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.

skills CLI

$ npx skills add cwinvestments/memstack --skill work -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install cwinvestments/memstack work --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/cwinvestments/memstack.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/work .cursor/skills/work && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "work" agent skill from https://github.com/cwinvestments/memstack/tree/master/skills/work into .cursor/skills/work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "work", 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

$ gemini skills install https://github.com/cwinvestments/memstack.git --path skills/work

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add cwinvestments/memstack --skill work -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install cwinvestments/memstack work --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/cwinvestments/memstack.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/work .gemini/skills/work && rm -rf skills-src

Use ~/.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/

Paste into Gemini CLI

Install the "work" agent skill from https://github.com/cwinvestments/memstack/tree/master/skills/work into .gemini/skills/work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "work", 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.

GitHub CLI

$ gh skill install cwinvestments/memstack work

Installs 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).

skills CLI

$ npx skills add cwinvestments/memstack --skill work -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/cwinvestments/memstack.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/work .github/skills/work && rm -rf skills-src

Use ~/.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/

Paste into GitHub Copilot

Install the "work" agent skill from https://github.com/cwinvestments/memstack/tree/master/skills/work into .github/skills/work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "work", 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.

skills CLI

$ npx skills add cwinvestments/memstack --skill work -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install cwinvestments/memstack work --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/cwinvestments/memstack.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/work .opencode/skills/work && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "work" agent skill from https://github.com/cwinvestments/memstack/tree/master/skills/work into .opencode/skills/work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "work", 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: work
GitHub stars: 423
Token cost: ~1.4k tokens
SKILL.md length: 552 words
Files: 1
Skills in repo: 87
Repo updated: Sep 26, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

A skill your agent uses when the user says 'plan', 'todo', 'copy plan', 'append plan', 'resume plan', 'priorities', or 'what's next'.

Works in 4 steps: Read the project's STATE.md (if it… → Read the project's CLAUDE.md (if it… → Check recent diary → …
The user says plan
SKILL.md covers Activation, Context Guard, Step 0: Silent Context… and Mode 1: Copy Plan, plus 7 more sections
Calls python and git

What it does

Work is an agent skill from cwinvestments/memstack. Use when the user says 'plan', 'todo', 'copy plan', 'append plan', 'resume plan', 'priorities', or 'what's next'.

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 Agent Workflows. The repository describes itself as: Structured skill framework for Claude Code. 130 skills, persistent memory, TokenStack compression, localhost dashboard with 3-agent runner, real-time streaming, MCP tools. The licence is MIT.

When your agent uses it

The user says plan

Example prompts

“copy plan”
“append plan”
“resume plan”
“/work”

Requirements

Python 3

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

Read the project's STATE.md (if it exists): current task, blockers, next steps
Read the project's CLAUDE.md (if it exists): conventions, architecture decisions
Check recent diary
Check git state

What it can do on your machine

Read from SKILL.md and the folder at commit 00370ce. 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
Shell commands in SKILL.md call:
- python
- git
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
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

Work loads about 1.4k tokens when it runs. Until then it costs about 30 tokens; SKILL.md has 552 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~30
When it runs · the whole SKILL.md, loaded when a task matches: ~1.4k

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 cwinvestments/memstack at commit 00370ce, republished under its MIT licence (© cwinvestments). 552 words, ~1,383 tokens.

Download SKILL.mdSave it as .claude/skills/work/SKILL.md (or your agent's skills folder).

name: work
description: Use when the user says 'plan', 'todo', 'copy plan', 'append plan', 'resume plan', 'priorities', or 'what's next'.
version: 1.0.0

📋 Work: Plan Execution Engaged

Track tasks, manage plans, and survive CC compacts with three operating modes.

Activation

When this skill activates, output:

📋 Work: Plan execution engaged.

Then determine which mode to use based on the trigger.

Context Guard

Context	Status
User says "copy plan", "append plan", "resume plan"	ACTIVE: use matching mode
User says "what's next", "todo", "priorities"	ACTIVE: quick query mode
User provides a task list or plan	ACTIVE: copy mode
General discussion about planning concepts	DORMANT: do not activate
User is executing a task (not managing the list)	DORMANT: do not activate

Step 0: Silent Context Compilation (MANDATORY)

Before executing ANY mode, silently gather current state. Do NOT present findings. Do NOT ask questions. Just internalize:

Read the project's STATE.md (if it exists): current task, blockers, next steps
Read the project's CLAUDE.md (if it exists): conventions, architecture decisions

Check recent diary:

bash

python "${CLAUDE_PLUGIN_ROOT}/db/memstack-db.py" get-sessions <project> --limit 3

Check git state:
bash
```
git log --oneline -5
git diff --stat
```

This is silent. Synthesize an internal understanding of where the project stands. Then proceed to the triggered mode with full context. The user already knows their project state, don't waste their time repeating it back.

Mode 1: Copy Plan

Trigger: "copy plan" or when a new plan is provided

Parse the entire plan into individual numbered tasks
For each task, save to SQLite:

Write the payload to a file, then pipe it in with - as the argument. A payload on stdin is never seen by the shell's parser, so a redirection operator inside a task description cannot be read as one.
bash
```
cat task.json | python "${CLAUDE_PLUGIN_ROOT}/db/memstack-db.py" add-plan-task -
```
task.json contains:
json
```
{"project":"<name>","task_number":<n>,"description":"<task>","status":"pending"}
```
Confirm with task count
Also write a markdown copy to memory/projects/{project}-plan.md for human readability

Status values: pending, in_progress, completed, blocked

Mode 2: Append Plan (Update Tasks)

Trigger: "append plan" or when updating task statuses

Read current plan from SQLite:

bash

python "${CLAUDE_PLUGIN_ROOT}/db/memstack-db.py" get-plan <project>

Update individual task statuses:

Same form, even though this payload is only metadata. One rule with no exceptions is easier to follow than a rule you have to judge.
bash
```
cat task-update.json | python "${CLAUDE_PLUGIN_ROOT}/db/memstack-db.py" update-task -
```
task-update.json contains:
json
```
{"project":"<name>","task_number":<n>,"status":"completed"}
```
Add new tasks if needed via add-plan-task
No size limits needed: SQLite handles scale

Show full SKILL.md (232 more words)Show less

Mode 3: Resume Plan

Trigger: "resume plan", use after CC compact or new session

Load plan from SQLite:

bash

python "${CLAUDE_PLUGIN_ROOT}/db/memstack-db.py" get-plan <project>

Parse the JSON output for task statuses

Output a summary:

Plan: {project} ({done}/{total} complete)

Completed: [list]
In Progress: [list]
Pending: [list]
Blocked: [list with reasons]

Recommended next: {first pending task}

Continue from the first incomplete task

Quick Commands

"what's next": queries plan, returns the single next pending task
"priorities": shows top 3 pending items from the plan
"todo": shows all pending and in-progress items with status

Inputs

Plan text (copy mode) or project name (append/resume)
Database: ~/.memstack/memstack.db (via memstack-db.py)
Fallback: $MEMSTACK_PATH/memory\projects\ (legacy markdown)

Outputs

Formatted task list with status indicators
Updated plan file in memory
Next recommended action

Example Usage

User: "resume plan for AdminStack"

📋 Work: Plan execution engaged.

Plan: AdminStack (5/9 complete)

[x] 1. Build CC Monitor page
[x] 2. Add setup guide
[x] 3. Fix API key validation
[x] 4. Add refresh feedback
[x] 5. Update guide with curl snippet
[ ] 6. Build cc-reporter.js Node script
[ ] 7. Add WebSocket real-time updates
[ ] 8. Session grouping by project
[!] 9. Mobile polish (blocked: waiting for design specs)

Recommended next: Task 6: Build cc-reporter.js

Level History

Lv.1: Base: Single-mode TODO tracking. (Origin: MemStack v1.0, Feb 2026)
Lv.2: Enhanced: Three modes (copy/append/resume), 1K-line limit with auto-summarize, context guard, YAML frontmatter. (Origin: MemStack v2.0 MemoryCore merge, Feb 2026)
Lv.3: Advanced: SQLite-backed plans with per-task status tracking, no size limits, structured queries. (Origin: MemStack v2.1 Accomplish-inspired upgrade, Feb 2026)
Lv.4: Native: CC rules integration (.claude/rules/work.md), always-on task planning awareness without skill file read. (Origin: MemStack v3.0-beta, Feb 2026)
Lv.5: Context-aware: Silent context compilation (Step 0): reads STATE.md, CLAUDE.md, recent diary, and git state before any operation. Inspired by Intellegix silent pre-flight pattern. (Origin: MemStack v3.2, Feb 2026)

Files

Just SKILL.md in skills/work of cwinvestments/memstack.

Open the folder on GitHubat commit 00370ce

Compare with similar skills

Work 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.

Work compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Work this skillcwinvestments/memstack	423	—	~1.4k	Automated safety check: Pass	MIT	12 days ago
MCP Server Builderanthropics/skills	180k	64 repos	~2.3k	Automated safety check: Pass	Apache-2.0	3 days ago
Hook Development for Claude Code Pluginsanthropics/claude-plugins-official	38k	11 repos	~4.1k	Automated safety check: Notes	Apache-2.0	today
Using Superpowersfarm-fe/farm	5.6k	35 repos	~1.4k	Automated safety check: Pass	MIT	16 days ago
Executing Plans Inlineobra/superpowers	296k	2 repos	~5.1k	Automated safety check: Pass	MIT	today
Claude Code Agent Developmentanthropics/claude-plugins-official	38k	8 repos	~2.8k	Automated safety check: Pass	Apache-2.0	today

Similar skills

MCP Server Builder
anthropics/skills
Official
Guides the design and implementation of Model Context Protocol servers in TypeScript or Python, from tool naming and error messages to evaluation.
180k GitHub starsUsed in 64 repos~2.3k tokens
Agent WorkflowsAuto-check passed
Hook Development for Claude Code Plugins
anthropics/claude-plugins-official
Official
Explains how to write Claude Code plugin hooks, both prompt-based checks and bash commands, for events such as PreToolUse, Stop and SessionStart.
38k GitHub starsUsed in 11 repos~4.1k tokens
Agent WorkflowsAuto-check: notes
Using Superpowers
farm-fe/farm
A skill your agent uses when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions
5.6k GitHub starsUsed in 35 repos~1.4k tokens
Agent WorkflowsAuto-check passed
Executing Plans Inline
obra/superpowers
Has the agent carry out an implementation plan itself, task by task in the current session, keeping a ledger, proving each step with a test and ending with one whole-branch review.
296k GitHub starsUsed in 2 repos~5.1k tokens
Agent WorkflowsAuto-check passed
Claude Code Agent Development
anthropics/claude-plugins-official
Official
Explains how to write agents for Claude Code plugins: the markdown file with YAML frontmatter, trigger descriptions, model and color settings, and system prompt design.
38k GitHub starsUsed in 8 repos~2.8k tokens
Agent WorkflowsAuto-check passed
Skill Creator
Azure/azqr
Official
Create new skills, modify and improve existing skills, and measure skill performance.
795 GitHub starsUsed in 89 repos~8.2k tokens
Agent WorkflowsAuto-check passed

More from cwinvestments/memstack

All 87 skills in this repo

Memstack SEO Site Audit
cwinvestments/memstack
A skill your agent uses when the user says 'SEO audit', 'site audit', 'check SEO', 'audit my site', 'SEO check', 'technical SEO', or is evaluating a website's search engine optimization health, meta…
423 GitHub stars~3.5k tokensUpdated 12 days ago
Auto-check passed
Memstack SEO Schema Markup
cwinvestments/memstack
A skill your agent uses when the user says 'add schema', 'schema markup', 'JSON-LD', 'structured data', 'rich results', 'rich snippets', or is adding or fixing schema.org structured data for better…
423 GitHub stars~2.7k tokensUpdated 12 days ago
Auto-check passed
Compress
cwinvestments/memstack
A skill your agent uses when the user says 'tokenstack', 'compression', 'token savings', 'proxy status', or asks about context window usage.
423 GitHub stars~1.2k tokensUpdated 12 days ago
Auto-check passed
Diary
cwinvestments/memstack
A skill your agent uses when the user says 'save diary', 'log session', 'wrapping up', or at end of a productive session.
423 GitHub stars~5k tokensUpdated 12 days ago
Auto-check passed
Echo
cwinvestments/memstack
A skill your agent uses when the user references past sessions, asks 'what did we do', 'do you remember', 'last session', 'recall', or 'continue from'.
423 GitHub stars~1.7k tokensUpdated 12 days ago
Auto-check passed
Familiar
cwinvestments/memstack
A skill your agent uses when the user says 'dispatch', 'send familiar', 'split task', or needs work split across parallel CC sessions.
423 GitHub stars~556 tokensUpdated 12 days ago
Auto-check passed

Questions about Work

What does Work do?

A skill your agent uses when the user says 'plan', 'todo', 'copy plan', 'append plan', 'resume plan', 'priorities', or 'what's next'. Work is an agent skill from cwinvestments/memstack. Use when the user says 'plan', 'todo', 'copy plan', 'append plan', 'resume plan', 'priorities', or 'what's next'.

When should I use Work?

Work fits situations like: the user says plan.

How do I install Work in Claude Code?

Run `npx skills add cwinvestments/memstack --skill work -a claude-code`. Or copy the skill folder (skills/work in cwinvestments/memstack) into .claude/skills/work in your project. Claude Code loads it when a task matches its description.

How do I install Work in Codex?

Run `npx skills add cwinvestments/memstack --skill work -a codex`. Or copy the skill folder (skills/work in cwinvestments/memstack) into .agents/skills/work in your project. Codex loads it when a task matches its description.

Can I use Work 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 cwinvestments/memstack --skill work -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/work, .gemini/skills/work, .github/skills/work and .opencode/skills/work in your project.

What does Work need to run?

Going by SKILL.md and its folder, Work needs the command-line tools its instructions call (python and git). Our summary lists: Python 3.

Does Work access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Work 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 Work use?

Work 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 Work use?

About 1.4k tokens (SKILL.md is roughly 5.5k 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 Work?

Skills that share tags, products or a category with Work: MCP Server Builder (anthropics/skills, 180k stars), Hook Development for Claude Code Plugins (anthropics/claude-plugins-official, 38k stars), Using Superpowers (farm-fe/farm, 5.6k stars) and Executing Plans Inline (obra/superpowers, 296k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Work?

cwinvestments (a GitHub user) maintains it in cwinvestments/memstack, which has 423 GitHub stars. The repository holds 87 skills in this directory. The repository was last updated on September 26, 2026.

Source: cwinvestments/memstack on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Work

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

📋 Work: Plan Execution Engaged

Activation

Context Guard

Step 0: Silent Context Compilation (MANDATORY)

Mode 1: Copy Plan

Mode 2: Append Plan (Update Tasks)

Mode 3: Resume Plan

Quick Commands

Inputs

Outputs

Example Usage

Level History

Files

Compare with similar skills

Similar skills

More from cwinvestments/memstack

Related

Questions about Work