pre-dev-subtask-creation

Atomize features into 2-5 minute subtasks with complete code, exact commands, and TDD verification steps. Each subtask includes full implementation, test commands, and rollback procedures, eliminating context-switching and enabling zero-context developers to execute independently.

A zero-context subtask is a self-contained 2-5 minute step with complete code, exact commands, and verification—no external knowledge required. It enables any engineer to implement features without understanding the broader codebase, reducing onboarding friction and accelerating large-track delivery.

Structure each subtask in RED-GREEN-REFACTOR order: write failing tests first, implement code to pass, then refactor. Each subtask includes explicit test commands and verification steps, enforcing TDD discipline and guaranteeing testability before code ships.

No. Subtask creation applies to large-track features after Gate 7 validation passes. Pre-development subtasks require validated requirements, architectural decisions, and explicit feature scope; use this for implementation planning, not requirements gathering.

Subtasks are saved to docs/pre-dev/{feature-name}/subtasks with complete code, file paths, exact verification commands, TDD test patterns, and commit boundaries. Each step is self-contained and executable in 2-5 minutes with no external context needed.

Each subtask avoids duplicating logic from prior steps and implements only features required by the current step—no speculative abstractions. Frequent commits after each subtask maintain rollback safety and prevent scope creep within atomic boundaries.