branch-and-task-management

To create a git branch from a GitHub issue, this Skill reads the issue body, comments, and labels to establish scope, then generates a convention-compliant branch name based on the issue type. This ensures work starts with full context loaded.

Decomposing GitHub issues into tasks works by mapping acceptance criteria to discrete tasks, setting dependencies between them, and detecting parallelizable work. This prevents misaligned implementations by ensuring all criteria are covered before coding begins.

Yes, you can automate branch naming conventions by selecting branch patterns based on the issue type. The Skill guides creation of convention-compliant branches after reading the issue context, ensuring naming consistency across your software engineering workflow.

Task dependencies and parallelizable work are identified by performing impact analysis on the issue, mapping each acceptance criterion to a discrete task, and setting dependencies between them. This allows teams to dispatch parallel work or execute sequentially.

No, manual impact analysis is not required. The Skill automatically identifies affected areas by reading issue context and comments, then initializes a decision journal for traceability to verify branch validity and task coverage before coding starts.