The ACM/IEEE-CS Joint Task Force on Computing Curricula published the Computer Science Curricula 2013. They express recommended contents of an introductory programming course as competencies. Competencies are latent properties that cannot be observed and measured directly. However, in order to make them observable and measurable tasks have to be solved. The Computer Science Curricula 2013 mentions competencies needed but doesn't mention the corresponding tasks as well. This job is left to each individual lecturer. The needed tasks cannot be derived directly from a competence since they contain a lot of very detailed information. We developed a construct that closes the gap between a competence and a task: the task type. On the basis of one of our programming courses for students of Mechanical Engineering we describe (a) the process of developing valid task types from given competencies and (b) valid tasks, which can be used in our computer-based training environment.