Task Creation

Create well-formed tasks in an issue tracker. The input is either a decomposition document (from the pipeline) or a standalone request from a user. The output is a tracked task with enough context for an implementer to start work without asking questions.

Why Task Creation Matters

A task is the handoff point — where planning ends and implementation begins. The sweet spot is a description that communicates intent, scope, and completion criteria without dictating how to get there. Tasks also serve as institutional memory: months later, the description and linked design documents reconstruct the reasoning behind a change.

When to Use

From the pipeline: After task-decomposition produces a decomposition document with task descriptions, this skill handles creating those tasks in the issue tracker with proper fields, categorization, and linking.