What problem does it solve?
It prevents vague, inconsistent issue tickets for non-user-facing engineering work by forcing structured inputs (driver, scope, acceptance criteria, risks) into a consistent GitHub issue format.
Core Features & Use Cases
- Structured technical ticket generation: Creates a GitHub Issue with an explicit driver (why), scope (what), and actionable acceptance criteria (what must be true).
- Works for tech debt and refactoring: Supports chores like infra changes, refactors, dependency updates, CI/CD improvements, and other work that doesn’t fit /feature or /bug.
- Prevents bad submissions: Enforces single-question flow, requires a driver, and requires at least one acceptance criterion before allowing issue creation.
- Auto-labeling and repo targeting: Applies priority labels, derives a work-type title prefix, and targets the correct repo based on the active project context.
Quick Start
Ask the AI to create a technical task ticket by calling /task and answering the driver, scope, acceptance criteria, priority, and any optional risks or dependencies.