Back to list
howells

tasklist

by howells

Claude Code plugin. From idea to working implementation—explore, validate, plan, and build in one flow.

7🍴 0📅 Jan 24, 2026

SKILL.md


name: tasklist description: | Persistent task backlog that survives across sessions. Git-committed, always available. Use when asked to "add a task", "show my tasks", "update the backlog", "prioritize", or when managing what needs to be done across sessions. license: MIT metadata: author: howells argument-hint: <add|review|done> website: order: 16 desc: Task backlog summary: A simple markdown backlog that lives with your code. Add tasks, prioritize, mark done—persists across sessions. what: | Tasklist maintains a markdown file (docs/tasklist.md) with your backlog. It's git-tracked, so it persists across sessions and machines. Add tasks, prioritize, mark done—all from the terminal. Arc reads it to understand what's queued up. why: | Ideas slip away if you don't write them down. Tasklist is the simplest backlog that actually gets used—a markdown file, no setup, no separate tool. It travels with your code and Arc checks it to know what's next. decisions: - Markdown file over database. Readable, diffable, portable. - Git-committed. Backlog travels with your code. - Simple sections: Up Next, Backlog, Ideas. No Jira complexity.

Tasklist Workflow

Manage a persistent task backlog that survives across sessions. Git-committed, always available.

File Location

docs/tasklist.md

Process

Step 1: Check for Existing Tasklist

Use Read tool: docs/tasklist.md

If file exists: Read and proceed. If not exists: Create with template using Write tool.

Step 2: Determine Action

Parse arguments or ask:

  • "add [task]" → Add a new task
  • "review" → Show current list, discuss priorities
  • "prioritize" → Reorder tasks
  • "done [task]" → Mark complete (remove or archive)
  • No argument → Show list and ask what to do

For "Add"

Add to appropriate section:

## Backlog

- [ ] [New task description]

For "Review"

Show current tasklist. Ask: "Anything to add, remove, or reprioritize?"

For "Prioritize"

Present current order. Ask: "What should be the top 3 priorities?"

Reorder based on response.

For "Done"

Options:

  1. Remove — Delete from list entirely
  2. Archive — Move to "## Completed" section

Tasklist Format

# Tasklist

## Up Next
[Top priority items, 1-3 max]
- [ ] Task 1
- [ ] Task 2

## Backlog
[Everything else, roughly prioritized]
- [ ] Task 3
- [ ] Task 4
- [ ] Task 5

## Ideas
[Things to consider, not committed]
- Task idea 1
- Task idea 2

## Completed
[Optional: archived done items]
- [x] Done task 1 (2026-01-14)

Step 3: Save Changes

git add docs/tasklist.md
git commit -m "docs: update tasklist"

Interop

  • /arc:suggest reads tasklist as primary source
  • /arc:ideate can add follow-up tasks
  • /arc:implement can add discovered tasks
  • Any workflow can add to tasklist

Score

Total Score

70/100

Based on repository quality metrics

SKILL.md

SKILL.mdファイルが含まれている

+20
LICENSE

ライセンスが設定されている

+10
説明文

100文字以上の説明がある

+10
人気

GitHub Stars 100以上

0/15
最近の活動

3ヶ月以内に更新がある

0/10
フォーク

10回以上フォークされている

0/5
Issue管理

オープンIssueが50未満

+5
言語

プログラミング言語が設定されている

+5
タグ

1つ以上のタグが設定されている

0/5

Reviews

💬

Reviews coming soon