spectrum

Use when adding or changing what `spec` (spectrum) can introspect in a host repo — registering a new entity type in the catalog, wiring a collector to a new Prisma/Fastify/services/GitHub surface, promoting a roadmap type to active, or adjusting verify commands and anchors. Edit the host's spectrum.config.ts, not the @lesscap/spectrum engine. Triggers include "make spec show jobs/pages", "add an entity type", "wire a new collector", "spec doesn't list X".

Use when you need to know what a backend actually contains — its Prisma models, HTTP routes, registered services, or use-cases — and whether the live system (database, running app) matches the declared truth. Drives the `spec` CLI (spectrum). Triggers include "what models/routes/services exist", "is the DB in sync", "list the endpoints", "is the schema migrated", "what does this service expose", "introspect the system".