kano-backlog

Categorize GitHub Issues into Kano categories and apply priority labels.

10|1|Updated Mar 9, 2026
One-click install
npx skills add https://github.com/Lykhoyda/rn-dev-agent --skill kano-backlog
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kano-backlog
Source: https://github.com/Lykhoyda/rn-dev-agent/tree/main/.claude/skills/kano-backlog
Command: npx skills add https://github.com/Lykhoyda/rn-dev-agent --skill kano-backlog

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps users prioritize and refine their GitHub Issues backlog using the Kano model, automating the categorization of issues and applying priority labels.

Core Features & Use Cases

  • Kano Model Analysis: Categorizes issues into 'Must-be', 'Performance', 'Attractive', 'Indifferent', or 'Reverse' based on user satisfaction.
  • Automated Labeling: Applies Kano and priority labels to GitHub issues automatically.
  • Backlog Refinement: Recommends the next best issue to work on based on Kano prioritization.

Quick Start

Refine your GitHub Issues backlog with the Kano model by using the command: "refine the backlog".

Frequently Asked Questions about kano-backlog

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

FAQPage Schema
How do I prioritize GitHub issues using the Kano model?

You can prioritize GitHub issues using the Kano model by running a command to categorize issues based on user satisfaction into Must-be, Performance, Attractive, Indifferent, or Reverse, automating label application.

What is backlog refinement with the Kano model?

Backlog refinement with the Kano model categorizes issues by their impact on user satisfaction, applying priority labels automatically to recommend the next best issue for software development planning.

Do I need the GitHub CLI to automate issue prioritization?

Yes, you need the gh CLI installed because the issue prioritization process requires GitHub API access to retrieve issue data and manipulate labels for backlog automation.

Can I automatically apply priority labels to GitHub issues?

You can automatically apply priority labels to GitHub issues by analyzing them with the Kano model, which assigns categories like Must-be and Performance directly to your repository backlog.

What is the best way to refine a GitHub backlog for planning?

The best way to refine a GitHub backlog is using Kano model analysis to categorize issues by user satisfaction, which automatically applies priority labels and recommends the next best issue to work on.