workflow-architecture-change

Name: workflow-architecture-change
Availability: InStock
Author: akourmaz

Coordinate architectural changes with ADRs, plans, and rollout gates.

Updated Mar 2, 2026

Search Tags:#architecture #adr #governance #plan #risk #change-management

Ready to run

npx skills add https://github.com/akourmaz/translate2 --skill workflow-architecture-change

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: workflow-architecture-change
Source: https://github.com/akourmaz/translate2/tree/main/.agents/skills/workflow-architecture-change
Command: npx skills add https://github.com/akourmaz/translate2 --skill workflow-architecture-change

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The protocol provides a structured approach to planning, validating, and executing major architectural changes, ensuring traceability and risk control.

Core Features & Use Cases

ADR creation and governance for significant design decisions.
Research and planning gates (STOP gates) to validate and approve changes before implementation.
Phase-based rollout with rollback strategies and clear responsibilities.

Quick Start

Initiate the Architecture Change Workflow by creating Research.md, ADR, and Plan.md and securing stakeholder approvals before starting any implementation.

Frequently Asked Questions about workflow-architecture-change

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

FAQPage Schema

How do I plan and govern major architecture changes across teams?▼

To govern major architecture changes, you enforce Architecture Decision Records (ADRs), detailed rollout plans, and stage-gated approvals to ensure traceability and risk mitigation across teams.

What is an architecture change workflow with STOP gates?▼

An architecture change workflow with STOP gates is a stage-gated process that validates and approves design decisions through Research.md, ADRs, and Plan.md files before implementation proceeds, ensuring strict risk control.

How do I create an ADR and rollback strategy for a technology migration?▼

You create an ADR and rollback strategy for a technology migration by documenting the design decision, securing stakeholder approvals, and defining phase-based rollout steps with clear rollback procedures before implementation.

When do I need to use ADRs and rollout gates for API changes?▼

You need ADRs and rollout gates for API changes when coordinating significant technology shifts or infrastructure upgrades that require stakeholder validation, structured planning, and risk mitigation across multiple teams.

What are the requirements to start an architecture change workflow?▼

Requirements to start an architecture change workflow include creating Research.md, an ADR, and Plan.md, along with securing stakeholder approvals at STOP gates before beginning any implementation phases.