一键导入
save-task-list
Save current task list for reuse across sessions
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Save current task list for reuse across sessions
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when: User wants to INSPECT, MONITOR, START, APPROVE, or CONTROL Archon workflow RUNS in the current project — driven through the `archon` CLI over bash. Triggers (inspect): "what's running", "list runs", "show recent runs", "run status", "did the review pass", "check run <id>", "show me run <id>", "what happened in that run". Triggers (control): "approve the plan", "approve run <id>", "reject that run", "cancel that run", "abandon run <id>", "resume run <id>", "continue that run". Triggers (start): "start <workflow> in the background", "kick off <workflow> detached". Capability: Drives `archon workflow runs/get/status/run --detach/approve/reject/abandon/resume` with machine-readable `--json` output, scoped to the current project by cwd. NOT for: Authoring workflows/commands, or Archon setup/config — use the broader `archon` skill.
Use when: User wants to run Archon workflows, CREATE workflows or commands, set up Archon, or manage Archon configuration. Triggers (run): "use archon to", "run archon", "archon workflow", "use archon for", "have archon", "let archon", "ask archon to". Triggers (create): "create a workflow", "write a workflow", "make a command", "author a workflow", "new workflow", "new command", "archon workflow yaml". Triggers (setup): "set up archon", "install archon", "how to use archon", "configure archon", "archon setup", "get started with archon". Triggers (config): "change my archon config", "modify archon config", "archon config", "change archon settings", "update my config", "help me change my config", "edit archon config", "archon configuration". Triggers (init): "initialize archon", "set up .archon", "archon init", "add archon to repo". Capability: Runs AI workflows in isolated git worktrees for parallel development. Also: Creates and manages workflow YAML files, c
Create a release from dev branch. Generates changelog entries from commits, bumps version, and creates a PR to main. TRIGGERS - Use this skill when user says: - "/release" - create a patch release (default) - "/release minor" - create a minor release - "/release major" - create a major release - "make a release", "cut a release", "ship it", "release to main"
Verify a released archon binary works end-to-end via a specific install path. Use when: cutting a new release, reproducing a user bug report on the released version, or validating that a hotfix binary actually works after a re-tag. Triggers: "test the release", "test 0.3.1 via brew", "verify the curl install", "smoke test the binary", "did the release binary work", "run /test-release", "verify the release". NOT for: testing dev work (use bun link directly), testing unreleased changes (build locally via scripts/build-binaries.sh first), or running the full validate suite (bun run validate is separate).
Use when: User wants to extend Docker with custom tools, personalize the Docker environment, or set up user-specific Docker customization. Triggers: 'extend docker', 'docker-extend', 'add tools to docker', 'customize docker', 'add my tools to the container', 'personalize docker setup', 'docker user setup', 'install tools in docker'. Does: Interactively sets up Dockerfile.user and docker-compose.override.yml so users can add personal tools to their Docker environment without affecting maintainer files or committing user-specific config to git.
Replicate and validate a GitHub issue by spinning up Archon, analyzing the issue, and systematically testing all described symptoms using browser automation. Use when: User wants to reproduce a bug, validate a GitHub issue, confirm a reported problem, or investigate whether an issue is real before working on a fix. Triggers: "replicate issue", "reproduce issue", "validate issue", "confirm bug", "test issue", "can you reproduce", "try to replicate", "verify the bug". Capability: Checks out main, pulls latest, starts Archon, reads the GitHub issue, then uses agent-browser to systematically test every symptom and produce a findings report. NOT for: Fixing issues (use /archon or /exp-piv-loop:fix-issue), general UI testing (use /validate-ui).
| name | save-task-list |
| description | Save current task list for reuse across sessions |
| disable-model-invocation | true |
| hooks | {"Stop":[{"hooks":[{"type":"prompt","prompt":"A skill just finished saving a task list for session reuse.\nEvaluate the assistant's final message below.\n\n$ARGUMENTS\n\nVerify:\n1. A task list ID was found and displayed\n2. A startup command (CLAUDE_CODE_TASK_LIST_ID=<id> claude) was provided\n3. A task summary was shown\n\nReturn {\"ok\": true} if all three are present.\nReturn {\"ok\": false, \"reason\": \"Missing: <what>\"} if anything is missing.\n","statusMessage":"Verifying task list was saved..."}]}],"PostToolUse":[{"matcher":"Bash","hooks":[{"type":"command","command":"jq -r '[.tool_name, .tool_input.command // \"n/a\"] | join(\": \")' | head -1","statusMessage":"Logging tool use...","once":true}]}]} |
Save the current session's task list so it can be restored in future sessions.
ls -1t ~/.claude/tasks/ 2>/dev/null | head -5 || echo "none found"ls -1t ~/.claude/tasks/ 2>/dev/null | head -1 | xargs -I{} ls ~/.claude/tasks/{} 2>/dev/null | head -10 || echo "no tasks"Find the current task list ID by checking ~/.claude/tasks/ for the most
recently modified directory. List the directories sorted by modification time.
Verify the match — read the task files inside the directory and compare them to any tasks you know about from this session. Confirm you have the correct task list.
Log the session mapping — write the mapping to .claude/archon/sessions/:
mkdir -p .claude/archon/sessions
echo '{"session": "${CLAUDE_SESSION_ID}", "task_list": "<TASK_LIST_ID>", "saved_at": "'$(date -u +%Y-%m-%dT%H:%M:%SZ)'"}' \
>> .claude/archon/sessions/task-lists.jsonl
Verify the SessionStart hook is installed — the project-level
.claude/settings.json already includes a SessionStart hook that runs
verify-task-list.sh on every session start. Confirm it's present by
reading the file. If it's missing for some reason, add it back:
{
"hooks": {
"SessionStart": [
{
"hooks": [
{
"type": "command",
"command": ".claude/skills/save-task-list/hooks/verify-task-list.sh",
"statusMessage": "Checking for restored task list..."
}
]
}
]
}
}
Important: Merge — don't overwrite existing settings. If hooks or SessionStart
already exists, append to the array. If the hook is already installed, skip this step.
Output the startup command for the user:
To continue with this task list in a new session:
CLAUDE_CODE_TASK_LIST_ID=<task_list_id> claude
Explain: On startup, the SessionStart hook will verify the task list exists and show a confirmation message.
Show the current task summary so the user knows what's preserved (task subjects, statuses, and any dependencies).