How this skill is triggered — by the user, by Claude, or both
Slash command
/dev-pipeline:save-task-listThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Save the current session's task list so it can be restored in future sessions.
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/dev-pipeline/sessions/:
mkdir -p .claude/dev-pipeline/sessions
echo '{"session": "${CLAUDE_SESSION_ID}", "task_list": "<TASK_LIST_ID>", "saved_at": "'$(date -u +%Y-%m-%dT%H:%M:%SZ)'"}' \
>> .claude/dev-pipeline/sessions/task-lists.jsonl
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).
npx claudepluginhub tviles/claude-plugins --plugin dev-pipelineGuides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.