Give me an overview of this project

This is Specsight's own product — the spec is Specsight analysed by Specsight itself. It spans 24 features, from the entry surfaces a visitor meets first through to the parts only the team uses day to day. The way in is **Authentication** and **Onboarding** — the path from a signed-out visitor to a working dashboard with an organisation, a connected GitHub project, and a plan in place. [1] The heart of the product is **The Spec**: the feature tree and Context/Action/Outcome scenarios, annotations, the changelog, and the feature map. Around it sit Digests, Export, Plans & Billing, and Email Notifications. The newest area is **Ask Specsight** — a conversation with the spec, where a plain-language question comes back as an answer with inline citations to the exact scenario behind each point. [2] You're using it right now.

Authentication833

The gateway between a visitor and a working Specsight dashboard. Every page that shows organisation data assumes a known, signed-in member; Authentication is the layer that establishes and maintains that identity.

Onboarding731

The first-run path from a verified email to a working dashboard. Onboarding is responsible for the short stretch where a brand-new member arrives with no organisation, no project, and no plan — and leaves with all three in place.

Organisations

The container every other Specsight surface lives inside. Projects, members, billing, and integrations are all scoped to an organisation, and a single person can belong to many of them at once.

Members & Roles751

How a Specsight organisation grows. Each person on the team is added with a role — Admin, Developer, Editor, or Viewer — and that role decides what they can see, change, and manage across the spec.

Organisation Settings32

The dial for the organisation itself — its name, its URL, and the doorway to deleting it entirely. Limited to admins, with the destructive parts sitting behind explicit confirmation.