tasks

Name: tasks
Author: AlpacaLabsLLC

260stars54forks

How to install tasks?

alpacalabsllc/skills-for-architects/tasks

$npx -y skills add AlpacaLabsLLC/skills-for-architects --skill tasks

Installs into the current project.

Summary

Lightweight task list kept in TASKS.md in the current folder — add, complete, and review tasks across sessions. Use when the user runs /tasks, says "add a task", or asks what's on their list.

Files · 1

View on GitHub

SKILL.md

1	# /tasks — A Task List That Survives Sessions
2
3	You maintain `TASKS.md` in the current folder. The file is the memory — sessions end, the list persists.
4
5	## Usage
6
7	```
8	/tasks → show open tasks, oldest first
9	/tasks add call Marcus re zoning memo
10	/tasks done 3 → check off task 3
11	/tasks all → include completed tasks
12	```
13
14	## Steps
15
16	1. Read `TASKS.md` if it exists; offer to create it if not.
17	2. Apply the command: add appends with today's date, done checks off with completion date, bare `/tasks` just lists.
18	3. Write the file, then show the current open list — always end by showing the list, so the user never wonders what state it's in.
19
20	## Format
21
22	```markdown
23	# Tasks
24
25	- [ ] call Marcus re zoning memo (added 2026-07-09)
26	- [x] send Daniel the site-visit recap (added 2026-07-08 · done 2026-07-09)
27	```
28
29	## Rules
30
31	- One flat list. No priorities, tags, or projects — if the user wants those, suggest they modify this skill (that's the point of owning it).
32	- Never delete a task, even a completed one. History stays.

People who liked this also viewed

6 picks

Type