gsd-modify

Guide safe GSD system modifications by checking invariants and verifying changes.

Updated May 11, 2025
One-click install
npx skills add https://github.com/rogsme/dotfiles --skill gsd-modify
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-modify
Source: https://github.com/rogsme/dotfiles/tree/main/.config/gsd/skills/gsd-modify
Command: npx skills add https://github.com/rogsme/dotfiles --skill gsd-modify

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill provides a guided workflow for safely modifying the GSD system, ensuring changes do not break existing functionalities or violate invariants.

Core Features & Use Cases

  • Safe Modification: Guides through the process of modifying the GSD system, including skills, subagent prompts, templates, and shared docs.
  • Impact Analysis: Maps the full seam impact surface before editing to avoid unintended consequences.
  • Contract Verification: Updates all contract counterparts together and verifies with bin/check.
  • Change Logging: Records a CHANGELOG entry for each modification.

Quick Start

Use the gsd-modify skill to change the GSD system by specifying what to modify.

Frequently Asked Questions about gsd-modify

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

FAQPage Schema
How do I safely modify system configuration and templates without breaking existing functionality?

Safe system modification requires checking changes against recorded invariants, mapping the impact surface before editing, and updating all contract counterparts together. This guided workflow prevents unintended violations across multiple files and components.

What is impact analysis in change management and when do I need it for code review?

Impact analysis in change management maps the full seam impact surface before editing to avoid unintended consequences. You need it when modifying subagent prompts, templates, or shared docs to ensure changes do not break existing functionalities or violate invariants.

How do I update contract counterparts and verify system modifications step by step?

Update all contract counterparts together when modifying the system, then verify the changes with bin/check. Finally, record a CHANGELOG entry for each modification to ensure coordinated changes across multiple files and components are fully tracked.

Does this guided modification workflow work for updating skills and subagent prompts?

Yes, this guided modification workflow applies to system configuration changes, skill updates, subagent prompts, template modifications, and shared docs within the framework. It ensures careful planning and coordination of changes across all these components.

What are the limitations of modifying a framework without checking recorded invariants?

Modifying a framework without checking recorded invariants risks breaking existing functionalities and violating system contracts. Without mapping the impact surface, changes across multiple files and components can cause unintended consequences that go undetected without verification.