Skip to content

Generate specs from the codebase ​

For: Adopter

First scan: an adopter runs usm scan after init and gets .usm files for every detected service, route, and data source.

Part of: Scan Command

Steps ​

  • Run (cli) — usm scan in the repo root after init created usmconfig.json
  • Review (cli) — console output — services, routes, and data sources matched against expectations
  • Inspect (spec) — generated .usm files in .usm/ for gaps or wrong detections

How this is verified ​

  • .usm/services/*.usm files created for each matched app
  • .usm/features/*.usm files created from route extraction