rule-docker-docker-architecture-mode-transition-model-decision

Enforce a formal workflow for architecture mode changes with roadmap and policy updates.

Updated Nov 7, 2025
One-click install
npx skills add https://github.com/belluga/delphi-ai --skill rule-docker-docker-architecture-mode-transition-model-decision
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rule-docker-docker-architecture-mode-transition-model-decision
Source: https://github.com/belluga/delphi-ai/tree/main/.cline/skills/rule-docker-docker-architecture-mode-transition-model-decision
Command: npx skills add https://github.com/belluga/delphi-ai --skill rule-docker-docker-architecture-mode-transition-model-decision

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This rule ensures safe governance when changing architecture modes by enforcing a formal workflow and coordinated updates across roadmaps and canonical documentation.

Core Features & Use Cases

  • Run the Architecture Mode Transition Workflow (delphi-ai/workflows/docker/architecture-mode-transition-method.md) to synchronize mode changes with governance.
  • Update system_roadmap.md, affected canonical module docs, and governance policies per the workflow before declaring the new mode.
  • Coordinate with the Strategic / CTO-Tech-Lead profile to ratify changes and communicate downstream impacts.

Quick Start

When you need to change architecture mode, run the Architecture Mode Transition Workflow and update the roadmap and policies before declaring the new mode.

Frequently Asked Questions about rule-docker-docker-architecture-mode-transition-model-decision

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

FAQPage Schema
How do I govern Docker architecture mode transitions safely?

Architecture mode transitions require updating the system_roadmap.md, affected canonical module docs, and governance policies before declaring the new mode. This ensures all downstream teams recognize the architectural shift from Foundational, Operational, or Expansion states.

What is the process for changing Docker architecture modes?

The process involves running the Architecture Mode Transition Workflow to update system_roadmap.md, canonical module docs, and governance policies. You must coordinate with the Strategic or CTO-Tech-Lead profile to ratify changes and communicate downstream impacts.

When do I need to update the system_roadmap.md for architecture governance?

You must update the system_roadmap.md during any architecture mode transition to reflect changes across Foundational, Operational, or Expansion layers. This formalizes governance before declaring the new mode operational.

Who needs to ratify Docker architecture mode changes?

Docker architecture mode changes require ratification from the Strategic or CTO-Tech-Lead profile. This coordination ensures proper governance and enables downstream communication of impacts to affected teams.

Does declaring a new Docker architecture mode require policy updates?

Yes, declaring a new Docker architecture mode requires updating governance policies alongside canonical module docs and the system_roadmap.md. These updates must be completed through the formal transition workflow before the mode declaration.