github-issue-workflow

Cross-repo GitHub issues are drafted from natural-language prompts to coordinate multi-stage work. The skill generates structured issue sets with explicit repo roles like primary and secondary, applying cross-links for stable backlog tracking.

Backlinks link related GitHub issues across different repositories by applying tasklist references and cross-links. This maintains repo health and captures durable context, ensuring primary and secondary issues stay connected for future pickup.

Standardized labeling schema for GitHub issue triage is maintained by applying an explicit label structure during issue creation. This ensures issues are categorized consistently across repositories, aiding triage and backlog tracking.

Brainstorming notes are turned into trackable GitHub issues by drafting concrete tasks with structured bodies and concise titles. This captures resumable work and follow-ups, enabling durable backlog tracking across repos.

Reference-only repositories are supported for cross-repo planning through explicit multi-repo roles. The workflow assigns roles like primary, secondary, and reference_only to coordinate issues and link related context without creating unnecessary tasks.

Explicit repo roles coordinate GitHub issues across repositories by defining primary, secondary, and reference_only responsibilities. This structure enables stable backlog tracking and ensures cross-links capture durable context for multi-repo work.