Run any Skill in Manus with one click

Get Started

create-github-issues-feature-from-implementation-plan

Stars36,269

Forks4,518

UpdatedFebruary 24, 2026 at 03:39

Create GitHub Issues from implementation plan phases using feature_request.yml or chore_request.yml templates.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

github

github/awesome-copilot

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Project Management SpecialistsBusiness and Financial Operations Occupations·SOC 13-1082

SKILL.md

readonly

name	create-github-issues-feature-from-implementation-plan
description	Create GitHub Issues from implementation plan phases using feature_request.yml or chore_request.yml templates.

Create GitHub Issue from Implementation Plan

Create GitHub Issues for the implementation plan at ${file}.

Process

Analyze plan file to identify phases
Check existing issues using search_issues
Create new issue per phase using create_issue or update existing with update_issue
Use feature_request.yml or chore_request.yml templates (fallback to default)

Requirements

One issue per implementation phase
Clear, structured titles and descriptions
Include only changes required by the plan
Verify against existing issues before creation

Issue Content

Title: Phase name from implementation plan
Description: Phase details, requirements, and context
Labels: Appropriate for issue type (feature/chore)

More from this repository

same repository

pester-should-migration

github/awesome-copilot

Experimental (preview) Pester skill for migrating classic Should -Be (v5) assertion syntax to the new Should-* (v6) assertions (note the hyphen, no space), e.g. `Should -Be` -> `Should-Be`, `Should -Not -Be` -> `Should-NotBe`. Tracks Pester 6, which is still a release candidate, so this guidance may change; verified against Pester 6.0.0-rc2. Use when converting Pester v5 assertions to Pester v6 Should-* operators, modernizing a Pester test suite, or when a user asks to migrate, convert, or rewrite `Should -...` calls in .Tests.ps1 / PowerShell files.

2026-07-0336.3k

agentic-workflows

github/awesome-copilot

Route gh-aw workflow design/create/debug/upgrade requests to the right prompts.

2026-07-0336.3k

pester-migration

github/awesome-copilot

Experimental (preview) Pester migration skill for upgrading PowerShell Pester test suites across major versions — v3→v4, v4→v5, and v5→v6. The v5→v6 path tracks Pester 6, which is still a release candidate, so that guidance may change. Covers the Discovery/Run two-phase model, moving setup into BeforeAll, $PSScriptRoot vs $MyInvocation, mock changes (Assert-MockCalled → Should -Invoke, removed fall-through), Invoke-Pester parameters → PesterConfiguration, data-driven -ForEach/-TestCases, and the v6 breaking changes. Use when the user asks to upgrade, migrate, or modernize Pester tests, fix *.Tests.ps1 files that broke after bumping the Pester version, or convert legacy Should / Invoke-Pester syntax.

2026-07-0236.3k

copilot-pr-autopilot

github/awesome-copilot

Copilot left 14 review comments on your PR — half are nits. Hours of fix → reply → resolve → re-request, and each round lands MORE comments. This skill runs loop engineering: auto-triggers Copilot Code Review via GraphQL (no @copilot mention), triages every open thread (Copilot, humans, advanced-security) with a fix / decline / escalate rubric, dispatches parallel fix sub-agents that obey the repo build/test/lint conventions, commits per iteration, replies+resolves citing the pushed SHA, then re-triggers until HEAD is reviewed with zero threads awaiting the agent's reply (remaining open threads are explicit hand-offs to the human — escalated declines, design tradeoffs). You merge a clean PR; the bot runs it. Trigger phrases: "address copilot comments", "run a copilot review loop", "fix this PR", "iterate on copilot feedback". Repo-agnostic, gh CLI + PowerShell. Full autopilot needs repo Triage/Write; external PR authors get single-iteration mode plus manual re-trigger (UI 🔄 or substantive-commit push).

2026-07-0136.3k

create-implementation-plan

github/awesome-copilot

Create a new implementation plan file for new features, refactoring existing code or upgrading packages, design, architecture or infrastructure.

2026-06-3036.3k

azure-devops-cli

github/awesome-copilot

Manage Azure DevOps resources via CLI including projects, repos, pipelines, builds, pull requests, work items, artifacts, and service endpoints. Use when working with Azure DevOps, az commands, devops automation, CI/CD, or when user mentions Azure DevOps CLI.

2026-06-2936.3k

name	create-github-issues-feature-from-implementation-plan
description	Create GitHub Issues from implementation plan phases using feature_request.yml or chore_request.yml templates.

Create GitHub Issue from Implementation Plan

Create GitHub Issues for the implementation plan at ${file}.

Process

Analyze plan file to identify phases
Check existing issues using search_issues
Create new issue per phase using create_issue or update existing with update_issue
Use feature_request.yml or chore_request.yml templates (fallback to default)

Requirements

One issue per implementation phase
Clear, structured titles and descriptions
Include only changes required by the plan
Verify against existing issues before creation

Issue Content

Title: Phase name from implementation plan
Description: Phase details, requirements, and context
Labels: Appropriate for issue type (feature/chore)