Project
A connected codebase in Specsight, scoped to one Organisation. Every Feature, Scenario, and changelog entry belongs to exactly one Project.
A Project is the unit of analysis in Specsight. You connect a GitHub repository, give it a name, and Specsight produces a spec — features, scenarios, connections, the lot — for that single codebase. Most teams start with one Project per product.
Projects belong to an Organisation, and roles (Admin, Developer, Editor, Viewer) are set once, at the Organisation level — every Member sees every Project. Plan limits split two ways: monthly allowances for analyses, syncs, and reports count across the whole Organisation, while the codebase ceiling (source-file count and repository size) applies per Project.
Multi-repo products work as multiple Projects today: one for each service, each with its own spec. Native multi-repo Projects, where one spec is drawn from several repositories, are on the roadmap.
Related terms
- SPEC
Feature
A logical grouping of scenarios that represents a meaningful unit of the product — like “Document Upload” or “User Authentication.” Features form the structure of a Specsight spec.
- SPEC
Scenario
A single plain-language description of how a product behaves in a specific situation. The atomic unit of a Specsight spec.
- OPERATIONS
Sync
The release-triggered update to a Specsight spec. Fires automatically every time code lands on the tracked branch, touching only the scenarios that release changed.