issue-register

Creating GitHub Issues from task files is done by registering prepared markdown files into GitHub while preserving task IDs and updating tracking summaries. This skill assigns labels, validates duplicates, and assigns Copilot agents based on dependencies.

Dependency-aware assignment works by checking execution environment and dependency readiness before assigning tasks. Copilot agent work is only assigned through the GitHub API when dependencies are verified and a base branch is established.

Yes, GitHub CLI authentication is required to register task files as Issues. This skill needs authenticated access to validate existing labels, perform duplicate checks, create issues, and assign Copilot agents through the API.

The required directory structure for registering task files is docs/specs/{feature}/tasks. This documentation-driven path allows the skill to locate task packs, apply duplicate checks, and synchronize issue links back into the summary file.

Preventing duplicate GitHub Issues is handled by checking existing Issues before creating new ones. This duplicate-safe registration ensures task files are only registered once and preserves original task IDs and issue links.