How do you start a Team on your own tickets?

Why start here?

Because it is the size one engineer can prove alone, on a real ticket, in an afternoon. No Team to name, no backlog to attach, no admin in the loop past the first connection. You already have tickets assigned to you. This Team works those, and nothing runs that you did not click Start on.

How do you set it up?

1. Connect GitHub. The first screen after sign-in offers two doors: Connect GitHub, or install YAGNI Code. Take the first. The YAGNI App installs once on your organization, on the repositories a Team will work in; a member asks a workspace admin. Linear or Jira connects the same way, under Connections.
2. Create the Team. Open Create a Team. Search for your repository and pick it (repositories the App covers are added to the workspace on Create). Leave My tickets selected. The identity line says which tracker account you were matched to by email and how many open tickets are yours, with Not you? to pick yourself. The right column shows day one: Wright plans and builds, supervised by you; Reeve reads plans on its own; Proctor reviews every pull request on its own; Bailey and Fletcher to add later. Click Create.
3. Start a ticket. Work opens on your Team with your unstarted tickets listed under Proposed, each with Start. Click it. The ticket moves to Plan, accepted by you, and Wright begins. Start several at once from Add tickets.
4. Approve the plan. Wright drafts a plan against the repository and Reeve critiques it in place. The open questions arrive as taps on the case file. Answer them, then Approve plan, or Send back with a note for the next pass. Wright builds to a draft pull request; Proctor reviews it and Wright answers the findings.
5. Merge. When Proctor’s verdict is approve, the pull request comes out of draft on its own. Merge it on GitHub, or click Merge on the case file if your workspace has the in-app switch on. Done means merged.

What appears on Work?

Your open, unstarted tickets from the tracker, listed under Proposed on your Team, read straight from Linear or Jira. Each keeps its key and its tracker glyph. Nothing is minted until you click Start; a ticket reassigned or closed in the tracker stops appearing. Past ten, Show more folds the rest. Once started, a ticket walks the six stages like any other, and Work shows where it is and how long it has been there.

Who sees this Team?

You and workspace admins. A Team whose from blank names exactly one member who is also its owner is personal, derived from those two facts, never a setting. It is listed in the sidebar only for you, and its Agents’ spend sits on your line in Usage. When a teammate should see it, add them as a member or widen the audience in the Edit sheet.

How does it grow?

By adding a line on the Team page. Switch Bailey’s propose line on and it picks your next tickets for you each morning; that is the backlog size in all but name. Turn on Fletcher once the repository’s environment is working and every pull request gets a browser walk. Move Proctor’s line to autonomous when its track record has earned it. The Team you started with is the Team you keep.