xddp.feedback

Name: xddp.feedback
Availability: InStock
Author: tsuna44

Synchronize manually edited project artifacts back into the Change Requirements Specification.

Updated Mar 28, 2026

Search Tags:#automation #documentation #specification #sync #traceability #xddp

Ready to run

npx skills add https://github.com/tsuna44/XddpSettings --skill xddp-feedback

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: xddp.feedback
Source: https://github.com/tsuna44/XddpSettings/tree/main/ClaudeCode/.claude/skills/xddp.feedback
Command: npx skills add https://github.com/tsuna44/XddpSettings --skill xddp-feedback

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill bridges the gap between manual code or design adjustments and the formal Change Requirements Specification (CRS), ensuring that human-led refinements are captured and documented without manual overhead.

Core Features & Use Cases

Bidirectional Sync: Automatically reflects manual edits from architecture, design, test, or code artifacts back into the CRS.
Code-to-Design Mapping: Synchronizes code changes with Change Design Documents (CHD) by analyzing git diffs and mapping them to specific design batches.
Use Case: After debugging a test failure and modifying the implementation code, use this skill to automatically update the corresponding design specifications and traceability matrix, keeping the entire XDDP documentation suite in sync.

Quick Start

Execute the feedback command by specifying the CR number and the artifact type to synchronize your manual changes back to the specification.

Frequently Asked Questions about xddp.feedback

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I sync manual code changes back to a Change Requirements Specification?▼

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.

What is the best way to update a traceability matrix after modifying implementation code?▼

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.

How does code-to-design mapping work when synchronizing artifacts to XDDP specifications?▼

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.

Can I synchronize architecture and test artifacts along with code edits into the CRS?▼

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.

Do I need git to propagate manual design adjustments into the Change Requirements Specification?▼

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.

Why does my XDDP documentation hierarchy fall out of sync after debugging a test failure?▼

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.