メニュー
Operate stable Taskwarrior `task` CLI: list/filter/report/add/modify/done/delete, projects, tags, due dates, recurrence, contexts, sync, import/export, config, UDAs, hooks, aliases, troubleshooting.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | taskwarrior |
| description | Operate stable Taskwarrior `task` CLI: list/filter/report/add/modify/done/delete, projects, tags, due dates, recurrence, contexts, sync, import/export, config, UDAs, hooks, aliases, troubleshooting. |
| metadata | {"target-taskwarrior-version":"3.4.2 stable","generated-on":"2026-05-15"} |
Use task safely. Target 3.4.2 stable. No legacy syntax unless user asks migration.
~/.taskrc or ~/.task..taskwarrior/taskrc in cwd/parent => project-local.$DOTFILES/cmd/task shim. Bootstrap puts it before real task.task OK only when shim active; shim finds .taskwarrior/taskrc, exports TASKRC/TASKDATA, delegates real Taskwarrior.TASKRC="$PWD/.taskwarrior/taskrc" TASKDATA="$PWD/.taskwarrior/data" task ...task may be another tool. Verify real Taskwarrior with task diagnostics.If user asks project-local and no .taskwarrior/taskrc, propose + confirm before files:
mkdir -p .taskwarrior/data
printf 'data.location=%s\nconfirmation=1\n' "$PWD/.taskwarrior/data" > .taskwarrior/taskrc
Git repo: ensure .taskwarrior/ ignored. Do not edit .env, .envrc, dotenv files, shell profiles, package scripts.
Global task: before mutation, state no project-local store found; ask/confirm.
references/command-router.mdreferences/selectors-and-filters.mdreferences/read-and-report.mdreferences/mutate-tasks.mdreferences/safety-and-files.md firstreferences/data-config-and-sync.mdreferences/troubleshooting.mdassets/command-groups.jsonAgent files:
out_dir="$([ -d .codex ] && printf '%s' '.codex/taskwarrior' || printf '%s' '.taskwarrior/agent')"
mkdir -p "$out_dir"
Use for exports/backups/diagnostics/scratch. .taskwarrior/ root is local store, not committed docs.
.taskwarrior/taskrc or project-local request => project-local; else global only after disclosure.command -v task, task diagnostics, task --version.task next, task <filter> list, task <id> information, task context show, task reports.task <filter> <command> [mods|args].Never broad write (modify, done, delete, purge) without explicit scope + safety. Quote spaces, parens, regex, or, xor, shell metachars, user text.
Unified scoped code review + parent-owned fix loop. Use for /review-loop, review until clean, code review with fixes, or modes: web, server, database, node, planning.
Orchestrate implementation work from intake to closeout. Use when the user asks to run a task through a consistent work flow, plan first, turn a plan into Taskwarrior tasks, execute task-by-task, verify, review, and optionally prepare commits. Trigger phrases include workstream, 작업흐름, 작업 흐름, 기획부터 태스크화, 계획 세우고 구현, and 태스크화해서 구현.
Convert implementation plans, Markdown checklists, and work items into a Taskwarrior task queue. Use when the user asks to queue, taskify, 태스크화, 작업 큐, 작업 등록, plan to tasks, checklist to tasks, or when workstream needs a Taskwarrior draft from plan Work Items. Shows a concise user-language summary before mutation and delegates command safety to the taskwarrior skill.
Close out implementation work by checking plan completion, Taskwarrior queue status, validation results, review findings, git status, residual risk, and commit readiness. Use when the user asks to close, finish, wrap up, 마감, 완료 정리, 종료 정리, or when workstream reaches its closeout phase. Does not commit by itself; delegates commits to git-commit only when requested.
Map a repository or working directory before implementation. Use when the user asks to survey, scan, inspect, orient, 구조 파악, 훑어보기, 작업 전 파악, or when workstream needs a pre-implementation map of project structure, package manager, commands, tests, local apps, ownership boundaries, and risk areas. Produces concise findings and recommended next checks without making code changes.
Choose and run validation for code, docs, config, UI, API, database, refactor, and bugfix work. Use when the user asks to verify, validate, test, confirm, check, 검증, 확인, 테스트, or when workstream needs a consistent validation matrix before marking tasks done. Produces focused checks, pass/fail criteria, and exact skipped or blocked validation gaps.