task-development-workflow

A test-driven development workflow structures software delivery by forcing requirement clarification, small task planning, and TDD red-green-refactor cycles before opening a pull request. This prevents rushed or ambiguous code by enforcing approval gates and reviewer notifications before merging to main.

Enforcing code review and branching rules requires a workflow that prohibits direct commits to main and mandates feature branches. This process ensures code is tested via TDD, submitted as a pull request, and only merged after explicit reviewer approval.

Yes, you can use a Trello-style board to track TDD implementation. The workflow supports breaking work into small tasks, tracking them on a board, and updating their status through the feature-branch, pull-request, and merge-safe delivery stages.

An approval-gated planning process works by asking clarifying questions about architecture and constraints, breaking the work into a small task plan, and waiting for explicit approval before any test-driven implementation begins.

Clarifying requirements before starting TDD implementation prevents ambiguous software delivery. By asking questions about user flow and constraints upfront, you ensure the test-driven development cycle directly targets approved, well-understood features.

Yes, the task-development-workflow skill supports merge-safe delivery by enforcing no-direct-to-main branching. It requires opening pull requests, responding to reviewer feedback, and passing TDD checks before any code is merged.