Single Task Responsibility

Core Principle

Each task should have a single, well-defined responsibility.

When implementing a task, if you find yourself writing code that addresses multiple distinct responsibilities, this is a violation of the Single Responsibility Principle (SRP) and a signal to STOP and consult the user.

Recognition Pattern

You're violating SRP when:

1. The task description covers one responsibility (e.g., "Write tests for PDF actions")
2. Your implementation requires addressing another responsibility (e.g., "Create mocking solution for external package")
3. These responsibilities are distinct enough to warrant separate tasks

The Test