skills.rest
BlocUnited-LLC
BlocUnited-LLCOFFICIAL
Explore all skills by this author →
GitHub

build-sequence-change

Review and manage workflow sequencing changes in Mozaiks extension_registry.

14|1|Updated Jan 8, 2026
Search Tags:#orchestration#control plane#contract validation#workflow sequencing#workflow registry#routing transitions#build journey
One-click install
npx skills add https://github.com/BlocUnited-LLC/mozaiks --skill build-sequence-change
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: build-sequence-change
Source: https://github.com/BlocUnited-LLC/mozaiks/tree/main/.claude/skills/build-sequence-change
Command: npx skills add https://github.com/BlocUnited-LLC/mozaiks --skill build-sequence-change

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Changing workflow sequencing, transitions, or entrypoints in Mozaiks can silently break build journeys, routing, contracts, and downstream artifacts without obvious failures, creating costly debugging and rollout risk.

Core Features & Use Cases

  • Workflow-sequence impact review: Determine which build journey truth objects are affected, including cross-workflow workflow_sequence changes and their propagation needs.
  • Routing and contract alignment: Verify and update the correct routing/entry surfaces such as control_plane.yaml, extension_registry.json, and related orchestration/handoff configuration across affected workflows.
  • Downstream and test readiness: Identify impacted downstream artifacts, required tests, and rollback risk before you commit the change.

Quick Start

Ask the AI to review and implement your specified workflow_sequence/transition/entrypoint change summary and list exactly what files, workflows, artifacts, and tests must be updated.

Frequently Asked Questions about build-sequence-change

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

FAQPage Schema
How do I change workflow sequencing in Mozaiks without breaking routing or contracts?▼

To safely change workflow sequencing in Mozaiks, inspect the extension registry JSON and architecture routing documents to review impacted build journeys. You must update orchestrator and handoff YAMLs across affected workflows to ensure consistent routing, contract validation, and control-plane alignment before committing the change.

What causes silent build journey failures when updating extension_registry transition routing?▼

Silent build journey failures occur when modifying workflow transitions or entrypoints without aligning control-plane routes and orchestration handoff YAMLs. These sequence-driven changes can break downstream artifacts and workflow contracts without throwing obvious errors, creating costly debugging and rollout risk during deployment.

When do I need to review workflow sequence impact before modifying build journey entrypoints?▼

You need workflow sequence impact review whenever build truth is workflow-sequence-driven and you modify entrypoints. This review identifies affected build journey truth objects, maps cross-workflow propagation needs, and returns a structured list of impacted workflows, transitions, downstream artifacts, tests, and rollback risk.

How do I identify downstream artifacts and rollback risk before committing a workflow sequence change?▼

Identify downstream artifacts and rollback risk by inspecting the extension registry JSON and routing orchestration documents to trace cross-workflow propagation. This review returns a structured list of impacted workflows, transitions, entrypoints, downstream artifacts, required tests, and rollback risk before you commit the change.

What files must I update when changing control plane routing and workflow transitions in a Mozaiks repository?▼

When changing control plane routing and workflow transitions, you must update the extension_registry JSON, control_plane.yaml, and related orchestrator and handoff YAMLs for impacted workflows. This ensures routing alignment and contract validation across the entire build journey composition.

Can I update workflow bundles and entrypoints independently of the extension registry JSON?▼

No, workflow bundles and entrypoints cannot be updated independently of the extension registry JSON. Because build truth is workflow-sequence-driven, routing transitions require consistent updates across the registry, control-plane routes, and orchestration handoff YAMLs to prevent breaking build journey contracts.

Related Skills

Explore More Software Engineering Skills→
BlocUnited-LLCBlocUnited-LLC
14

factory-build-workflow-change

Review and implement Mozaiks factory build workflow changes with contract tests.

Official
Advanced
yutnayutna
2

quality-gates

Run type checks, linting, tests, and verification handoff in canonical order.

Community
Advanced
harkersharkers

control-plane-agent

Coordinate multi-agent handoff workflows with verification gates and standardized handoff packets.

Community
Advanced
zhongadamwangzhongadamwang

change-impact-analysis

Trace change propagation across EDPS process hierarchies and output impact JSON.

Community
Intermediate