/spdd-prompt-update

Update an existing SPDD (Structured Prompt-Driven Development) prompt file with new requirements, architectural changes, or refinements while maintaining the REASONS Canvas structure and following all specification rules.

Input: The argument after /spdd-prompt-update includes the prompt file reference and the update instructions.

Examples:

# Update with architectural principles
/spdd-prompt-update @spdd/prompt/GGQPA-XXX-202603131758-[Feat]-api-token-usage-billing.md
Add three-layer architecture with dependency inversion principle

# Update with new requirements
/spdd-prompt-update @spdd/prompt/GGQPA-XXX-202603131758-[Feat]-api-token-usage-billing.md
Add support for batch usage submission

# Update specific section
/spdd-prompt-update @spdd/prompt/GGQPA-XXX-202603131758-[Feat]-api-token-usage-billing.md
Update Safeguards section to add rate limiting constraints

Steps

1. Validate input

   a. If no prompt file provided, use the AskUserQuestion tool to ask:

   "Please provide the path to the SPDD prompt file to update (e.g., @spdd/prompt/xxx.md)"

   b. If no update instructions provided, use the AskUserQuestion tool to ask:

   "What changes would you like to make to this prompt? (e.g., new requirements, architectural changes, constraint updates)"

   IMPORTANT: Do NOT proceed without both the file path and update instructions.

2. Read and analyze the existing prompt

   a. Read the entire SPDD prompt file b. Identify all existing REASONS sections:

   • Requirements
   • Entities
   • Approach
   • Structure
   • Operations
   • Norms
   • Safeguards c. Understand the current architecture, entities, and constraints

3. Analyze the update request

   Determine which sections need to be updated based on the change request:

   Change Type	Affected Sections
   New functional requirement	R, E, A, S, O, possibly N, S
   Architectural change	A, S, O, N
   New entity/relationship	E, S, O
   New constraint/safeguard	S (Safeguards), possibly O
   Coding standard change	N, O
   Bug fix in specification	Targeted section only

4. Read relevant codebase context (if needed)

   If the update involves:

   • New entities → Read existing entity classes
   • New patterns → Read existing similar implementations
   • New integrations → Read related services/repositories

5. Apply updates to affected sections

   For each affected section:

   a. Preserve unchanged content - Do NOT rewrite sections that don't need changes b. Integrate changes coherently - Ensure new content fits with existing content c. Maintain consistency - Cross-check that changes are reflected across related sections d. Follow REASONS construction guidance - Apply the same quality standards as initial generation

   Section-specific guidance:

   • Requirements: Update if business goal changes
   • Entities: Add/modify entities, update Mermaid diagram
   • Approach: Update strategies, add new architectural decisions
   • Structure: Update inheritance, dependencies, layered architecture
   • Operations: Add new operations, modify existing operation specifications
   • Norms: Add new standards, update package structure
   • Safeguards: Add new constraints, update existing rules

6. Validate cross-section consistency

   After updates, verify:

   • Entities mentioned in Operations exist in Entities section
   • Dependencies in Structure match what's described in Operations
   • Constraints in Safeguards are enforceable based on Operations
   • Norms are applied consistently across Operations

7. Write the updated prompt file

   a. Overwrite the existing file with the updated content b. Preserve the original filename (do NOT rename)

8. Show update summary

   ✅ SPDD prompt updated: `spdd/prompt/<file-name>.md`
   
   📋 Changes made:
   - [Section]: [Summary of changes]
   - [Section]: [Summary of changes]
   
   🔍 Sections unchanged:
   - [List of sections that were not modified]
   
   ⚠️ Review recommendations:
   - [Any areas that may need manual review]