implementation-task-plan

To turn a low-level design document into an executable work plan, you need dependency mapping and task decomposition. This Skill generates an implementation task plan that breaks down engineering work into ordered, dependency-aware tasks with batch commit checkpoints.

Dependency mapping in implementation planning identifies which modules must be built first. It performs parallelization analysis to distinguish truly independent work from tasks that appear parallel but still conflict on shared files, preventing merge issues during execution.

You batch implementation tasks by organizing work into committable execution batches with checkpoints and verification steps. This approach reduces merge conflicts by mapping prerequisites, detecting shared file conflicts, and tracing requirements back to the design documents.

Yes, you need completed requirements and low-level design documents to generate a task breakdown. The Skill applies prerequisite mapping and critical-path analysis to these inputs to produce a concrete, dependency-aware task roadmap before coding starts.

You should avoid automated task decomposition when a project lacks a completed low-level design document. Without explicit design inputs, the Skill cannot perform requirements traceability, critical-path analysis, or accurately map module dependencies for parallelization.

The best way to trace requirements during task decomposition is to map generated tasks directly back to design documents. This ensures every committable execution batch includes verification steps and explicit traceability to the original engineering requirements.