specops-ambiguity-audit

To audit ambiguities in a legacy code specification, run an ambiguity audit that scans the SpecOps analysis file to locate undecided behaviors and missing thresholds, then resolves them by reading source code. It outputs a patched spec with concrete resolutions.

Common ambiguities in legacy code specs include undecided behaviors, missing thresholds, and potential policy gaps. The audit identifies these ambiguity candidates systematically, ensuring each judgment call is documented and mitigated with concrete evidence from the source.

Yes, you can use parallel processing to resolve spec gaps in legacy source code. The audit spawns parallel subagents to simultaneously examine legacy source files and patch the spec accordingly, generating a concrete patch plan based on source evidence.

The best way to log open questions when auditing legacy specifications is to use an automated open questions logging mechanism. It records deferred ambiguities for out-of-band resolution, ensuring traceability and a concrete, auditable spec analysis.

No, the ambiguity audit does not require external dependencies to patch a SpecOps file. It operates with zero dependencies, orchestrating internal subagents to read relevant legacy source code and generate a concrete patch plan with evidence automatically.

Ambiguities that cannot be resolved during the spec audit are logged as deferred items. The tool records these open questions for out-of-band resolution and traceability, while still outputting a patched spec with concrete resolutions and notes for the deferred items.