qualify

Issue and PR Qualification

Validate issue/PR #$ARGUMENTS for correctness, completeness, and Python SDK alignment. Produces a verdict report that feeds into /tdd.

Phase 1: Identification & Context Gathering

Determine what #$ARGUMENTS is and find its linked counterpart:

1. Check if it is an issue - Run gh issue view $ARGUMENTS --json number,title,body,state,labels,comments
2. Check if it is a PR - Run gh pr view $ARGUMENTS --json number,title,body,state,files,additions,deletions,commits,comments,headRefName
3. Find the linked counterpart:
   • If PR: extract linked issue from body (Closes #N, Fixes #N, Issue #N, (Issue #N)) and fetch it
   • If issue: search for linked PRs via gh pr list --search "issue #$ARGUMENTS" and check open PRs referencing it
4. Fetch all comments on both the issue and PR (if both exist) for additional context

Display a summary:

Context for #$ARGUMENTS
-----------------------
Issue: #<number> - <title> (<state>)
PR:    #<number> - <title> (<state>) [or "None found"]

---

Phase 2: Issue Validation

Assess whether the issue is well-defined and ready for implementation:

1. Check issue structure - Does the body contain:
   • Clear description of the problem or feature
   • Reproduction steps (for bugs)
   • Proposed Implementation section
   • Files to Modify section
   • Example Usage (if applicable)
2. Read all comments - Look for scope changes, decisions, or additional requirements added after filing
3. Check labels - Confirm categorization (bug, enhancement, good first issue, etc.)
4. Extract requirements - Build a numbered list of acceptance criteria from the issue body and comments. Include both explicit requirements and implied ones.

Output the requirements list - this feeds directly into /tdd Phase 2:

Requirements for #$ARGUMENTS
-----------------------------
1. <requirement>
2. <requirement>
...

If the issue is missing critical information: Note the gaps but continue - the verdict will reflect them.