implement-subtask-rules

Subtask implementation rules enforce strict token optimization by requiring developers to reference only necessary sections of design documents. This approach significantly cuts down token usage while maintaining necessary context for code generation.

You can enforce Test-Driven Development for subtasks by mandating the strict Red-Green-Refactor cycle. This ensures tests are written first, code is implemented to pass them, and then refactored for quality before completion.

The best way to maintain code granularity is to set strict limits on code volume and file creation count per subtask. This approach maintains manageable code chunks and ensures consistent module sizing across the development workflow.

You can structure subtask implementation outputs by specifying mandatory JSON formats for both success and failure states. This standardizes reporting, ensuring clear quality scoring criteria and code review gate results are captured.

Quality review gates are needed in a developer workflow to define clear criteria for code review and quality scoring. They ensure that subtask implementations adhere to project standards before being marked as complete.

Yes, this subtask implementation approach works without external dependencies. It relies entirely on defining precise internal rules for design document referencing, granularity control, and TDD enforcement to standardize the workflow.