ring:pre-dev-subtask-creation

Zero-context subtasks break large features into 2-5 minute steps with explicit file paths, verification commands, and commit-ready sequences. This enables any engineer to execute tasks without prior codebase knowledge, following a strict RED-GREEN-REFACTOR TDD rhythm.

The TDD rhythm for subtask generation follows a RED-GREEN-REFACTOR cycle, breaking large tasks into 2-5 minute steps. Each step includes explicit file paths, test steps, and verification commands, producing deterministic subtasks executable by any engineer.

Deterministic subtasks are created by breaking feature work into 2-5 minute steps that include exact file paths, test steps, verification commands, and commit-ready sequences. This ensures zero-context clarity and consistent task execution across engineers.

Zero-context task breakdown is ideal for ramping up on unfamiliar codebases because it generates 2-5 minute subtasks with explicit file paths and verification commands. Engineers with zero knowledge of the codebase can execute the steps following the TDD rhythm.

Subtask generation requires no dependencies or prior codebase knowledge. It produces zero-context subtasks with explicit file paths, test steps, and verification commands, allowing any engineer to execute the 2-5 minute steps during onboarding.

Bite-sized task breakdown is designed for complex features requiring onboarding-friendly, zero-context subtasks. It may not suit tasks that cannot be broken into 2-5 minute TDD steps or features that do not require explicit file paths and verification commands.