agentsclimarketplace

Todo

Skill uwuclxdy/agenticat/skills/todo

Authors and normalizes tasks into `docs/todo.md`. Use when writing a todo list, capturing audit findings, or turning loose notes into pickup-cold-ready tasks.From its SKILL.md

Install
npx -y skills add uwuclxdy/agenticat --skill todo

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 5 stars5 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

3.7 KB, 820 tokens by cl100k_base, as published. Nobody here has run it

Todo

docs/todo.md is the per-repo task inbox.

Core Rule

Every task must be executable by a fresh agent with no session context. Self-contained: current behavior, expected behavior, and a verify step. If a task needs a decision the user hasn't made, AskUserQuestion before writing it down (AskUserQuestion is Claude Code's question tool; other harnesses ship their own native tool: opencode's question, gemini-cli's ask_user, Codex CLI's request_user_input. Use it if present, else fall back to a plain numbered message). Never park open questions inside a task.

Tasks say what needs to change and, sometimes, how. Never where. No file:line, no file paths. The executing agent locates the code itself since locations rot faster than intent.

State observed behavior as fact; label attributed causes as hypotheses. A task's "current behavior" is what you saw or reproduced. Any "why" you did not verify (an engine's timing, an API's state model, a component's intent) must read as a hypothesis (hypothesis:, suspected:), never as fact. Baking an unverified root cause into a task sends the executing agent to fix the wrong thing (a retry built on an inferred "the API hasn't synced" missed that the API never stored the data at all). If the cause is load-bearing for the fix, the verify step must confirm it first against the vendor source (swagger/docs/code) or a repro before the fix is built on it.

Size tasks by scope. Combine small related nits into one task; split anything too big for a single reviewable change into independent tasks. The unit is "one agent, one clean commit".

Two Formats, Picked by Source

Audit Findings / Bugs -> Punch-List

For audit results, contract violations, bug reports:

# <audit name> punch-list

<one-line provenance: what was audited against what, date>

## <component / feature area>

- [ ] <current behavior> -> <required behavior>. <optional how. ordering note if other items cascade from it>
  • Group by component or feature area, not by severity.
  • Note cascade order explicitly ("fix first: X findings depend on it").

Feature Ideas / Specs -> Checkbox Spec

For new features, enhancements, raw idea notes:

## <N>. <feature title>

<one-line intent if the title doesn't carry it>

### <surface: Backend / Frontend / TUI / CLI / Schema>
- [ ] <concrete, verifiable step>
  • Number tasks; subsection per surface touched; one reviewable change per checkbox.

Normalizing Raw Notes

When the user dumps loose notes ("inconsistent cursor..", "remove j/k"):

  1. Read the relevant code first. Resolve each note to specific files and current behavior.
  2. Ask clarifying questions for anything ambiguous (batch them, don't trickle).
  3. Rewrite as tasks in the matching format above. The original note text can be dropped once the task captures it fully.

Resolving

  • docs/todo.md holds OPEN work only. A landed item gets propagated to where it can't rot (a test that fails when the behavior changes, else the owning docs/ page or CLAUDE.md), then deleted from the list instead of left as a checked-off record. A ship narrative parked in the backlog drifts against the code it describes; nothing re-reads it to notice.
  • Never delete an unresolved or in-progress task without the user saying so. Deletion is reserved for a task you have confirmed landed and propagated; it is never a way to prune work you chose to skip.
  • When asked to "resolve the todo", route execution through your multi-task runner or workflows (one task each); this skill only owns the file.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most docs writing skills give in 820 tokens

Counted across 1,951 of the 3,904 authors here whose files we hold, read 2026-09-06

  • Use third-person for skill descriptionsin 54 of 1951, across 35 files
  • Start descriptions with Use whenin 43 of 1951, across 29 files
  • Run baseline scenarios before writing any skillin 40 of 1951, across 26 files
  • Use active voicein 40 of 1951, across 36 files
  • Map file responsibilities before defining tasksin 36 of 1951, across 29 files
  • Use checkbox syntax for tracking stepsin 35 of 1951, across 27 files
  • Ask one question at a timein 35 of 1951
  • Offer execution options after saving the planin 33 of 1951, across 24 files
  • Include complete code in every stepin 33 of 1951, across 27 files
  • Design units with clear boundaries and interfacesin 31 of 1951, across 23 files
  • Announce the skill usage at the startin 30 of 1951
  • Verify agent compliance after adding the skillin 29 of 1951, across 17 files

Said here and by no other author read

  • Ensure tasks are executable without session context
  • Ask user for missing decisions before writing tasks
  • State observed behavior as fact
  • Combine small related nits into one task
  • Split large tasks into independent units
  • Group audit findings by component or feature

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 611,884. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.