القائمة
Use when the user says 'plan', 'todo', 'copy plan', 'append plan', 'resume plan', 'priorities', or 'what's next'.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| 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 |
Track tasks, manage plans, and survive CC compacts with three operating modes.
When this skill activates, output:
📋 Work — Plan execution engaged.
Then determine which mode to use based on the trigger.
| 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 |
Before executing ANY mode, silently gather current state. Do NOT present findings. Do NOT ask questions. Just internalize:
STATE.md (if it exists) — current task, blockers, next stepsCLAUDE.md (if it exists) — conventions, architecture decisionspython "$MEMSTACK_PATH/db/memstack-db.py" get-sessions <project> --limit 3
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.
Trigger: "copy plan" or when a new plan is provided
python "$MEMSTACK_PATH/db/memstack-db.py" add-plan-task '{"project":"<name>","task_number":<n>,"description":"<task>","status":"pending"}'
memory/projects/{project}-plan.md for human readabilityStatus values: pending, in_progress, completed, blocked
Trigger: "append plan" or when updating task statuses
python "$MEMSTACK_PATH/db/memstack-db.py" get-plan <project>
python "$MEMSTACK_PATH/db/memstack-db.py" update-task '{"project":"<name>","task_number":<n>,"status":"completed"}'
add-plan-taskTrigger: "resume plan" — use after CC compact or new session
python "$MEMSTACK_PATH/db/memstack-db.py" get-plan <project>
Plan: {project} ({done}/{total} complete)
Completed: [list]
In Progress: [list]
Pending: [list]
Blocked: [list with reasons]
Recommended next: {first pending task}
$MEMSTACK_PATH/db\memstack.db (via memstack-db.py)$MEMSTACK_PATH/memory\projects\ (legacy markdown)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
.claude/rules/work.md), always-on task planning awareness without skill file read. (Origin: MemStack v3.0-beta, Feb 2026)Use when the user says 'git-guard', 'check git protection', 'is this repo protected', 'verify gitleaks', 'set up git hooks', 'install git-guard', or wants to confirm a repo blocks secrets and internal files before commit. This is an installer and verifier, NOT a scanner (gitleaks does the actual scanning). Do NOT use for deep secret audits or RLS work.
Use when the user says 'tokenstack', 'compression', 'token savings', 'proxy status', or asks about context window usage.
Use when the user says 'save diary', 'log session', 'wrapping up', or at end of a productive session.
Use when the user says 'token optimization', 'save tokens', 'context window', 'reduce tokens', 'token stack', or 'TokenStack', or asks about extending context window capacity. Covers TokenStack, the built-in compression proxy that shrinks Claude Code tool output before it reaches the Anthropic API. Do NOT use for proxy troubleshooting or live status (Compress skill).
Use when the user references past sessions, asks 'what did we do', 'do you remember', 'last session', 'recall', or 'continue from'.
Use this skill when the user says 'Hetzner', 'VPS setup', 'server provisioning', 'deploy to VPS', 'hetzner-setup', 'cloud server', or needs to provision, harden, and deploy applications to a Hetzner Cloud server with Docker, Nginx/Caddy, SSL, and monitoring. Do NOT use for managed platform deployments like Railway or Netlify.