init

Topics in the source

• Onboard a repo
• 1. Detect
• 2. Propose
• 3. One question round
• 4. OpenSpec scaffold
• 5. Write the file
• 6. Doctor
• 7. Next steps (full run only)

Preflight: run la-doctor --plugin once per session before using any la- or dr- command; if it fails, stop and show the user its output — unless the only failure is the existing living-architecture.yaml being invalid or declaring an older format, which this skill converts (steps 1 and 5). living-architecture.yaml records each gate of the flow as an explicit decision; its presence means the repo is onboarded. Keys, defaults and the doctor's consistency checks are in docs/configuration.md of the plugin repo; la-config show prints the resolved values. Fast path. When another skill's preflight reports the missing config, run steps 1–6 only, then hand back to that skill. A full run (the user invoked /la:init) continues to step 7. Read, don't ask. For each key note the value and where it came from: Existing config. If living-architecture.yaml exists, this run edits it in place: start from its values. Read it as raw YAML, not with la-config (which rejects removed keys and an older format). Under reviewers, the coderabbit flag and Sonar's enabled switch were removed (both bots are detected per PR): propose deleting them and keeping Sonar's projectkey. living-architecture.local.yaml, if pres

This is an excerpt. Refer to the complete source and its current requirements.