brownfield-validate

To validate brownfield code against approved OpenSpec artifacts, this Skill reads your specs, design, and changed source files to produce evidence-based pass or fail results for gap, design, and implementation criteria. It checks for missing MUST and SHALL requirements, architectural drift, and coding-standard violations.

Design conformance checking for 1C change workflows verifies that your implemented code follows the intended architecture, module scope, and SQL or procedure patterns described in design.md. It detects architectural drift to ensure the implementation matches the approved design before archiving or merging.

You check 1C code for missing requirements and spec compliance gaps by running a gap validation that compares implemented code against approved specs. This Skill flags every MUST and SHALL requirement from the specifications that is absent from the changed source files.

Yes, you can use this validation tool for 1C development without external dependencies, as it operates with an empty dependencies list. It requires only your approved OpenSpec artifacts, design documents, and changed source files to generate a consolidated implementation quality review.

Yes, implementation validation reviews test coverage and coding standards for 1C changes. It examines changed files for syntax issues, common quality problems, and standard violations to confirm the completed code is ready for release.

The best way to audit implementation quality for brownfield changes is performing a structured review against approved OpenSpec artifacts. This consolidates gap analysis, design conformance checks, and coding-standard validation into one evidence-based report before archiving or merging.