Menu

Individual skill

todos

0upvotes

Use when the user asks for a shared plan, a task needs at least three substantive execution steps, or a loose TODO is pending. Without an explicit plan request, not for one-shot answers or checks, or one- to two-step work that is not already in the list.

packages/pi-todos/skills/todos/SKILL.md

Read pinned source

Source commit 519286befe0f15cc2dd270e251ecd8cdb9d0a01c

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 8, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
7,973
Repository last updated
Nov 7, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Chat TODO plan

## What it is

- A plan **scoped to this chat** — your tasks for the conversation. Shown to the user in the Todo
  panel; lives with the session (not committed to the repo).
- **Group = task, item = step.** One user ask = one group; its title is the *outcome* ("Fix login
  redirect"), not the process. The steps inside are the items — each has a **title**, a **status**
  (`pending` → `in_progress` → `done`), and an optional **note**. The note is **agent-facing working
  detail** — the human's default plan view shows titles + status and keeps notes behind a disclosure —
  so it's where your own tracking, reminders, and the done-criterion live (e.g. "login e2e green"),
  never a place the user must read to follow along. A task's own status is never stored — it derives from its steps.
- **Loose items are the shared raw-input queue — and they sit at the END of the plan.** Both sides
  write there: the user adds from the UI, and you may drop an unprocessed note with `todo_add` (no