batch-task-decomposition

Identify independent work units by package or role, assign each a stable key and owner role, then define dependencies and acceptance criteria. This Skill automates that decomposition and outputs a tasks_json payload ready for batch issue creation.

Feed the approved architecture document and spec into the decomposition workflow. It generates child tasks with an acyclic dependency graph, owner assignments, and observable acceptance criteria, reusing stable keys when child issues already exist.

It requires an approved spec document, an architecture document, the workflow variant, owner roles, and the context blackboard from prior stages. Tasks that are not independently verifiable are merged or refined rather than created.

Each task receives a stable key, and existing child issues are reused via that key instead of being recreated. The output tasks_json is idempotent, so rerunning the decomposition does not produce duplicate delegation.

It only operates within its assigned stage and cannot make product or architecture decisions when scope is unclear; those cases are gated back to decision stages. It also does not execute privileged actions directly and must request the approved action pipeline.