xddp.feedback

To sync manual code changes back to a Change Requirements Specification, this Skill analyzes git diffs and document states to identify edits and automatically propagates them across the XDDP documentation hierarchy. It ensures consistency between implementation and requirements through automated traceability matrix regeneration and CRS updates.

Updating a traceability matrix after modifying implementation code is handled by synchronizing the manual edits back into the Change Requirements Specification. The Skill reflects adjustments from architecture, design, test, or code artifacts directly into the CRS, keeping the entire XDDP documentation suite in sync without manual overhead.

Code-to-design mapping works by analyzing git diffs from manual code adjustments and mapping them to specific design batches within the Change Design Documents. This bidirectional sync automatically reflects the implementation changes across the formal XDDP documentation hierarchy.

Yes, you can synchronize architecture, design, test, and code artifacts into the CRS. The Skill captures human-led refinements across all these project artifact types, ensuring that any manual adjustments are documented and consistency is maintained throughout the XDDP documentation suite.

Git diffs are used to identify and propagate manual design adjustments into the Change Requirements Specification, but document states are also analyzed to detect changes. This dual approach allows the Skill to capture human-led refinements accurately across the XDDP documentation hierarchy.

Your XDDP documentation hierarchy falls out of sync because manual code modifications made during debugging are not automatically captured in the formal Change Requirements Specification. Running a feedback sync analyzes these git diffs and updates the corresponding design specifications to restore consistency.