# Final Checklist

Use this checklist before creating or returning an issue.

## Target and Duplication

- The target repository is confirmed.
- Existing open and recent closed issues were checked when practical.
- The new issue is not an obvious duplicate.
- Labels match the repository's existing label taxonomy.

## Evidence

- The issue records the most important facts discovered during investigation.
- Code references use exact files, functions, commands, routes, events, payload fields, or error strings.
- External behavior is backed by primary sources when possible.
- Inferences are not worded as verified facts.

## Scope

- The goal is clear.
- Scope and non-goals are explicit.
- User constraints are preserved.
- The issue does not expand into unrelated refactors or product changes.

## Implementation Helpfulness

- Suggested direction names likely implementation entry points.
- Edge cases are called out.
- Compatibility and regression risks are called out.
- Acceptance criteria are concrete and testable.

## Validation

- Automated checks are listed when applicable.
- Manual smoke tests are listed when automated tests are insufficient.
- Documentation follow-up is included when behavior or public workflow changes.

## Safety

- No secrets, tokens, private keys, or sensitive customer data are included.
- Private repository names or internal paths are included only when appropriate for the target repository audience.
- The issue body is readable by someone who did not see the original chat.