First read ../comet-github/references/maintainer-contract.md. The drafting phase is read-only; creating a GitHub Issue requires explicit confirmation.
Determine Issue content
- Understand the local observation, inspect the current implementation, tests, Runtime paths, and related documentation.
- Search existing GitHub Issues and PRs by domain concept to determine whether this is a duplicate, a follow-up to an existing Issue, or a new report.
- Choose the most matching repository template: bug, feature, task, or question. Read the current YAML template before drafting fields.
- Distinguish user-visible problems from speculated implementation causes. Include implementation details only when they help reproduce or scope the issue.
Draft the body
Generate the following:
- A concise title using the repository template prefix;
- Affected workflow, platform, and version/status;
- Current behavior and expected behavior;
- Reproduction steps or the user workflow that triggered the idea;
- Existing evidence and suspected boundaries; label unverified content as assumptions;
- Explicit scope and non-goals;
- Acceptance criteria that can be independently checked;
- Related Issue/PR links and duplicate search notes.
For a Feature, first describe the workflow problem and desired behavior, then propose an implementation approach. For a Bug, preserve accurate commands, logs, version, and project state when necessary.
Confirm before publishing
First show the complete title, template type, labels, and body. Only after confirmation may you call gh issue create. After creation, verify the returned URL and title, and report the Issue number. Unless otherwise requested, do not modify labels, close related Issues, or create additional tickets.