wayq-issues

Generate issue resolution plans for GitHub issue triage.

1|Updated Jun 21, 2026
One-click install
npx skills add https://github.com/rcrath/wayq --skill wayq-issues
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wayq-issues
Source: https://github.com/rcrath/wayq/tree/main/.claude/skills/wayq-issues
Command: npx skills add https://github.com/rcrath/wayq --skill wayq-issues

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill streamlines the process of managing GitHub issues by offering a plan-first approach, which helps in organizing and prioritizing tasks without directly editing code.

Core Features & Use Cases

  • Issue Triage: Automate the classification and prioritization of GitHub issues based on milestones and user feedback.
  • Plan-First Analysis: Generate plans for issues to be implemented, ensuring all necessary steps are considered.
  • Dual-Repo Architecture: Maintain a clear separation between private technical work and public-facing issue tracking.

Quick Start

To get started, type /wayq-issues in your GitHub issue tracker.

Frequently Asked Questions about wayq-issues

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

FAQPage Schema
How do I triage GitHub issues using a plan-first approach?

GitHub issue triage with a plan-first approach automates classification and prioritization based on milestones and user feedback, then generates resolution plans without directly editing code to ensure all implementation steps are considered.

What is plan-first analysis for software development issue management?

Plan-first analysis for issue management generates structured implementation plans for GitHub issues, ensuring all necessary steps are considered before coding begins, streamlining task organization without direct code editing.

Do I need a dual-repo architecture to manage GitHub issue triage?

A dual-repo architecture is not strictly required but helps maintain a clear separation between private technical work and public-facing issue tracking when managing GitHub issue triage and milestones.

How do I automate issue classification based on GitHub milestones?

Automating issue classification based on GitHub milestones requires accessing associated repositories and relevant issue labels to organize, prioritize, and generate plans for issue resolution within the GitHub ecosystem.

Can I generate implementation plans for GitHub issues without writing code?

Generating implementation plans for GitHub issues without writing code is possible by analyzing issue labels and milestones to produce structured resolution steps, facilitating a plan-first approach to software development.

What are the limitations of plan-first GitHub issue management?

The primary limitation of plan-first GitHub issue management is that it focuses on organizing tasks and generating resolution plans without directly editing code, requiring separate tools for actual implementation.