linear-issue-workflow

To turn a Linear issue into a shippable pull request, you can use a workflow that fetches the issue details, clarifies scope, generates a structured implementation plan, sets up an isolated worktree branch, and runs a self-review gate before delivery.

You can set up a git worktree for feature development by creating an isolated branch based directly on the repository's remote default branch, ensuring your code changes start from the latest updated source baseline.

You can automate code review on a feature branch by running a whole-branch diff self-review, fixing every finding, and repeating the cycle iteratively up to three passes until the branch is review-clean or requires user escalation.

Yes, you can attach an implementation plan to a Linear issue automatically by using Linear MCP tools to retrieve the issue and upload the generated implementation plan directly to the issue record.

Yes, the linear-issue-workflow requires explicit user approval before starting implementation, ensuring you review and confirm the generated implementation plan and worktree setup before any code changes are executed.

If code review findings remain after iterative fix cycles on a feature branch, the workflow escalates the unresolved issues for a user decision, potentially applying a Greybeard waiver to bypass specific non-critical findings.