delegate-sidequest

Delegate non-blocking issues to Copilot via GitHub Issues or Agent Tasks.

Updated Jan 14, 2026
One-click install
npx skills add https://github.com/Mossaka/skills --skill delegate-sidequest
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: delegate-sidequest
Source: https://github.com/Mossaka/skills/tree/main/delegate-sidequest
Command: npx skills add https://github.com/Mossaka/skills --skill delegate-sidequest

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you stay focused on your primary task by proactively delegating non-blocking issues (bugs, code smells, missing tests, or documentation gaps) to Copilot when you notice them, so you can continue with your main work without getting distracted.

Core Features & Use Cases

  • Proactively delegate minor issues discovered during work (bugs unrelated to your current task, code smells, TODOs, outdated docs, accessibility concerns, UI inconsistencies, or lint warnings).
  • Choose between two delegation methods: create a GitHub Issue assigned to @copilot or create an Agent Task for immediate execution.
  • Follow WRAP principles and keep the user informed after delegation to maintain transparency and focus.

Quick Start

Notice a non-blocking issue and delegate it to Copilot using either a GitHub issue or an agent task to keep your main task on track.

Frequently Asked Questions about delegate-sidequest

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I delegate minor GitHub issues to Copilot without losing focus on my main task?

You can delegate non-blocking bugs or TODOs to Copilot by creating either a GitHub Issue assigned to @copilot or an Agent Task for immediate execution, ensuring your main workflow remains uninterrupted.

What is the best way to handle non-blocking code smells and TODOs during active development?

The best way to handle non-blocking code smells during active development is to delegate them to Copilot as Agent Tasks or GitHub Issues, preventing context switching while ensuring minor issues are tracked and resolved.

Can I use Copilot agent tasks for immediate UI cleanup and documentation updates?

Yes, you can use Copilot agent tasks for immediate UI cleanup and documentation updates by delegating these non-blocking issues directly, ensuring adherence to WRAP principles and naming conventions while you focus on core tasks.

Does delegating side quests to Copilot require specific naming conventions or workflow setups?

Yes, delegating side quests to Copilot requires clear delegation workflows using GitHub Issues or Agent Tasks, establishing specific naming conventions, and adhering to WRAP principles to maintain transparency and focus.

When should I avoid delegating issues to Copilot during my development workflow?

You should avoid delegating issues to Copilot when encountering blocking bugs or issues directly related to your current core task, as this Skill targets non-blocking tech debt, UI inconsistencies, and documentation gaps to prevent distraction.