Build a tool that helps software teams determine what could break, disappear, or become more expensive when removing an existing product feature.
Allow users to supply feature flags, route definitions, source-code references, API specifications, configuration files, documentation, and available usage analytics.
Generate:
A feature dependency graph.
A map of routes, components, APIs, and workflows associated with the feature.
A comparison of static references and observed usage.
A detector for potentially orphaned code and documentation.
A list of consumers that may be affected by removal.
A staged retirement plan with compatibility checks.
A rollback and monitoring checklist.
A report of unresolved dependencies requiring human investigation.
Never claim that a feature is unused merely because static analysis finds no references. Distinguish verified dependencies from incomplete coverage, and treat missing telemetry as uncertainty. Do not remove code automatically. Include a sample application with an obsolete feature and deterministic dependency tests.
0 Comments