github-ticket-intake

To convert messy user requests into tracked GitHub issues, provide the request and repo context. The system builds a task contract to resolve whether it becomes a single issue, a checklist, or a linked set, then optionally writes artifacts to GitHub.

Yes, this workflow supports creating linked issue sets. It resolves the destination structure to determine whether a request should become a single GitHub issue, a checklist, or a small linked set based on the request scope.

Yes, you can generate draft artifacts without writing directly. The system supports a draft-only mode that returns a ready-to-edit ticket package, alongside a write-ready mode that applies preflight checks before executing writes.

To map GitHub issues to a project, you must provide a known repository context, clarity on write intent, and optional project mapping parameters. This context is required to build the task contract before any artifact creation.

The best way to automate GitHub ticket intake is to route on intent and build a task contract before any writes. This establishes a clear boundary between intake and execution, ensuring templates and preflight checks are applied before creating issues.