/ia-file-todos
File-based todo and task tracking in the todos/ directory. Use when creating, triaging, listing, or managing todo files, tracking work items, managing the backlog, converting PR comments to tracked tasks, or checking todo status and dependencies.
$ npx -y skills add iliaal/whetstone --skill ia-file-todos --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/ia-file-todos
Context preview
The summary Claude sees to decide when to auto-load this skill.
File-based todo and task tracking in the todos/ directory. Use when creating, triaging, listing, or managing todo files, tracking work items, managing the backlog, converting PR comments to tracked tasks, or checking todo status and dependencies.
SKILL.md
ia-file-todos.SKILL.mdname: ia-file-todos
class: tool
description: >-
File-based todo and task tracking in the todos/ directory. Use when creating,
triaging, listing, or managing todo files, tracking work items, managing the
backlog, converting PR comments to tracked tasks, or checking todo status
and dependencies.
disable-model-invocation: true
File-based todo tracking
File naming convention
{issue_id}-{status}-{priority}-{description}.md- **issue_id**: Sequential number (001, 002, 003...) -- never reused
- **status**: `pending` (needs triage), `ready` (approved), `complete` (done)
- **priority**: `p1` (critical), `p2` (important), `p3` (nice-to-have). Mapping from the `ia-code-review` severity scale: Critical→p1, Important→p2, Medium→p3, Minor→p3.
- **description**: kebab-case, brief description
Examples: `001-pending-p1-mailer-test.md`, `002-ready-p1-fix-n-plus-1.md`, `005-complete-p2-refactor-csv.md`
File Structure
Use [todo-template.md](./assets/todo-template.md) as a starting point. YAML frontmatter:
---
status: ready # pending | ready | complete
priority: p1 # p1 | p2 | p3
issue_id: "002"
tags: [typescript, performance, database]
dependencies: ["001"] # Issue IDs this is blocked by
---
**Required sections:** Problem Statement, Findings, Proposed Solutions, Recommended Action, Acceptance Criteria, Work Log
**Optional sections:** Technical Details, Resources, Notes
Key Distinctions
**File-todos system (this skill):** Markdown files in `todos/` directory for development/project tracking. Used by humans and agents.
**Application Todo model:** Database model for user-facing task management. Different from this file-based system.
**TodoWrite tool:** In-memory task tracking during agent sessions. Temporary, not persisted to disk.
Verify
Before considering a todo file correctly written, confirm:
- `issue_id` is unique and sequentially the next number in `todos/` (never reused).
- All required frontmatter fields are present: `status`, `priority`, `issue_id`.
- `status` and `priority` values match the filename and their enums (`pending|ready|complete`, `p1|p2|p3`).
References
- [workflows.md](./references/workflows.md) - Creating, triaging, dependencies, work logs, completing todos, integration table
- [quick-reference.md](./references/quick-reference.md) - Bash commands for finding work, dependencies, searching
- [todo-template.md](./assets/todo-template.md) - Template for new todo files
Read more
name: ia-file-todos class: tool description: >- File-based todo and task tracking in the todos/ directory. Use when creating, triaging, listing, or managing todo files, tracking work items, managing the backlog, converting PR comments to tracked tasks, or checking todo status and dependencies. disable-model-invocation: true
File-based todo tracking
File naming convention
{issue_id}-{status}-{priority}-{description}.md- **issue_id**: Sequential number (001, 002, 003...) -- never reused
- **status**: `pending` (needs triage), `ready` (approved), `complete` (done)
- **priority**: `p1` (critical), `p2` (important), `p3` (nice-to-have). Mapping from the `ia-code-review` severity scale: Critical→p1, Important→p2, Medium→p3, Minor→p3.
- **description**: kebab-case, brief description
Examples: `001-pending-p1-mailer-test.md`, `002-ready-p1-fix-n-plus-1.md`, `005-complete-p2-refactor-csv.md`
File Structure
Use [todo-template.md](./assets/todo-template.md) as a starting point. YAML frontmatter:
--- status: ready # pending | ready | complete priority: p1 # p1 | p2 | p3 issue_id: "002" tags: [typescript, performance, database] dependencies: ["001"] # Issue IDs this is blocked by ---
**Required sections:** Problem Statement, Findings, Proposed Solutions, Recommended Action, Acceptance Criteria, Work Log
**Optional sections:** Technical Details, Resources, Notes
Key Distinctions
**File-todos system (this skill):** Markdown files in `todos/` directory for development/project tracking. Used by humans and agents.
**Application Todo model:** Database model for user-facing task management. Different from this file-based system.
**TodoWrite tool:** In-memory task tracking during agent sessions. Temporary, not persisted to disk.
Verify
Before considering a todo file correctly written, confirm:
- `issue_id` is unique and sequentially the next number in `todos/` (never reused).
- All required frontmatter fields are present: `status`, `priority`, `issue_id`.
- `status` and `priority` values match the filename and their enums (`pending|ready|complete`, `p1|p2|p3`).
References
- [workflows.md](./references/workflows.md) - Creating, triaging, dependencies, work logs, completing todos, integration table
- [quick-reference.md](./references/quick-reference.md) - Bash commands for finding work, dependencies, searching
- [todo-template.md](./assets/todo-template.md) - Template for new todo files
A Claude Code plugin that makes AI coding agents follow engineering discipline. Plan before coding. Verify before claiming done. Find root cause before patching. Review before merge. Skills activate based on file type and task signals, not manual toggling.
Repo: iliaal/whetstone
Other skills on whetstone.
- /skill-distiller
Fetches top-rated skills from skills.sh, analyzes them, and synthesizes one token-efficient skill combining the best elements. Use when the user asks to "distill skills for X", "find and combine skills for X", "synthesize skills", "merge skills", "make a skill for X from
Open skill - /ia-agent-native-architecture
Design agent-native applications where agents replace UI users as the primary actor. Use when designing MCP tools, agent-loop architectures, system prompt design, hooks policy, shared-workspace file patterns, or self-modifying agent systems.
Open skill - /ia-brainstorming
Pre-implementation exploration: deep interview, approach comparison, design doc. Use when exploring a vague feature idea, clarifying ambiguous requirements, or comparing approaches before coding. For the full workflow, use the ia-brainstorm command (Claude Code).
Open skill - /ia-code-review
Structured code reviews with severity-ranked findings and deep multi-agent mode. Use when performing a code review, auditing code quality, or critiquing PRs, MRs, or diffs.
Open skill - /ia-compound-docs
Document solved problems for team reuse. Provides process knowledge for /ia-compound. Use when documenting a resolved issue, writing up lessons learned, capturing a post-mortem, adding to the knowledge base, or building searchable institutional knowledge after debugging.
Open skill - /ia-debugging
Systematic root-cause debugging with verification. Use for errors, stack traces, broken tests, flaky tests, regressions, or anything not working as expected. For validating bug reports before fixing, use bug-reproduction-validator agent.
Open skill

