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.
Scanned 6/11/2026
Install via CLI
openskills install iliaal/ai-skills---
name: 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)
- **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:
```yaml
---
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.
## 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
No comments yet. Be the first to comment!
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
**Complete production-ready guide for Google Gemini embeddings API** This skill provides comprehensive coverage of the `gemini-embedding-001` model for generating text embeddings, including SDK usage, REST API patterns, batch processing, RAG integration with Cloudflare Vectorize, and advanced use cases like semantic search and document clustering. ---
Interview, source-challenge, verify, save, and ADR-gate fuzzy coding requests into Codex-ready implementation specs. Use when a feature, bugfix, refactor, migration, repo-wide change, or architecture task needs user-verified requirements, source-backed decisions, durable architecture decisions, acceptance criteria, validation commands, rollout notes, saved spec/ADR files, and a Codex execution prompt. Do not use when already fully specified or when the user wants direct implementation now.
Use when a repo needs CodeGraph plus ast-grep for Codex MCP setup, exploration, impact analysis, structural search, or safe refactor planning.