take

Reference the issue by number, URL, or description and invoke the take workflow. It reads the issue and comments, assigns it to the current GitHub user, implements the change on a new branch, runs relevant checks, and opens a PR linked with Closes #<issue-number>.

The workflow checks git status and existing artifacts first, then reconciles the checkout, branch, PR state, and prior evidence before continuing. It never repeats assignment, branch creation, or PR creation for work already in progress.

Unanswered Critical questions and unresolved Awaiting answer placeholders block implementation until resolved with the user. Questions explicitly deferred by the user do not block, and vague issues trigger codebase exploration before deciding whether implementation is safe.

No. It creates a branch from the repository's configured base branch without assuming main or master, and it does not pull or rebase implicitly. It also checks for unrelated dirty work and asks before carrying ambiguous changes into the new branch.

For substantial dependencies, consequential technical unknowns, or work spanning sessions, the workflow offers a write-exec-plan step that resolves unknowns through bounded prototypes first. Small issues keep a simple inline checklist instead.