bootstrap-ops-config

You can generate an ops.config.json by running a guided bootstrap that detects project context from git, GitHub, and filesystem signals. It conducts an interactive interview to fill gaps, validates the result against the ops.config schema, and shows a diff before writing the file.

Bootstrapping ops configuration after a fresh clone is best handled by a guided interview. It detects existing git and GitHub state to seed initial values, asks about work tracking and release planning, then produces a validated config file alongside an interview transcript for your records.

No, the ops.config bootstrap process never mutates GitHub or pushes changes. It strictly writes non-destructive files locally, providing a configuration diff and an interview transcript for review without altering your remote repository state.

You can use the interactive configuration bootstrap for both existing projects and fresh clones. It detects project context from git and GitHub state regardless of age, guiding you through detection, interview, diff preview, and optional apply to generate a complete ops configuration.

During an ops.config.json interview, you provide details covering work tracking, release planning, e2e setup, and compliance context. The process auto-detects what it can via git, gh, and filesystem signals, then interviews you only on the remaining gaps needed for schema validation.

Schema validation ensures the output from the interactive interview conforms to the ops.config schema before writing. The process validates the resulting config, outputs a diff for review, and only writes non-destructive files locally if you choose to apply the changes.