tasks

Name: tasks
Author: chacosoldier

29stars6forks

How to install tasks?

chacosoldier/compabob/tasks

$npx -y skills add chacosoldier/compabob --skill tasks

Installs into the current project.

Summary

Show a single aggregated task view pulled from across the vault and the brief queue. Use for "/tasks", "what are my open tasks", "what's overdue", or "/tasks done [id]" to complete one.

Files · 1

View on GitHub

SKILL.md

1	# Tasks
2
3	One view of everything open, gathered from where tasks actually live.
4
5	## Sources
6
7	- `- [ ]` checkboxes anywhere in `vault/` (meeting notes, project notes, daily notes).
8	- `memory/topics/brief-queue.md` — items captured via "remember this".
9	- Follow-ups tracked by the `comms-meetings` agent.
10
11	## Steps
12
13	1. Collect open `- [ ]` items via `Grep` across `vault/`. Record each item's source file.
14	2. Group by urgency: Overdue, Due today, This week, Next week, Someday (no date).
15	3. Deduplicate: if the same task appears in two places, show it once and note both sources.
16	4. Present the grouped list. Each line: the task, its due date if any, and a link to its source file.
17
18	## Commands
19
20	- `/tasks` — full refresh and grouped view.
21	- `/tasks done [text or id]` — find the matching `- [ ]`, change it to `- [x]` with a completion date, confirm.
22	- `/tasks add [text]` — add a task; route it through the `second-brain` intake gate so it does not duplicate an existing one.
23
24	## Output
25
26	Overdue first, always. If nothing is overdue, say so plainly. Keep it a scannable list, not prose.

People who liked this also viewed

6 picks

Type