anthropics/knowledge-work-plugins

task-management

Simple task management using a shared TASKS.md file.

ソースを見る

使い方

  1. インストールコマンドをコピーし、自分の環境へ導入する前にソースを確認します。
  2. 必要なツール、認証情報、対応環境を原文で確認します。
  3. 入力と成果物を指定し、出力を資料と照合します。
npx skills add https://github.com/anthropics/knowledge-work-plugins --skill task-management

開始前の確認

  • 導入にはモデル契約、API枠、ファイルへのアクセス許可は含まれません。
  • スター数や導入数は活動の指標であり、独立した品質・安全性試験ではありません。
リポジトリの原文

見出し、例、コード、表、リンク、参照画像を含む原文を表示しています。

Task Management

Tasks are tracked in a simple TASKS.md file that both you and the user can edit.

File Location

Always use `TASKS.md` in the current working directory.

  • If it exists, read/write to it
  • If it doesn't exist, create it with the template below

Dashboard Setup (First Run)

A visual dashboard is available for managing tasks and memory. On first interaction with tasks:

  1. Check if dashboard.html exists in the current working directory
  2. If not, copy it from ${CLAUDE_PLUGIN_ROOT}/skills/dashboard.html to the current working directory
  3. Inform the user: "I've added the dashboard. Run /productivity:start to set up the full system."

The task board:

  • Reads and writes to the same TASKS.md file
  • Auto-saves changes
  • Watches for external changes (syncs when you edit via CLI)
  • Supports drag-and-drop reordering of tasks and sections

Format & Template

When creating a new TASKS.md, use this exact template (without example tasks):

markdown
# Tasks

## Active

## Waiting On

## Someday

## Done

Task format:

  • - [ ] **Task title** - context, for whom, due date
  • Sub-bullets for additional details
  • Completed: - [x] ~~Task~~ (date)

How to Interact

When user asks "what's on my plate" / "my tasks":

  • Read TASKS.md
  • Summarize Active and Waiting On sections
  • Highlight anything overdue or urgent

When user says "add a task" / "remind me to":

  • Add to Active section with - [ ] **Task** format
  • Include context if provided (who it's for, due date)

When user says "done with X" / "finished X":

  • Find the task
  • Change [ ] to [x]
  • Add strikethrough: ~~task~~
  • Add completion date
  • Move to Done section

When user asks "what am I waiting on":

  • Read the Waiting On section
  • Note how long each item has been waiting

Conventions

  • Bold the task title for scannability
  • Include "for [person]" when it's a commitment to someone
  • Include "due [date]" for deadlines
  • Include "since [date]" for waiting items
  • Sub-bullets for additional context
  • Keep Done section for ~1 week, then clear old items

Extracting Tasks

When summarizing meetings or conversations, offer to add extracted tasks:

  • Commitments the user made ("I'll send that over")
  • Action items assigned to them
  • Follow-ups mentioned

Ask before adding - don't auto-add without confirmation.

タスクに関連する項目

同じリポジトリから

関連する Skills

すべての Skills
anthropics
公式

data-visualization

Create effective data visualizations with Python (matplotlib, seaborn, plotly). Use when building charts, choosing the right chart type for a dataset, creating publication-quality figures, or applying design principles like accessibility and color theory.

導入数
3
GitHub Stars
3.2万
更新日
10月22日
anthropics
公式

ux-copy

Write or review UX copy — microcopy, error messages, empty states, CTAs. Trigger with "write copy for", "what should this button say?", "review this error message", or when naming a CTA, wording a confirmation dialog, filling an empty state, or writing onboarding text.

導入数
3
GitHub Stars
3.2万
更新日
10月22日
anthropics
公式

daily-briefing

Morning rundown - today's meetings with account context, opps closing soon with stale flags, waiting customer emails, and the day's top actions. Use when the user says "daily briefing", "daily brief", "morning briefing", "what's my day", "what's on my plate today", "prep my day", "start my day", "morning rundown", or on a schedule.

導入数
2
GitHub Stars
3.2万
更新日
10月22日
anthropics
公式

incident-response

Run an incident response workflow — triage, communicate, and write postmortem. Trigger with "we have an incident", "production is down", an alert that needs severity assessment, a status update mid-incident, or when writing a blameless postmortem after resolution.

導入数
2
GitHub Stars
3.2万
更新日
10月22日