qualify-issue

Drive a structured Q&A loop to gather missing issue details.

5|Updated Jul 25, 2025
One-click install
npx skills add https://github.com/tomzx/agents --skill qualify-issue
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: qualify-issue
Source: https://github.com/tomzx/agents/tree/main/skills/qualify-issue
Command: npx skills add https://github.com/tomzx/agents --skill qualify-issue

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

GitHub issues often arrive with incomplete context (missing acceptance criteria, steps to reproduce, or scope). This skill orchestrates a structured, multi-round Q&A loop with the reporter to gather the missing details and make the issue ready for the requirements stage.

Core Features & Use Cases

  • Iterative clarification: engages the reporter to fill gaps in the issue description, such as acceptance criteria, environment details, and user impact.
  • Workflow orchestration: fetches issue history, identifies open questions, and manages updates and comments until the issue is fully qualified.
  • Use Case: when a feature request or bug report lacks explicit criteria, this skill drives a focused dialogue to produce a complete, testable specification for /create-requirements.

Quick Start

Start the qualification loop by invoking this skill on an issue URL or number to begin asking clarifying questions.

Frequently Asked Questions about qualify-issue

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

FAQPage Schema
How do I clarify incomplete GitHub issues and gather missing requirements?▼

You can clarify incomplete GitHub issues by driving a structured Q&A loop with the reporter to gather missing details like acceptance criteria and steps to reproduce, making the issue ready for requirements.

What is the best way to automate asking follow-up questions on bug reports?▼

Automating follow-up questions on bug reports involves fetching issue history, identifying open questions, and posting clarifying comments to orchestrate a focused dialogue with the reporter.

How do I qualify a feature request before creating testable specifications?▼

To qualify a feature request, you engage the reporter iteratively to fill gaps in environment details and user impact until the issue has a complete, testable specification for requirements generation.

Does issue qualification work with existing GitHub issue histories?▼

Yes, issue qualification works with existing histories by fetching previous comments, identifying unanswered open questions, and re-invoking the clarification loop when the reporter replies.

When do I need to run a multi-round Q&A loop for issue requirements?▼

You need a multi-round Q&A loop for issue requirements when feature requests or bug reports lack explicit acceptance criteria, defined scope, or steps to reproduce.

What are the limitations of automated issue qualification workflows?▼

Automated issue qualification workflows depend on reporter responsiveness to fill missing context, meaning the loop cannot complete until the reporter provides answers to the open clarifying questions.