メニュー
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.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Reviews code changes before merging, through a correctness/security lens and an SRE operational-risk lens. Use when reviewing PRs, checking staged changes, reviewing diffs, code review, merge readiness check, assessing deploy or rollback risk, or validating changes before commit/push.
Dispatches a task to a Claude Fable 5 subagent with a prompt written the way Fable 5 wants to be prompted, and holds a back-and-forth with it across turns. Use when the user says /ask-fable, ask fable, fable, fable 5, send this to fable, hand this off to fable, get a Fable second opinion, or when a task sits at the top of the difficulty range: multi-hour or multi-day implementations, deep debugging, whole-repo review or bug hunts, dense technical screenshots, or ambiguous multithreaded requests where first-shot correctness matters.
Drafts a copy-pasteable prompt for Claude Fable 5 without dispatching anything. Use when the user says /prompt-fable, write me a fable prompt, draft a prompt for fable, help me prompt fable 5, or wants to hand a prompt to Fable somewhere else (the web app, another session, a colleague). For actually running the task, use the ask-fable skill instead.
User-invoked codebase recon via an ant-colony pattern. The moderator carves a large or unfamiliar codebase into disjoint territories, fans out cheap Haiku scout subagents that explore in parallel and dump full findings to /tmp scratchpads (returning only terse pointers), then one Sonnet verifier cross-checks every claim against the repo before reporting. Use to map an unfamiliar codebase or locate where something lives without bloating the main context.
User-invoked breadth check — convenes 3 specialist subagent personas to pressure-test a plan/decision/diff from angles you might have missed, surfacing framed positions + a dissent log. Intended to run AFTER the user has already reasoned through the problem, as a final "did we miss anything" sweep.
Serialize the current brainstorm/design discussion into a structured implementation spec and delegate the build to the cheaper "executor" subagent (Sonnet). Use when the user says to dispatch, delegate, hand off, or offload implementation to the executor after designing an approach together.
| name | ctask |
| description | 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. |
| user-invocable | false |
| allowed-tools | ["Bash(ctask:*)"] |
Use the ctask CLI to track tasks, dependencies, comments, and labels in a local SQLite database.
ctask must be on $PATH. Database auto-initializes on first use.
ctask create "Title" [--desc "Description"] [--priority low|medium|high|critical] [--project "name"]
ctask list [--status open|in_progress|blocked|done|cancelled] [--priority <p>] [--project <name>] [--all]
Default: excludes cancelled tasks. Use --all to show everything.
ctask show <id>
Returns task fields, labels, dependencies (blocked by / blocks), and comments.
ctask update <id> [--title "New title"] [--desc "New desc"] [--status <s>] [--priority <p>] [--project "name"]
ctask comment <id> <body> # Add comment
ctask comments <id> # List comments
ctask block <id> --by <blocker_id> # Task <id> is blocked by <blocker_id>
ctask unblock <id> --by <blocker_id> # Remove dependency
ctask deps <id> # Show what blocks/is blocked by
ctask label <id> <label> # Add label
ctask unlabel <id> <label> # Remove label
ctask labels <id> # List labels
ctask delete <id> # Permanently delete task
ctask search <query> # Search title and description
| 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 <id> --status done + ctask comment <id> "outcome" |
| "X depends on Y" / "can't do X until Y" | ctask block <X> --by <Y> |
| "I'm stuck on X" | ctask update <id> --status blocked + ctask comment <id> "why" |
| starts working on a task | ctask update <id> --status in_progress |
Always ctask list first to avoid creating duplicates.
update --status done + closing comment summarizing the outcome.update --status blocked + comment explaining why + block if another task is the blocker.--project to scope tasks when working across multiple projects.