product-thinking

Validate CLI command changes by evaluating surface impact, ensuring proposed modifications are necessary, durable, and compatible with existing configurations before writing code. This prevents poorly justified or breaking changes to public-facing interfaces.

Surface impact analysis for API contracts evaluates whether a proposed change to public-facing schemas is necessary and durable. It ensures architectural decisions require product-level justification before code implementation begins.

Add telemetry to new CLI features by defining a success metric during the planning phase. Every new user-facing feature must be instrumented with telemetry before implementation to track its effectiveness.

You need product-level justification for configuration schema changes when modifying public-facing surfaces like JSON report schemas or config files. This ensures changes adhere to runbook steps for trust and compatibility.

Yes, you can verify if an existing configuration option can be reused before adding a new one. This process checks doctor.config.ts entries to prevent unnecessary surface area expansion and ensure architectural durability.

The validation of public-facing software surfaces is limited to CLI commands, configuration schemas, and API contracts. It requires strict adherence to predefined runbook steps and cannot bypass the product-level justification phase.