cr-analyze

You generate a CR proposal by describing the Change Request you want to analyze. The Skill deep-dives across backend, service, entity, DTO, and DB layers, producing current-code-logic, compare-logic, metadata, and proposal artifacts in a new change directory.

Code-vs-documentation comparison is the process of contrasting current code logic with existing documentation to identify discrepancies. It generates a compare-logic artifact that highlights differences to support CR scoping and documentation accuracy.

Yes, you can analyze multiple affected modules for a single Change Request. The Skill applies deep investigation across backend, service, entity, DTO, and data access layers, supporting multi-module scanning to generate comprehensive CR artifacts.

To use openspec for scaffolding, describe the Change Request you want to investigate. The Skill provides guidance on running openspec commands to create the CR context and generate the required artifacts directly in a new change directory.

Deep-dive code-change analysis generates four specific files: current-code-logic.md, compare-logic.md, metadata.yaml, and proposal.md. These artifacts are created in a new change directory to fully document the Change Request scope.