des-dev-task-breakdown

To break down ready implementation stories into developer tasks, you consume the story catalog and readiness report to generate an ordered task list with acceptance criteria, tests, and quality and security work. This prevents jumping into coding without a validated plan.

Story readiness gating in task breakdown ensures selected implementation stories are marked ready before decomposition. It requires honoring the readiness report to validate that story scope, acceptance criteria, test expectations, and dependencies are known before generating developer tasks.

To prepare a coding agent handoff for data pipeline implementation, you generate a structured development task plan with expected outputs, validation checks, and governance items. This allows the coding agent to implement directly without planning inside the same step.

Task breakdown does cover data quality, data contracts, governance, security, metadata, and CI/CD expectations. It adds task-level items for these areas when relevant to ensure comprehensive validation and quality assurance during the implementation phase.

You cannot generate production code from the dev task breakdown. It explicitly produces a task plan document with acceptance criteria and a handoff prompt, ensuring a separate coding agent handles the actual implementation rather than generating code during planning.

The implementation task plan output uses a markdown file format written to the implementation artifacts directory. This document contains the ordered developer tasks, validation checks, dependencies, risks, and the ready-for-implementation decision.