Skip to main content

1. Create your project

This page gets your project created and pointed at a repository, no matter which starting point you have. By the end, you should be looking at the project dashboard with a healthy board ready for the next tutorial.

If you have not installed Squadboard yet, follow Installation first, then come back here.

Pick your starting point​

Choose the path that matches what you already have. All three converge on the same project.

A. New repo with Squad initialized
Best when you already ran squad init in a fresh repo and want Squadboard to give that team a board.
B. Empty workspace + project template
Best when you have nothing yet and want sensible defaults: backlog → ready → in progress → in review → done, plus example ceremonies.
C. Existing repo already running Squad
Best when the repo has a populated .squad/, agents, and history you do not want Squadboard to overwrite.

1. Create the project​

Open Squadboard. The first screen is Projects — the boundary for every board card, agent, ceremony, run, MCP server, and integration you create.

Click New project, name it (e.g., MyProject), and pick the repository folder:

  • Path A or C — choose the existing repository that already owns .squad/. Squadboard reads that folder as the operating model; it will not overwrite the agents, decisions, or history that are already there.
  • Path B — pick an empty folder, then choose the Default Software Project template. Squadboard scaffolds .squad/ with a roster, routing rules, casting state, and example ceremonies.

Either way, your project now exists.

2. Read the dashboard before touching anything​

Open your project from the project list. The dashboard is the cockpit: project identity, board state, recent runs, and automation status all in one place. Confirm the project name and repository path match what you intended before you move work around.

3. Confirm the board exists with the expected columns​

Open Board. You should see five columns — Backlog → Ready → In Progress → In Review → Done. Template- and existing-repo paths may already have cards; the new-repo path will be empty except for any seeded launch work.

You do not need to add a card yet. The board is just here so you know where work will live.

4. (Optional) Import a Squad App for more than defaults​

Squad Apps package reusable team + ceremonies + skills + tool recipes + seed work as one unit. Use them when the default template is too thin for the project you are running.

Open Templates and switch to the Projects tab to see what is available.

Before applying any import, check:

  1. Which agents and charters will be added.
  2. Which skills or tool instructions will be injected into agent prompts.
  3. Whether MCP servers or GitHub settings need secrets you have not configured yet.
  4. What seed work will appear on the project board.

For the rest of these tutorials, the default software template is enough. Heavier imports (launch-readiness, integration-validation) are reviewed in Tutorial 4.

What you should have now​

  • A project visible on the Projects page.
  • A dashboard pointed at the repository you intended.
  • A board with the standard five columns.
  • (Optional) An imported Squad App you reviewed before applying.

Continue with 2. Cast and review the team → to give your project a roster the coordinator can actually route work to.

Last updated on