Client onboarding

One repo. One backlog item. One reviewed PR.

Your code stays in your GitHub repository. We work in a branch, provide test evidence and review, and your team controls the merge.

01 · Scope

Send the repo and task.

Submit the repository URL, issue or task link if one exists, the expected outcome, and any boundaries we need to respect.

02 · Access

Invite only the repo we need.

After we confirm the sprint, invite phillipbraithwaithe-ctrl as an outside collaborator with Write access to that repository only.

Do not grant Admin access. Do not share organization-wide access.

03 · Issue

Assign the backlog item.

If the task already exists as a GitHub issue, assign it to phillipbraithwaithe-ctrl after access is granted. If not, the sprint request is enough for us to scope the work.

04 · Delivery

Your team owns the merge.

We implement in an isolated branch/worktree, run automated tests, perform a separate review pass, and open a PR with the evidence needed to review it.

Security rule: never paste passwords, API keys, private tokens, production credentials, or customer data into the sprint form or a GitHub issue. If a sprint genuinely requires a secret, we’ll arrange a separate secure handoff.

Submit a backlog item