service-modify

Modify and migrate service specifications and documentation across API, data model, and dependency changes.

Updated Apr 2, 2026
One-click install
npx skills add https://github.com/oogDZ/2 --skill service-modify
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: service-modify
Source: https://github.com/oogDZ/2/tree/main/.claude/skills/service-modify
Command: npx skills add https://github.com/oogDZ/2 --skill service-modify

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams update service specifications and documentation consistently when APIs, data models, or dependencies change. It deactivates docs when a service is removed and migrates docs on renaming.

Core Features & Use Cases

  • Update and standardize specs/docs for a service across API endpoints, data models, dependencies, and tech stack.
  • Deactivate documentation when a service is deleted to avoid stale references.
  • Migrate documentation and references when a service is renamed to preserve traceability and history.

Quick Start

Provide the service name and optional --scenario flag to start updating the service's specs and documentation.

Frequently Asked Questions about service-modify

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

FAQPage Schema
How do I update service documentation when API endpoints change?▼

To update service documentation when API endpoints change, you apply a standardized modify-service workflow that enforces SSOT-aligned templates, ensuring specs and docs remain consistent and traceable across endpoint updates.

What is the best way to migrate documentation when renaming a service?▼

Migrating documentation when renaming a service involves updating the service specifications and transferring all existing references, preserving historical traceability while preventing stale documentation from lingering under the old name.

How do I deactivate documentation for a deleted service to avoid stale references?▼

You deactivate documentation for a deleted service by applying a standardized workflow that safely removes or marks specs as inactive, ensuring no stale references remain in the system's single source of truth.

Can I use a single workflow to update specs across data models, dependencies, and tech stack reorganizations?▼

Yes, you can update specs across data models, dependencies, and tech stack reorganizations using a unified workflow that applies SSOT-aligned templates to guide changes end-to-end and maintain consistency.

What do I need to start updating service specifications and docs?▼

To start updating service specifications and docs, you need to provide the target service name and an optional scenario flag, which triggers the modify-service workflow to guide the required changes end-to-end.

Why does service specification migration enforce SSOT-aligned templates?▼

Service specification migration enforces SSOT-aligned templates to guarantee that all documentation changes remain consistent with the single source of truth, preventing fragmented or contradictory specs during API and data model updates.