legacy-spec-writer

Generating evidence-backed specifications involves translating post-BRD business capabilities into platform-agnostic spec.yaml and spec.md artifacts. The process merges the approved BRD Package with module and flow analyses to define declarative business rules and target data models.

The best way to document business rules for a legacy system capability spec is by constructing a declarative spec.yaml. These rules must be explicitly confirmed by SMEs and grounded in legacy code analysis or SME validation to ensure spec alignment.

Yes, an approved BRD Package is required to create capability specifications. The Skill merges this package with module and program analyses to identify capabilities, requiring accurate discovery data and explicit SME validation to bridge post-BRD gaps.

Legacy data model mapping works by connecting legacy data structures to target entities within the specification. This maintains data lineage and constraints while ensuring alignment with new architecture decisions and the operational behavior of the business capability.

Yes, you can use this approach for post-BRD discovery because it specifically bridges gaps between the approved BRD and technical implementation. It utilizes various artifacts produced by downstream and related analysis skills to ensure accurate spec alignment.

Without SME validation, generating modernization specifications lacks the explicit confirmation needed for declarative business rules and spec alignment with legacy behaviors. The process depends on accurate data and validation to produce evidence-backed, platform-agnostic specifications.