How do I install the To Dos skill?

Run npx skillmds@latest add mike-diff/to-dos-3 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is To Dos safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with To Dos?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is To Dos free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published To Dos?

mike-diff (@mike-diff) published this skill. Their other Agent Skills are listed on their SkillMD profile.

To Dos by mike-diff — Agent Skill

Name: To Dos
Author: mike-diff

File contents

Technical Implementation Task Generator

Requires the task tools. Claude Code 2.1.233+ removes TaskCreate/TaskUpdate on Opus 4.8, the Claude 5 family, and newer models unless CLAUDE_CODE_ENABLE_TODO_TOOLS=1 is set (this repo's settings.json sets it). If the tools are still unavailable, stop and report that instead of generating tasks.

Generate detailed, actionable developer tasks using Claude Code's native task primitives (TaskCreate, TaskUpdate) for implementation tracking.

Core Principles

Explore-First — search the codebase before planning
Clarify-Before-Planning — ask questions when ambiguous
Junior-Developer Friendly — enough detail to execute independently
Rich Descriptions — use TaskCreate's multi-line description field
Dependency Tracking — use addBlocks/addBlockedBy for ordering
Minimal Tasks — consolidate related changes

Workflow Phases

EnterPlanMode at the start — exploration and design are read-only. ExitPlanMode before creating tasks to present the plan and get explicit approval.

Parse — extract core functionality, scope, type, tech hints
Explore — search codebase, find patterns, detect environment
Clarify — AskUserQuestion (max 5), wait for answer
Plan — design the task structure in read-only mode
Present — ExitPlanMode to show full task plan, wait for approval
Generate — call TaskCreate + TaskUpdate after approval

Task Format (Quick Reference)

TaskCreate:
  subject: "[domain] Action description"
  description: |
    ## Context
    [Why this task exists]
    ## Implementation Guidance
    [Signatures, patterns, pseudocode]
    ## Files
    - **Modify:** `path/to/file` - [what changes]
    ## Acceptance Criteria
    - [ ] [Testable criterion]

Always end with verification tasks (dev checks, unit tests, browser tests if UI modified).

Full Workflow

For complete phase-by-phase instructions, task format details, dependency tracking patterns, owner assignment, and integration with /agent-team:dev, read references/workflow.md.

---name: to-dos-3description: Generate detailed, actionable developer tasks using TaskCreate with rich descriptions, dependency tracking, and owner assignment.---# Technical Implementation Task Generator> **Requires the task tools.** Claude Code 2.1.233+ removes `TaskCreate`/`TaskUpdate`> on Opus 4.8, the Claude 5 family, and newer models unless> `CLAUDE_CODE_ENABLE_TODO_TOOLS=1` is set (this repo's `settings.json` sets it).> If the tools are still unavailable, stop and report that instead of generating tasks.Generate detailed, actionable developer tasks using Claude Code's native task primitives (`TaskCreate`, `TaskUpdate`) for implementation tracking.<role>You are a senior technical lead creating implementation tasks for developers. You break down implementation requests into clear, ordered tasks with enough context that a junior developer (or teammate subagent) could execute them without additional context.</role><implementation_request>$ARGUMENTS</implementation_request>---## Core Principles1. **Explore-First** — search the codebase before planning2. **Clarify-Before-Planning** — ask questions when ambiguous3. **Junior-Developer Friendly** — enough detail to execute independently4. **Rich Descriptions** — use TaskCreate's multi-line `description` field5. **Dependency Tracking** — use `addBlocks`/`addBlockedBy` for ordering6. **Minimal Tasks** — consolidate related changes---## Workflow Phases`EnterPlanMode` at the start — exploration and design are read-only. `ExitPlanMode` before creating tasks to present the plan and get explicit approval.1. **Parse** — extract core functionality, scope, type, tech hints2. **Explore** — search codebase, find patterns, detect environment3. **Clarify** — `AskUserQuestion` (max 5), wait for answer4. **Plan** — design the task structure in read-only mode5. **Present** — `ExitPlanMode` to show full task plan, wait for approval6. **Generate** — call `TaskCreate` + `TaskUpdate` after approval---## Task Format (Quick Reference)```TaskCreate: subject: "[domain] Action description" description: | ## Context [Why this task exists] ## Implementation Guidance [Signatures, patterns, pseudocode] ## Files - **Modify:** `path/to/file` - [what changes] ## Acceptance Criteria - [ ] [Testable criterion]```Always end with verification tasks (dev checks, unit tests, browser tests if UI modified).---## Full WorkflowFor complete phase-by-phase instructions, task format details, dependency tracking patterns, owner assignment, and integration with `/agent-team:dev`, read [references/workflow.md](references/workflow.md).

Frequently asked questions

To Dos