adapt-system

Propose cascading diffs across configuration and governance artifacts for user approval.

Updated Apr 17, 2026

Search Tags:#automation #labels #diff-preview #tracker-sync #adapt-system #ops.config.json #memory-seeds

Ready to run

npx skills add https://github.com/ctxr-dev/agent-staff-engineer --skill adapt-system

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: adapt-system
Source: https://github.com/ctxr-dev/agent-staff-engineer/tree/main/skills/adapt-system
Command: npx skills add https://github.com/ctxr-dev/agent-staff-engineer --skill adapt-system

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reshapes a live project installation when the context changes by proposing cascading diffs across ops.config.json, labels, templates, rules, and memory seeds. It outputs diffs for review and applies only after explicit user approval, keeping changes auditable and idempotent.

Core Features & Use Cases

Proposes cascading diffs across configuration and governance artifacts (ops.config.json, labels, templates, rules, memory seeds) without applying them automatically.
Generates a label reconciliation plan and memory-seed updates that reflect the requested project-shape changes.
Handles ambiguous intents with an explicit halt and user clarification to prevent unsafe mutations.

Quick Start

Describe the requested project-shape change and run Adapt-System to preview the cascading diff for your project.

Frequently Asked Questions about adapt-system

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

FAQPage Schema

How do I automate project configuration updates when changing tech stack or compliance requirements?▼

Automate project reshaping by generating cascading diffs across ops.config.json, labels, templates, rules, and memory seeds to preview required configuration updates before applying them.

What is a cascading diff preview for project governance artifacts?▼

A cascading diff preview shows proposed changes across ops.config.json, labels, templates, rules, and memory seeds simultaneously, allowing you to review project-shape mutations before approval.

How do I safely update ops.config.json and label state after dropping dependencies?▼

Safely update ops.config.json and label state by generating a preview diff and label reconciliation plan that reflects dropped dependencies, applying changes only after explicit user approval.

Can I preview template and memory-seed changes without applying them automatically?▼

Yes, you can preview template and memory-seed changes without automatic application; the system outputs a diff for review and halts on ambiguous intents to prevent unsafe mutations.

Does the project reshaping process require access to current label state via tracker-sync?▼

Yes, project reshaping requires access to current label state via tracker-sync, ops.config.json, and the bundle's templates, rules, and memory seeds to generate accurate cascading diffs.

When should I avoid automated cascading diffs for project installation updates?▼

Avoid automated cascading diffs when intents are ambiguous; the system halts for user clarification to prevent unsafe mutations, ensuring changes remain auditable and idempotent.