A GitHub issue or board item can describe work, but delivery still spans product context, agent execution, repository artifacts, checks, and review. PullPlane keeps those stages connected to one live task.
Connect only the repositories agents need
A workspace owner installs the PullPlane GitHub App on selected repositories and connects a project to its repository and base branch. Repository scope remains controlled by the GitHub installation.
Turn the work item into the branch brief
Write the outcome, context, acceptance criteria, and verification in the card. A coding run checks out the repository in an isolated sandbox and works on the card branch against that shared brief.
Review the same artifacts GitHub already understands
The result returns as a branch and pull request with a concrete diff and checks. PullPlane can also surface terminal output, changed files, and a preview before the team approves the repository change.
- Keep branch protection and repository checks in force
- Use Reviewer, QA, or Security for additional read-only evidence
- Return merge state to the live project board through webhooks
Treat merge as a project decision
The default branch remains the source of truth. Conflicts, failed checks, unresolved review comments, or insufficient evidence should keep the task out of Done until a human resolves them and approves the merge.