spdd-prompt-update

Update SPDD prompts with new requirements while preserving REASONS Canvas structure.

Updated Jun 17, 2026
One-click install
npx skills add https://github.com/gabbello/medicine-plan --skill spdd-prompt-update-gabbello
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spdd-prompt-update
Source: https://github.com/gabbello/medicine-plan/tree/main/.agents/skills/spdd-prompt-update
Command: npx skills add https://github.com/gabbello/medicine-plan --skill spdd-prompt-update-gabbello

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the need for efficiently updating existing SPDD prompt files with new requirements or architectural changes while preserving the integrity of the REASONS Canvas structure.

Core Features & Use Cases

  • SPDD Prompt Updates: Facilitates modifications to SPDD prompts without altering the original design.
  • Automated Validation: Checks for cross-section consistency to maintain quality and reliability.
  • Update Examples: Supports adding new architectural principles, incorporating new requirements, or updating specific sections of an existing prompt.

Quick Start

Use the 'spdd-prompt-update' skill to update the SPDD prompt file at path 'spdd/prompt/GGQPA-XXX-202603131758-[Feat]-api-token-usage-billing.md' with the change: 'Add three-layer architecture with dependency inversion principle'.

Frequently Asked Questions about spdd-prompt-update

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

FAQPage Schema
How do I update SPDD prompt files with new architectural changes?

Update SPDD prompts by providing a file path and change request, which modifies the content while preserving the REASONS Canvas structure and enforcing specification rules.

Can I add new requirements to an existing SPDD prompt without breaking the original design?

Yes, adding new requirements to an SPDD prompt preserves the original REASONS Canvas structure. Automated validation checks cross-section consistency to maintain quality and reliability.

What is the best way to maintain cross-section consistency when modifying specifications?

Maintain cross-section consistency during specification updates by using automated validation. This checks structural integrity across the REASONS Canvas when incorporating new architectural principles.

How do I add a dependency inversion principle to an existing architecture specification?

Add architecture principles by passing the change request to the SPDD update workflow. It integrates the dependency inversion principle directly into the existing prompt file.

Does the SPDD update workflow support command-line file references?

Yes, the SPDD update workflow supports command-line based file referencing. You can target specific prompt files by providing their path for localized architectural refinements.