/spdd-sync

Synchronize implementation details from refactored or updated code back to the structured SPDD (Structured Prompt-Driven Development) prompt file, ensuring the prompt remains the accurate source of truth for the system design.

Input: The argument after /spdd-sync is the path to the structured prompt file (e.g., @spdd/prompt/GGQPA-XXX-202602271430-[Feat]-api-create-agent-endpoint.md).

Steps

1. If no input provided, ask for the prompt file

   Use the AskUserQuestion tool to ask:

   "Please provide the path to the structured prompt file you want to sync (e.g., @spdd/prompt/xxx.md)."

   IMPORTANT: Do NOT proceed without a valid prompt file path.

2. Read and parse the structured prompt file

   Read the prompt file and identify the REASONS Canvas sections:

   Section	Purpose	Sync Priority
   R - Requirements	Overall goal and DoD	Low (rarely changes from code)
   E - Entities	Domain model and relationships	High (class diagrams may change)
   A - Approach	Implementation strategy	Medium (architectural decisions)
   S - Structure	Components and dependencies	High (inheritance/dependencies change)
   O - Operations	Concrete implementation tasks	Highest (implementation details)
   N - Norms	Engineering standards	Medium (patterns may evolve)
   S - Safeguards	Non-negotiable constraints	Low (constraints rarely relax)

   IMPORTANT: Operations section typically requires the most updates as it contains implementation specifics.

3. Identify affected components from user context

   Ask the user (if not already specified):

   "Which components were refactored? Please specify:

   • Specific files/classes that changed
   • Type of change (renamed, restructured, logic changed, new components added)
   • Brief description of what changed"

   Alternatively, analyze recent git changes or user-specified files to identify modifications.

4. Analyze current implementation

   For each affected component:

   a. Read the current implementation:

   • Locate the source file in the codebase
   • Extract class structure, methods, annotations
   • Identify relationships and dependencies

   b. Compare with prompt specification:

   • Find corresponding Operation/Entity/Structure section
   • Note discrepancies in:
     • Class names, package paths
     • Method signatures and return types
     • Attributes and their types
     • Annotations used
     • Business logic steps
     • Validation rules
     • Error messages

   c. Categorize changes:

   • Structural: Class hierarchy, dependencies, component relationships
   • Behavioral: Method logic, validation rules, error handling
   • Naming: Class/method/field renames
   • Additions: New methods, fields, or components
   • Deletions: Removed methods, fields, or components

5. Generate prompt update plan

   Create a detailed update plan showing:

   ## Prompt Sync Plan
   
   ### Entities Section Updates
   - [ ] Update: ClassName - added/removed/changed fields
   - [ ] Update: Relationship diagram - new dependency
   
   ### Structure Section Updates
   - [ ] Update: Inheritance relationships - ComponentX now extends BaseY
   - [ ] Update: Dependencies - ServiceA now depends on ValidatorB
   
   ### Operations Section Updates
   - [ ] Update: "Create ClassName" operation - new method signature
   - [ ] Update: "Create ClassName" operation - logic steps changed
   - [ ] Add: New operation for NewComponent
   - [ ] Remove: Obsolete operation description
   
   ### Norms Section Updates
   - [ ] Update: New pattern adopted (e.g., Chain of Responsibility)
   

   Present this plan to the user for review before proceeding.