home / skills / petekp / agent-skills / record-todos

record-todos skill

/skills/record-todos

This skill records user ideas as todos in .claude/todos/active.md without execution, enabling later organization and prioritization.

npx playbooks add skill petekp/agent-skills --skill record-todos

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
4.7 KB
---
name: record-todos
description: 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.
---

# Todo Recording Mode

Capture user's thoughts and ideas as todos without acting on them.

## File Locations

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 items

## During Recording

When the user mentions something that should be done:

1. **Acknowledge briefly** — "Noted." or "Got it."
2. **Append to `.claude/todos/active.md`** as a raw item:
   ```
   - <what the user said, paraphrased if needed>
   ```
3. **Do NOT**:
   - Start implementing
   - Ask clarifying questions unless completely unclear
   - Suggest solutions or alternatives
   - Reorganize the file yet

**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 Triggers

Exit recording mode when user signals completion:
- "ok all done", "done recording", "that's all", "let's review", "end recording"

## On Exit: Summarize, Prioritize, Archive

### 1. Archive Completed Items

**Before reorganizing**, check for completed items:

#### Move completed items to done.md

Scan for items marked `[x]`:
1. Create/update `.claude/todos/done.md`
2. Move completed items under dated section (e.g., `## January 2026`)
3. Remove `[x]` checkbox—use plain bullets in done.md
4. Remove from active.md

#### Archive if too large

If done.md exceeds 50 items or 500 lines:
1. Create `.claude/todos/archive/done-{YYYY-MM}.md`
2. Move older items (keep last 2 weeks in done.md)
3. Add note: `*Older items archived in .claude/todos/archive/done-{date}.md*`

**done.md structure:**
```markdown
# 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*
```

### 2. Find Project Goals

Search in order:
1. **CLAUDE.md** — "Goals", "Product Vision", "Objectives" sections
2. **.claude/todos/active.md** — Goals section at top

If no goals found:
- Tell user: "I couldn't find documented project goals. Before prioritizing, let's define what success looks like."
- Establish 3-5 high-level goals
- Record in active.md Goals section
- Then proceed

### 3. Summarize

Brief conversational summary:
- How many items captured
- Themes or clusters noticed
- Related items that could combine
- Items complex enough for a spec document

### 4. Prioritize Against Goals

Evaluate each todo:
- **🎯 Active** — Work on RIGHT NOW (1-3 max)
- **📋 Next** — Ready to start when Active is done
- **💡 Backlog** — Lower priority, needs scoping
- **⚠️ Not Recommended** — Decided against (include rationale)

For complex features, suggest creating `.claude/docs/feature-{name}.md` spec.

### 5. Rewrite active.md

Replace raw items with organized structure:

```markdown
# 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:**
- Skip empty sections
- Items needing >3 lines → spec document
- Keep under ~100 lines of active content

### 6. Confirm

After rewriting:
- Items per priority tier
- Items moved to done.md
- Specs to create for complex features
- Ask if prioritization makes sense

## Principles

1. **active.md is for WHAT** — Scannable, action-oriented
2. **Specs are for HOW** — `.claude/docs/` for detailed plans
3. **done.md is for history** — Archive, don't delete
4. **Link, don't embed** — Reference specs
5. **Keep under 100 lines** — Move to spec or done.md if long

Overview

This skill enters a focused todo recording mode to capture ideas, requests, and action items without taking immediate action. It appends raw todos to .claude/todos/active.md while preventing implementation, solutioning, or unnecessary questions. On exit, it summarizes, archives completed items, discovers project goals, prioritizes todos against those goals, and rewrites active.md into a scannable prioritized board.

How this skill works

While recording, any user statement that implies work is converted into a raw bullet appended to .claude/todos/active.md and acknowledged briefly (e.g., "Noted."). The skill avoids starting work, proposing fixes, or asking clarifying questions unless the input is completely unclear. When the user signals exit, the skill moves checked items to done.md (and archives if large), finds or prompts for project goals, summarizes themes, assigns priority tiers, and rewrites active.md into an organized TODO structure.

When to use it

  • You want to dump ideas quickly without starting implementation.
  • During brainstorming sessions or design reviews to capture action items.
  • When stakeholders give many requests and you need a neutral intake.
  • To collect todos across meetings before planning or sprinting.
  • If you need a structured, reviewable list before prioritization.

Best practices

  • Acknowledge each input briefly and append it verbatim or lightly paraphrased.
  • Do not implement, propose solutions, or reorganize during recording.
  • Mark completed items with [x] so they are moved to done.md on exit.
  • Keep active.md focused on WHAT; create .claude/docs/ specs for HOW.
  • Limit the final active.md to roughly 100 lines; move long items to specs or done.md.

Example use cases

  • Run during a product brainstorm: capture feature ideas and follow-ups without debating feasibility.
  • Collect todos during a UX review so designers and engineers can prioritize later.
  • Capture ad-hoc requests from stakeholders during a demo to avoid distraction.
  • Aggregate engineer notes and bugs mentioned in a standup for later triage.
  • Quickly record feature requests from user interviews for later scoping.

FAQ

What counts as a todo while recording?

Any statement that describes something that should be done (e.g., "fix layout", "add X to Y", "investigate Z") should be recorded as a todo.

When are todos moved to done.md?

On exit, items marked with [x] are moved into .claude/todos/done.md under a dated section and removed from active.md.

What if there are no documented project goals?

The skill will tell you it couldn't find goals, prompt to define 3–5 high-level goals, record them in active.md, and then continue prioritization.