---
name: create-todo
description: Use when creating structured todo files for any project. Reads CLAUDE.md for project context, identifies affected files via codebase search, and writes todos to the todos/ folder.
argument-hint: <description of the todo>
allowed-tools: Read, Write, Edit, Glob, Grep
---

# Create Todo

Creates structured todo files in the `todos/` directory of the current project.

## Workflow

### Step 1: Gather Project Context

1. Read the project's `CLAUDE.md` to understand tech stack, architecture, and conventions
2. Parse the user's request to identify the affected area
3. Use Glob/Grep to find relevant files in the codebase if affected files are not obvious

### Step 2: Choose Filename

Format: `kebab-case-description.md` in the `todos/` directory.

Create `todos/` if it doesn't exist.

### Step 3: Write Todo

Use this template:

```markdown
# [Short, precise title]

**Status:** Open
**Priority:** High | Medium | Low
**Area:** [module/app/component name]

## Description

[What needs to be done - clear and concise]

## Requirements

1. [Concrete requirement]
2. [Concrete requirement]

## Affected Files

- `path/to/file` - [What to change]

## Technical Notes

[Relevant patterns, reusable functions, conventions from CLAUDE.md]

## Acceptance Criteria

- [ ] Criterion 1
- [ ] Criterion 2
```

## Rules

1. **Be specific** - "Add column X to table Y" not "Improve table"
2. **Name files** - Always list concrete paths from codebase search
3. **Reference patterns** - Point to similar existing solutions found in the code
4. **No implementation** - Describe WHAT, not HOW in detail
5. **Use project language** - Match the language of CLAUDE.md and user request (German/English)