tasklist-conventions
This skill should be used when working with built-in TaskList tools (TaskCreate, TaskUpdate, TaskList, TaskGet) to track execution progress within and across Claude Code sessions.
What this skill does
# TaskList Conventions ## Overview TaskList is a built-in Claude Code feature for tracking task execution. Tasks are stored in `~/.claude/tasks/[session-uuid]/` and can be shared across sessions using the `import-tasks` skill. ## When to Use TaskList **Use TaskList when:** - Executing a plan with multiple steps - Tracking dependencies between work items - Coordinating work across sessions or subagents - Progress needs to be visible and trackable **Consider file-todos instead when:** - Findings need detailed documentation (Problem Statement, Findings, Solutions) - Work items need to be committed to the repository - Rich context with work logs is needed **Use both when:** - Review findings need documentation (file-todos) AND execution tracking (TaskList) ## Built-in Tools | Tool | Purpose | |------|---------| | `TaskCreate` | Create a new task with subject, description, activeForm | | `TaskUpdate` | Update status, add dependencies, modify tasks | | `TaskList` | View all tasks with status and blockers | | `TaskGet` | Get full details of a specific task | ## Task Fields **Required:** `subject` (imperative form), `description` (detailed scope) **Recommended:** `activeForm` (present continuous for spinner display) **Set via TaskUpdate:** `status` (pending/in_progress/completed), `addBlockedBy`, `addBlocks` ## Conventions ### Task Subjects Use imperative form (like git commits): "Implement user authentication", "Add validation for email field", "Write integration tests" ### ActiveForm Use present continuous: Subject "Run database migrations" → ActiveForm "Running database migrations" ### Status Workflow ``` pending → in_progress → completed ``` ### Dependencies ``` TaskCreate: "Implement User model" → #1 TaskCreate: "Add authentication service" → #2 TaskUpdate: #2 addBlockedBy [#1] ``` ### Task Granularity Create tasks that are completable in a focused session (1-4 hours), specific enough to know when done, independent or with clear dependencies, and verifiable. ## Execution Loop ``` while TaskList shows pending tasks: TaskList # Check available work TaskUpdate: #X status=in_progress # Claim next unblocked task # ... implementation ... TaskUpdate: #X status=completed # Mark complete ``` ## Cross-Session Coordination ### Including TaskList ID in Plan Files ```yaml --- title: Add user authentication task_list_id: a69ce44f-1559-4052-89e2-66605323adca --- ``` ### Importing in Another Session Use the `import-tasks` skill to import tasks from another session's TaskList. ### Parallel Subagent Execution Multiple agents can work on the same TaskList by importing it and claiming individual tasks. ## Relationship to Other Systems | System | Storage | Purpose | Persistence | |--------|---------|---------|-------------| | **TaskList** (this) | `~/.claude/tasks/` | Execution tracking | Session-scoped | | **file-todos** | `todos/` in repo | Detailed documentation | Git-committed | | **TodoWrite tool** | In-memory | Temporary tracking | None | **Recommended:** File-todos for detailed findings, TaskList for execution tracking. Link them via description references.
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.