Best Practices
Best Practices
Do
- Start with the goal, not the tasks
- Order tasks by dependency
- Include rollback strategies for risky changes
- Reference existing patterns in codebase
- Use consistent naming conventions
- Group related tasks logically
Don't
- Write vague task descriptions
- Skip the test-first steps
- Combine unrelated changes
- Assume prior knowledge
- Leave out error scenarios
- Make tasks too big or too small