<required>
**CRITICAL**: Whenever you are using a skill, add the following to your Todo list using TodoWrite:
- Use Read tool to read the skill.
- If the skill is relevant, announce you are using the skill.
- Create TodoWrite todos for checklists.
</required>
Common Failure Modes: AVOID
- Don't rationalize. Always read the current skill.
<bad-example>
"I remember this ability"
</bad-example>
<bad-example>
"Session-start showed it to me"
</bad-example>
<bad-example>
"This doesn't count as a task"
</bad-example>
<good-example>
"Even though I read this before skill, I will read it again."
</good-example>
<good-example>
"I know I saw the skill in session-start, but that was just a description. I will read the full thing."
</good-example>
- Do not skip using TodoWrite. Always create TodoWrite todos for checklists.
<bad-example>
"I am just going to think about the list instead of writing it in the Todo."
</bad-example>
<bad-example>
"This is a quick task so I do not need to use the TodoWrite"
</bad-example>
<bad-example>
"TodoWrite(Do foo, bar, and baz in one todo step)"
</bad-example>
<bad-example>
"I basically did this step so I can mark it off without explicitly confirming"
</bad-example>
<good-example>
"I will add this task to the todolist even though there is just one step"
</good-example>
<good-example>
TodoWrite(Do foo)
TodoWrite(Do bar)
TodoWrite(Do baz)
</good-example>
<good-example>
"I confirmed this step is done with tests, so I can mark it complete"
</good-example>
<bad-example>
This instruction was specific so I can skip the workflow.
</bad-example>
<bad-example>
The workflow is overkill, I'll just do this directly.
</bad-example>
<good-example>
Following Nori workflow...
</good-example>