What problem does it solve?
It reduces the risk and friction of taking an engineering ticket from Linear through implementation, local verification, and an atomic Graphite PR with correct scope and sequencing.
Core Features & Use Cases
- Dependency-aware ticket execution: Verifies whether prerequisite tickets or PRs are already implemented before starting and blocks when evidence is missing.
- Repo-guided, scope-limited changes: Loads repo authoring guidance (AGENTS.md, CLAUDE.md, and relevant BUGBOT docs) and constrains work to the ticketed scope unless correctness requires expansion.
- Local validation before PR: Runs the repo-specific lint/typecheck/format commands (and targeted tests) until all required checks pass, then submits via Graphite and links back to Linear.
Quick Start
Use the linear ticket workflow for issue <ISSUE_ID> by starting the ticket, implementing only the scoped changes, running the required local validations, then creating and submitting the Graphite PR and posting a concise follow-up to the issue.