rule-docker-shared-foundation-docs-sync-model-decision

Name: rule-docker-shared-foundation-docs-sync-model-decision
Availability: InStock
Author: belluga

Synchronize foundation documentation across routes, screens, repos, and domain models.

Updated Nov 7, 2025

Search Tags:#roadmap #architecture-docs #foundation-docs #scope-governance #contract-sync #todo-driven-execution

Ready to run

npx skills add https://github.com/belluga/delphi-ai --skill rule-docker-shared-foundation-docs-sync-model-decision

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: rule-docker-shared-foundation-docs-sync-model-decision
Source: https://github.com/belluga/delphi-ai/tree/main/.cline/skills/rule-docker-shared-foundation-docs-sync-model-decision
Command: npx skills add https://github.com/belluga/delphi-ai --skill rule-docker-shared-foundation-docs-sync-model-decision

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Foundation documentation often drifts when routes, screens, repos, or domain models change. This rule ensures canonical ownership and synchronized updates across all related surfaces.

Core Features & Use Cases

Enforces alignment by updating foundation_documentation/policies/scope_subscope_governance.md as canonical ownership source and refreshing foundation_documentation/modules/ and foundation_documentation/screens/ for new flows and UI behaviors.
Ensures explicit EnvironmentType, main scope, and subscope declarations; migrates touched legacy scopes marked Partial into the canonical module surface.
Notifies downstream teams by recording roadmap deltas before code merges and synchronizes API/contract changes in foundation_documentation/endpoints_mvp_contracts.md.

Quick Start

Update any touched contract surface (route, screen, repo, or domain model) and apply this rule so foundation docs reflect the new scope.

Frequently Asked Questions about rule-docker-shared-foundation-docs-sync-model-decision

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

FAQPage Schema

How do I keep foundation documentation synced with scope changes across routes and domain models?▼

To keep foundation documentation synced with scope changes, you update any touched contract surface like routes or domain models and apply a synchronization rule. This automatically refreshes module and screen docs to reflect new flows.

What is the best way to prevent foundation docs from drifting during API contract updates?▼

Preventing foundation docs from drifting during API contract updates requires synchronizing endpoints_mvp_contracts.md with any code changes. A canonical rule aligns these contract changes and records roadmap deltas before merges.

When do I need to update scope_subscope_governance.md for legacy scope migrations?▼

You need to update scope_subscope_governance.md when touching legacy scopes marked as Partial. This ensures explicit EnvironmentType and subscope declarations are migrated into the canonical module surface.

How to notify downstream teams of roadmap deltas before merging contract changes?▼

To notify downstream teams of roadmap deltas before merging, you apply a documentation synchronization rule. It records the roadmap changes and aligns API contracts before the code is officially merged.

Does updating system_roadmap.md require explicit subscope declarations for new UI behaviors?▼

Yes, updating system_roadmap.md for new UI behaviors requires explicit main scope and subscope declarations. The synchronization process refreshes screen documentation to ensure these new flows are properly captured.

Why does foundation documentation often become outdated after modifying repos or screens?▼

Foundation documentation becomes outdated because modifying repos or screens often bypasses canonical ownership policies. Applying a contract synchronization rule enforces alignment by automatically updating the related module and screen surfaces.