A project is one GitHub repository on one watched branch. Each project has its own feature tree, scenarios, changelog, reports, and flow diagram.
You create your first project during onboarding. This article covers everything after that — adding more, editing settings, re-analysing, and deleting.
Create a project
Connect the GitHub App once before adding a project — see connect GitHub. Then, from the organisation home, click the New project button in the header or the New project tile at the end of the project grid. (Once you have at least one project, the project switcher in the top bar also exposes a + New project shortcut.) Fill in the form:
- Repository — every repo the GitHub App can read, alphabetised. Private repos are tagged PRIVATE
- Branch — Specsight pre-selects the repository's default branch
- Project name — pre-fills from the repository name; edit if you want
- Context description — optional. A short plain-English summary of what the product does. Specsight uses it to classify features more accurately
As soon as you pick a repository, Specsight measures it and the button label flips to Checking codebase…. When the measurement comes back, the button switches to Create project. Click it and the first analysis starts in the background — you land on the project page with a full-page Analysing codebase screen. Small repos finish in minutes; large ones can take up to an hour. You can close the tab — Specsight emails you when the spec is ready.
Edit a project
Open a project and click Project settings in the project rail. Settings has three pages:
- General — edit the project name and context description. Click Save changes
- Repository — read-only summary of the connected repository and watched branch. To switch either one, delete and recreate the project
- Danger zone — re-analyse or delete the project
Re-analyse the codebase
A re-analysis discards every AI-generated scenario and runs a full analysis from scratch. Use it when the codebase has shifted enough that incremental automatic syncs no longer reflect the product.
In Project settings → Danger zone, click Re-analyse codebase. If you have manual scenarios, choose whether to keep them (default) or delete them. Confirm with Yes, re-analyse — or, if you chose to delete manual scenarios too, the confirm button switches to Yes, delete all & re-analyse.
Delete a project
In Project settings → Danger zone, click Delete project and confirm.
Project caps
Standard covers up to five projects. BYOK and Partnership are unlimited. When a Standard organisation reaches the cap, the New project page replaces the form with a card pointing you at a quick conversation about higher limits — see plans and limits.
Who can do what
- Admins and Developers — create, edit, re-analyse, delete
- Editors — edit name and context description
- Viewers — read-only
See members and roles for the full capability matrix.