format-todo-list
The format-todo-list Claude Code skill transforms todo items into properly structured lists for the TodoWrite tool by validating status values (pending, in_progress, completed) and generating contextual active form descriptions through verb conversion rules such as converting "Run" to "Running" or "Create" to "Creating." Use this skill when initializing phase checklists in orchestrators, updating task statuses, or maintaining consistent formatting for progress tracking across multi-phase workflows.
git clone --depth 1 https://github.com/maslennikov-ig/claude-code-orchestrator-kit /tmp/format-todo-list && cp -r /tmp/format-todo-list/.claude/skills/format-todo-list ~/.claude/skills/format-todo-listSKILL.md
# Format Todo List
Create properly structured todo lists for TodoWrite tool with correct status and activeForm fields.
## When to Use
- Creating initial phase checklists in orchestrators
- Updating todo list status
- Ensuring consistent todo formatting
- Generating progress tracking lists
## Instructions
### Step 1: Receive Todo Items
Accept array of todo items with status.
**Expected Input**:
```json
{
"todos": [
{
"content": "Phase 1: Discovery",
"status": "completed"
},
{
"content": "Phase 2: Implementation",
"status": "in_progress"
},
{
"content": "Phase 3: Validation",
"status": "pending"
}
]
}
```
### Step 2: Generate Active Forms
Create activeForm for each todo based on content.
**Rules**:
- Convert imperative to present continuous
- "Run X" → "Running X"
- "Create X" → "Creating X"
- "Fix X" → "Fixing X"
- "Validate X" → "Validating X"
### Step 3: Validate Status
Ensure status is valid TodoWrite value.
**Valid Statuses**:
- `pending`: Not started
- `in_progress`: Currently active
- `completed`: Finished
### Step 4: Format for TodoWrite
Structure data for TodoWrite tool.
**Expected Output**:
```json
{
"todos": [
{
"content": "Phase 1: Discovery",
"status": "completed",
"activeForm": "Discovering and analyzing"
},
{
"content": "Phase 2: Implementation",
"status": "in_progress",
"activeForm": "Implementing changes"
},
{
"content": "Phase 3: Validation",
"status": "pending",
"activeForm": "Validating results"
}
]
}
```
## Error Handling
- **Invalid Status**: Return error listing valid statuses
- **Missing Content**: Return error for empty content
- **Empty Array**: Return error requesting at least one todo
## Examples
### Example 1: Phase Checklist
**Input**:
```json
{
"todos": [
{"content": "Phase 0: Pre-flight validation", "status": "completed"},
{"content": "Phase 1: Bug detection", "status": "in_progress"},
{"content": "Phase 2: Bug fixes", "status": "pending"},
{"content": "Phase 3: Verification", "status": "pending"}
]
}
```
**Output**:
```json
{
"todos": [
{
"content": "Phase 0: Pre-flight validation",
"status": "completed",
"activeForm": "Validating pre-flight checks"
},
{
"content": "Phase 1: Bug detection",
"status": "in_progress",
"activeForm": "Detecting bugs"
},
{
"content": "Phase 2: Bug fixes",
"status": "pending",
"activeForm": "Fixing bugs"
},
{
"content": "Phase 3: Verification",
"status": "pending",
"activeForm": "Verifying fixes"
}
]
}
```
### Example 2: Simple Task List
**Input**:
```json
{
"todos": [
{"content": "Run type check", "status": "completed"},
{"content": "Run build", "status": "completed"},
{"content": "Run tests", "status": "in_progress"}
]
}
```
**Output**:
```json
{
"todos": [
{
"content": "Run type check",
"status": "completed",
"activeForm": "Running type check"
},
{
"content": "Run build",
"status": "completed",
"activeForm": "Running build"
},
{
"content": "Run tests",
"status": "in_progress",
"activeForm": "Running tests"
}
]
}
```
### Example 3: Priority-Based List
**Input**:
```json
{
"todos": [
{"content": "Fix critical bugs", "status": "completed"},
{"content": "Fix high-priority bugs", "status": "in_progress"},
{"content": "Fix medium-priority bugs", "status": "pending"}
]
}
```
**Output**:
```json
{
"todos": [
{
"content": "Fix critical bugs",
"status": "completed",
"activeForm": "Fixing critical bugs"
},
{
"content": "Fix high-priority bugs",
"status": "in_progress",
"activeForm": "Fixing high-priority bugs"
},
{
"content": "Fix medium-priority bugs",
"status": "pending",
"activeForm": "Fixing medium-priority bugs"
}
]
}
```
## Validation
- [ ] Generates activeForm for all items
- [ ] Validates status values
- [ ] Handles various content formats
- [ ] Preserves original content
- [ ] Returns proper TodoWrite structure
## Supporting Files
- `template.json`: TodoWrite format template (see Supporting Files section)Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.
Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX artifacts.
Initialize Beads issue tracking in your project with interactive configuration setup.
Calculate priority score for bugs, issues, or tasks based on severity, impact, and likelihood. Use for bug prioritization, task ordering, or risk assessment.
Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.
Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.
Inline orchestration workflow for dead code detection and removal with Beads integration. Provides step-by-step phases for dead-code-hunter detection, priority-based cleanup with dead-code-remover, and verification cycles.