# Ctask > Manages tasks using the ctask CLI wrapper over a local SQLite database. Use when tracking work items, creating tasks, managing dependencies, adding comments, labeling, or reviewing task status. Triggers on task tracking, ticket management, work planning, backlog management. - Skill: `majiayu000/ctask` (Agent Skill, multi-file: 2 files) - Install (CLI): `npx skillmds add majiayu000/ctask` - Raw SKILL.md: https://api.skillmd.com/api/skills/majiayu000/ctask/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Product & Planning - Author: majiayu000 (https://skillmd.com/u/majiayu000) - Updated: 2026-09-09 - Page: https://skillmd.com/skills/majiayu000/ctask --- # ctask — Local Task Tracker Use the `ctask` CLI to track tasks, dependencies, comments, and labels in a local SQLite database. ## Prerequisites `ctask` must be on `$PATH`. Database auto-initializes on first use. ## CLI Reference ### Create a task ```bash ctask create "Title" [--desc "Description"] [--priority low|medium|high|critical] [--project "name"] ``` ### List tasks ```bash ctask list [--status open|in_progress|blocked|done|cancelled] [--priority

] [--project ] [--all] ``` Default: excludes cancelled tasks. Use `--all` to show everything. ### Show task details ```bash ctask show ``` Returns task fields, labels, dependencies (blocked by / blocks), and comments. ### Update a task ```bash ctask update [--title "New title"] [--desc "New desc"] [--status ~~] [--priority~~

] [--project "name"] ``` ### Comments ```bash ctask comment # Add comment ctask comments # List comments ``` ### Dependencies ```bash ctask block --by # Task is blocked by ctask unblock --by # Remove dependency ctask deps # Show what blocks/is blocked by ``` ### Labels ```bash ctask label # Add label ctask unlabel # Remove label ctask labels # List labels ``` ### Other ```bash ctask delete # Permanently delete task ctask search # Search title and description ``` ## When to Act | User says... | Do this | |-------------|---------| | "track this" / "add a task" / "remember to..." | `ctask create` — infer title from context, ask project if ambiguous | | "what's open" / "what am I working on" | `ctask list --status open` | | "I finished X" / marks work done | `ctask update --status done` + `ctask comment "outcome"` | | "X depends on Y" / "can't do X until Y" | `ctask block --by ` | | "I'm stuck on X" | `ctask update --status blocked` + `ctask comment "why"` | | starts working on a task | `ctask update --status in_progress` | Always `ctask list` first to avoid creating duplicates. ## Enums - **Statuses**: open, in_progress, blocked, done, cancelled - **Priorities**: low, medium, high, critical (list output sorts by priority desc, then date desc) ## Guidelines - Always quote titles with double-quotes to avoid shell issues. - Comments are engineering logs, not status updates: - Bad: "done" / "updated status" - Good: "Fixed by switching to connection pooling — was hitting PG max_connections under load" - When completing: `update --status done` + closing comment summarizing the outcome. - When blocked: `update --status blocked` + comment explaining why + `block` if another task is the blocker. - Use `--project` to scope tasks when working across multiple projects.