Spexso

Appearance

Team Onboarding & Enablement ​

New here? Start with a quickstart

If your stack is CAP + UI5 or ABAP, read the CAP + UI5 quickstart or the ABAP quickstart first — five minutes to your first spec-to-MR loop. This page covers the one-time registry setup and the broader onboarding path.

Prerequisite: configure the private @flexso npm registry ​

@flexso/spexso (and every other @flexso package) is published to Flexso's private GitLab npm registry, not the public npmjs.com registry. npm install only finds it once you point the @flexso scope at GitLab's instance-level package endpoint and authenticate. Do this once per machine (or per project).

  1. Create a GitLab access token with the read_api scope (read_package_registry is enough if your GitLab version offers it). A Personal Access Token works; a Group or Project Access Token is fine too. Copy the value.

  2. Expose the token to npm via an environment variable (so it never lands in git):

    bash
    export NPM_REGISTRY_READ_TOKEN=<your-token>        # macOS/Linux
    powershell
    $env:NPM_REGISTRY_READ_TOKEN = "<your-token>"      # Windows PowerShell

  3. Point the @flexso scope at the registry by adding an .npmrc. Use ~/.npmrc (all your projects) or a project-root .npmrc:

    ini
    @flexso:registry=https://flexso.gitlab.host/api/v4/packages/npm/
//flexso.gitlab.host/api/v4/packages/npm/:_authToken="${NPM_REGISTRY_READ_TOKEN}"

    This is GitLab's instance-level npm endpoint — it resolves any @flexso package across the instance, so no group or project ID is needed.

  4. Verify the scope resolves:

    bash
    npm config get @flexso:registry        # → https://flexso.gitlab.host/api/v4/packages/npm/

Keep the token out of version control: set NPM_REGISTRY_READ_TOKEN in your shell/profile, and only ever reference ${NPM_REGISTRY_READ_TOKEN} (never a literal token) in a committed .npmrc.

Install & start ​

bash
# In your SAP BTP project (after the registry is configured above)
npm install -D @flexso/spexso
npx @flexso/spexso init

# Open Claude Code
claude

# Setup + start developing
/spexso-setup
/spexso-brainstorm Employee leave request extension for SuccessFactors
/spexso-start 42 --pilot     # one issue, guided
/spexso-marathon             # autonomous over the whole backlog

Updating to a new version ​

bash
npm install -D @flexso/spexso@latest
npx spexso update

update is offline and asks nothing. It refreshes everything spexso owns — slash commands, agents, templates, rulebook baselines and the Spexso section of AGENTS.md (between the <!-- spexso:start --> / <!-- spexso:end --> markers) — and re-applies your per-agent models from .spexso/config.json. It also appends spexso .gitignore entries added since your install, leaving your own lines untouched. Labels, boards, config.json, CLAUDE.md and the rest of AGENTS.md are left alone. It prints the version jump (1.8.0 → 1.9.0, from .spexso/version); commit the refreshed files. No need to re-run init or /spexso-setup.

Edits inside the markers are overwritten

Put project-specific instructions in AGENTS.md outside the Spexso section, and project rules in .spexso/rules/*.local.md. On the first update of an older install (no markers yet), the section from ## Spexso Framework up to the next ## heading is replaced and the markers are added.