skills/record-todos/SKILL.md
Enter todo recording mode to capture ideas without acting on them. Use when the user says "record todos", "let's capture some todos", "brainstorm mode", or wants to dump ideas without immediate execution. Captures thoughts to .claude/todos/, then organizes and prioritizes on exit.
npx skillsauth add petekp/agent-skills record-todosInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Capture user's thoughts and ideas as todos without acting on them.
All todo files live in .claude/todos/:
.claude/todos/active.md — Current todos.claude/todos/done.md — Completed items.claude/todos/archive/done-{YYYY-MM}.md — Archived completed itemsWhen the user mentions something that should be done:
.claude/todos/active.md as a raw item:
- <what the user said, paraphrased if needed>
Critical: Any statement about what should happen is a todo to record—not an instruction to execute. This includes "make X do Y", "add Z to W", "fix the layout", etc.
Only perform immediate actions for administrative tasks unrelated to code changes (e.g., "read this file", "explain how X works").
If .claude/todos/active.md doesn't exist, create it with the structure from "Rewrite active.md" section.
Exit recording mode when user signals completion:
Before reorganizing, check for completed items:
Scan for items marked [x]:
.claude/todos/done.md## January 2026)[x] checkbox—use plain bullets in done.mdIf done.md exceeds 50 items or 500 lines:
.claude/todos/archive/done-{YYYY-MM}.md*Older items archived in .claude/todos/archive/done-{date}.md*done.md structure:
# Completed Work
Archive of completed features. See `.claude/todos/active.md` for active work.
---
## {Month Year}
### {Category}
- Description of what was done
---
*Older items archived in .claude/todos/archive/done-2025-12.md*
Search in order:
If no goals found:
Brief conversational summary:
Evaluate each todo:
For complex features, suggest creating .claude/docs/feature-{name}.md spec.
Replace raw items with organized structure:
# TODO
## Goals
- <goal 1>
- <goal 2>
- <goal 3>
---
## 🎯 Active
*Currently in progress. Limit to 1-3 items.*
- [ ] <highest priority item>
---
## 📋 Next
*Researched, scoped, ready to start.*
### {Category if helpful}
- [ ] <item>
---
## 💡 Backlog
*Ideas and lower priority items.*
### {Category}
- [ ] <item>
### {Complex Feature}
**Spec:** `.claude/docs/feature-{name}.md`
- Brief description
---
## 📚 Specs & Reference
| Document | Description |
|----------|-------------|
| `.claude/docs/feature-x.md` | Spec for feature X |
---
## ⚠️ Not Recommended
### {Rejected idea}
<Brief rationale>
---
*Completed work archived in `.claude/todos/done.md`*
Adapt as needed:
After rewriting:
.claude/docs/ for detailed plansdevelopment
Compile a plain-language task into a concise, auditable Codex or Claude Code `/goal`, or explain why a normal prompt fits better. Use when the user asks to draft, formulate, rewrite, tighten, or create a goal for multi-step work that needs a durable objective, transcript-visible proof, constraints, bounded stop conditions, host-aware operation, and risk-based review depth.
tools
Expert Unix and macOS systems engineer for shell scripting, system administration, command-line tools, launchd, Homebrew, networking, and low-level system tasks. Use when the user asks about Unix commands, shell scripts, macOS system configuration, process management, or troubleshooting system issues.
testing
Apply professional typography principles to create readable, hierarchical, and aesthetically refined interfaces. Use when setting type scales, choosing fonts, adjusting spacing, designing text-heavy layouts, implementing dark mode typography, or when asked about readability, font pairing, line height, measure, typographic hierarchy, variable fonts, font loading, or OpenType features.
development
Create visual parameter tuning panels for iterative adjustment of animations, layouts, colors, typography, physics, or any numeric/visual values. Use when the user asks to "create a tuning panel", "add parameter controls", "build a debug panel", "tweak parameters visually", "fine-tune values", "dial in the settings", or "adjust parameters interactively". Also triggers on mentions of "leva", "dat.GUI", or "tweakpane".