task-delegation

Convert task specifications into structured GitHub issues with dependencies and acceptance criteria.

Updated Dec 30, 2025
One-click install
npx skills add https://github.com/henrybravo/developer-readiness-portal --skill task-delegation-henrybravo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: task-delegation
Source: https://github.com/henrybravo/developer-readiness-portal/tree/main/.github/skills/task-delegation
Command: npx skills add https://github.com/henrybravo/developer-readiness-portal --skill task-delegation-henrybravo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Delegates implementation work to Copilot by turning requirements into well-structured GitHub issues, reducing back-and-forth and accelerating parallel development.

Core Features & Use Cases

  • Create a GitHub issue with a clear title and a comprehensive description that captures task scope, dependencies, acceptance criteria, testing requirements, and references to PRD/FRD/ADR.
  • Automatically update the task file in specs/tasks/ with the created issue link and issue number for traceability.
  • Enables parallel development by distributing work across Copilot-enabled tasks and aligning with the MCP workflow.

Quick Start

Provide a task specification in specs/tasks/ and let Copilot create a GitHub issue and assign the task for automated implementation.

Frequently Asked Questions about task-delegation

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

FAQPage Schema
How do I automate creating GitHub issues for Copilot from task specifications?

Automating GitHub issue creation for Copilot involves converting task specifications into structured issues with clear titles, acceptance criteria, dependencies, and testing plans. This enables parallel development by mapping specs to issues with automated PR creation references.

What is the best way to delegate implementation work to Copilot using GitHub issues?

Delegating implementation work to Copilot requires well-structured GitHub issues that capture task scope, dependencies, and PRD/FRD/ADR references. This reduces back-and-forth communication and accelerates parallel development across Copilot-enabled tasks.

Can I automatically update task files with GitHub issue links for traceability?

Automatically updating task files with GitHub issue links is supported in the specs/tasks/ directory. The system maps created issue numbers and links back to the original task specification files, ensuring full traceability across the delegation workflow.

Does Copilot need specific acceptance criteria and testing plans in GitHub issues to implement tasks?

Copilot requires specific acceptance criteria and testing plans within GitHub issues to properly implement tasks. Structured issues must satisfy requirements for task descriptions, dependencies, testing plans, and ADR/PRD/FRD references for successful automated implementation.

How do I structure GitHub issues for parallel development with Copilot?

Structuring GitHub issues for parallel development with Copilot means including comprehensive descriptions that capture task scope, dependencies, acceptance criteria, and references to PRD/FRD/ADR documents. Clear ownership and well-defined issue structures enable distributed automated work.

Why should I use structured GitHub issues instead of plain text for Copilot task delegation?

Using structured GitHub issues instead of plain text for Copilot task delegation ensures clear ownership and comprehensive task descriptions. Structured issues map specifications to dependencies, acceptance criteria, and testing requirements, reducing manual back-and-forth communication.