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

factory-build-workflow-change

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you review, implement, and integrate changes to Mozaiks’ factory build workflow system without breaking workflow sequencing, transition/entrypoint routing, artifact ownership, or build lifecycle integration.

Core Features & Use Cases

  • Workflow sequencing governance: Update workflow_sequence-driven build journey steps via the extension registry while preserving dependency order and artifact-family ownership.
  • Transition/entrypoint correctness: Add or modify transitions and entrypoints with the right routing semantics (route-time user choice vs workflow-local agent routing).
  • Generator contract alignment: Change AppGenerator and AgentGenerator behaviors while honoring tool/file contracts and expected generated artifact shapes.
  • Build lifecycle hook integration: Adjust build lifecycle surfaces and shared workflow glue with tests that validate sequence-position payload semantics.
  • Existing app adoption integrity: Apply changes to ExistingAppDiscovery while keeping brownfield/adoption journeys distinct from greenfield builds.
  • Refinement/control-plane linkage: Ensure routes and refinement/control-plane linkage stay consistent with the declared workflow sequence source of truth.

Quick Start

Ask your AI to review and update the specific workflow sequence, transition, entrypoint, or generator contract described in this change request, then identify the narrowest test slice to run before proposing the patch.

Frequently Asked Questions about factory-build-workflow-change

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

FAQPage Schema
How do I safely update build workflow sequencing without breaking artifact routing?▼

To safely update build workflow sequencing, modify workflow_sequence steps via the extension registry while preserving dependency order and artifact-family ownership. This maintains registry-driven routing semantics and prevents contract drift across the build pipeline.

What is the difference between route-time user choice and workflow-local agent routing in transitions?▼

Route-time user choice determines transitions dynamically during execution, whereas workflow-local agent routing handles transitions internally within the workflow. Correctly applying these routing semantics ensures entrypoint validity and build journey integrity.

How do I modify AppGenerator and AgentGenerator behaviors while honoring file contracts?▼

To modify AppGenerator and AgentGenerator behaviors while honoring file contracts, apply changes that respect expected generated artifact shapes. Run narrowly scoped contract tests to validate generator contract alignment and minimize drift.

Can I adjust build lifecycle hooks without disrupting sequence-position payload semantics?▼

Yes, you can adjust build lifecycle hooks by validating sequence-position payload semantics with targeted lifecycle tests. This ensures build lifecycle integration changes remain consistent with the declared workflow sequence source of truth.

Does changing ExistingAppDiscovery affect greenfield build workflows?▼

Changing ExistingAppDiscovery applies to brownfield/adoption journeys and keeps them distinct from greenfield builds. This existing app adoption integrity ensures standard greenfield build workflow sequencing remains unaffected.

Why do transition routing changes cause contract drift in build pipelines?▼

Transition routing changes cause contract drift in build pipelines when routing semantics violate registry-driven rules or workflow layering boundaries. Validating transitions against the declared workflow sequence source of truth prevents this drift.

Related Skills

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

build-sequence-change

Review and manage workflow sequencing changes in Mozaiks extension_registry.

Official
Advanced
espensevespensev

ship

Execute tightly scoped code edits and patches within repositories.

Community
Intermediate
BlocUnited-LLCBlocUnited-LLC
14

control-plane-refinement-change

Evaluates Tailwind code and produces a report of detected smells and inconsistencies.

Official
Advanced
crissdiamondcrissdiamond

crisai-semantic-registry-reference

Reference crisAI semantic registry vocabulary, graph structures, and routing semantics.

Community
Advanced