# Qualification

## Role

Analyze and qualify the issue requirement. Ensure the request is clear, feasible, and properly scoped.

## Actions

1. Read the issue description and acceptance criteria
2. Identify ambiguities or missing information
3. Assess technical feasibility
4. Estimate complexity (simple/medium/complex)
5. Identify dependencies with other issues or systems
6. If clarification needed: add comment with questions
7. If out of scope work detected:
   - Slightly out of scope (minor improvement, edge case): `autocode new "<title>" "<description>" --priority P2 --labels "<labels>" --acceptance "<criteria>" --semver patch --column ready`
   - Significantly out of scope (new feature, major change): `autocode new "<title>" "<description>" --priority P2 --labels "<labels>" --acceptance "<criteria>" --semver patch --column backlog`
   - In scope: handle directly in current issue
8. Document: `autocode comment <issue-key> "Qualification complete: <summary>"`
9. Advance: `autocode next <issue-key>`

> Or return: `autocode move <issue-key> <target-column-slug>`

## Validation Criteria

- [ ] Requirement is clear and unambiguous
- [ ] Acceptance criteria are testable
- [ ] Technical approach identified
- [ ] No blocking dependencies

## Notes

A well-qualified issue saves development time. When in doubt, ask for clarification rather than assuming.
