2026-03-18 11:42:57 +09:00
|
|
|
export const TODOWRITE_DESCRIPTION = `Use this tool to create and manage a structured task list for tracking progress on multi-step work.
|
|
|
|
|
|
|
|
|
|
## Todo Format (MANDATORY)
|
|
|
|
|
|
|
|
|
|
Each todo title MUST encode four elements: WHERE, WHY, HOW, and EXPECTED RESULT.
|
|
|
|
|
|
2026-04-04 01:27:51 +09:00
|
|
|
Format: "[WHERE] [HOW] to [WHY] - expect [RESULT]"
|
2026-03-18 11:42:57 +09:00
|
|
|
|
|
|
|
|
GOOD:
|
2026-04-04 01:27:51 +09:00
|
|
|
- "src/utils/validation.ts: Add validateEmail() for input sanitization - returns boolean"
|
|
|
|
|
- "UserService.create(): Call validateEmail() before DB insert - rejects invalid emails with 400"
|
|
|
|
|
- "validation.test.ts: Add test for missing @ sign - expect validateEmail('foo') to return false"
|
2026-03-18 11:42:57 +09:00
|
|
|
|
|
|
|
|
BAD:
|
|
|
|
|
- "Implement email validation" (where? how? what result?)
|
2026-04-03 21:37:16 +09:00
|
|
|
- "Add dark mode" (feature, not a todo)
|
2026-03-18 11:42:57 +09:00
|
|
|
- "Fix auth" (what file? what changes? what's expected?)
|
|
|
|
|
|
|
|
|
|
## Granularity Rules
|
|
|
|
|
|
|
|
|
|
Each todo MUST be a single atomic action completable in 1-3 tool calls. If it needs more, split it.
|
|
|
|
|
|
|
|
|
|
**Size test**: Can you complete this todo by editing one file or running one command? If not, it's too big.
|
|
|
|
|
|
|
|
|
|
## Task Management
|
|
|
|
|
- One in_progress at a time. Complete it before starting the next.
|
|
|
|
|
- Mark completed immediately after finishing each item.
|
|
|
|
|
- Skip this tool for single trivial tasks (one-step, obvious action).`
|