メニュー
Manage personal tasks using OmniFocus via the `of` CLI. Use when discussing tasks, projects, inbox processing, GTD workflow, or adding/organizing to-dos.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | task-management |
| description | Manage personal tasks using OmniFocus via the `of` CLI. Use when discussing tasks, projects, inbox processing, GTD workflow, or adding/organizing to-dos. |
Manage the user's personal tasks and projects through the of CLI. Apply GTD principles to clarify work.
Use for: Tasks, inbox processing, project planning, follow-ups, meeting action items Not for: Code implementation planning, technical architecture
of inbox ls # List inbox items
of inbox count # Get inbox count
of inbox add "Task name" # Quick capture
of inbox add "Task" --note "Details" --due "Friday" --flagged
of task ls # List all tasks
of task ls --flagged # Flagged tasks only
of task ls --project "ProjectName"
of task ls --tag "waiting"
of task create "Task" --project "Project" --tag "home" --due "tomorrow"
of task view "task-id"
of task update "task-id" --flagged --due "next week"
of task delete "task-id"
of project ls # List active projects
of project ls --folder "Work"
of project create "Project Name" --folder "Area" --sequential
of project update "project-id" --status "on hold"
of search "keyword" # Search tasks by name/note
of perspective ls # List perspectives
of perspective view "Today" # View tasks in perspective
of tag ls # List tags with usage
of folder ls # Folder hierarchy
Flexible: today, tomorrow, Friday, next week, in 3 days, 2024-01-15, Jan 15
Transform vague into concrete:
| Vague | Concrete |
|---|---|
| "Follow up with client" | "Draft email about contract terms" |
| "Handle the thing" | "Call vendor about pricing" |
| "Work on presentation" | "Outline three key points for deck" |
Focus on effort, not results:
| Outcome-focused | Controllable |
|---|---|
| "Close the deal" | "Send proposal by Tuesday" |
| "Get approval" | "Submit complete proposal for review" |
Project vs Single Action: If multiple steps required, it's a project. Always identify the immediate next action first.
Quick Capture: of inbox add "The thing they mentioned"
Process Inbox: Review each item, decide: delete, do now, delegate, defer, or file with of task update "item-id" --project "Relevant Project"
Weekly Review: of project ls + of task ls --tag "waiting" + of perspective view "Review"
Frame naturally: "Sounds like the next step is drafting that email?" / "Should I add that to your inbox?"
Avoid: "Here's your GTD structure with contexts..."
Analyze unresolved PR review comments and recommend whether to fix, skip, or optionally address each. Use when a PR has review comments and you need a verdict on how to respond.
Create a git commit. Use when ready to commit changes. Creates conventional commit messages focused on why, not what.
Open a pull request for the current branch. Use when code is ready for review. Creates concise descriptions focused on the problem being solved.
Karpman Drama Triangle analysis for communication and conflict. Use when reviewing emails, proposals, or scripts for hidden drama dynamics, coaching difficult conversations, analyzing interpersonal conflict, or reframing victim/hero/villain patterns into Creator/Challenger/Coach alternatives.
Audit codebase, assess technical debt, analyze architecture, find structural problems. Use when evaluating code health, planning refactors, or need architectural review. Covers brittleness, coupling, complexity.
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.