Verified:GitHub

control-plane-refinement-change

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

14|1|Updated Jan 8, 2026

Search Tags:#artifact routing #control plane #pytest validation #ai workflow orchestration #refinement routing #checkpoint re-entry #workflow sequence

Ready to run

npx skills add https://github.com/BlocUnited-LLC/mozaiks --skill control-plane-refinement-change

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: control-plane-refinement-change
Source: https://github.com/BlocUnited-LLC/mozaiks/tree/main/.claude/skills/control-plane-refinement-change
Command: npx skills add https://github.com/BlocUnited-LLC/mozaiks --skill control-plane-refinement-change

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you review or implement changes to Mozaiks control-plane and refinement routing without breaking build-sequence re-entry, artifact routing ownership, or checkpoint semantics.

Core Features & Use Cases

Change-impact discovery: Pinpoints which contract/config files and runtime guidance are affected when control-plane, refinement routing, or checkpoint re-entry behavior changes.
Routing correctness enforcement: Keeps workflow_sequence routing aligned with extended_orchestration/extension_registry.json and preserves the intended separation between checkpoints, transitions, and workflow-local handoffs.
Test-first validation: Guides you to run the narrowest matching tests that validate loader behavior, refinement routing derivation, pack path resolution, and build lifecycle hooks.

Quick Start

Use this skill to review a proposed change by identifying the impacted control-plane/refinement surfaces and then running the specified pytest targets to produce an OSS Change Impact final report.

Frequently Asked Questions about control-plane-refinement-change

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

FAQPage Schema

What is refinement routing in AI workflow orchestration?▼

Checkpoint re-entry requires workflow sequences to exist in extension registries. It separates checkpoints from handoffs, ensuring build-sequence re-entry preserves artifact routing ownership and refinement classification behavior.

How do I validate control-plane configuration changes without breaking workflow sequences?▼

Routing correctness enforcement keeps workflow sequences aligned with extension registries. It preserves separation between checkpoints, transitions, and handoffs, preventing broken build-sequence re-entry.

Does this workflow orchestration approach support pytest validation for artifact routing?▼

Yes, pytest validation targets loader behavior, refinement routing derivation, pack path resolution, and build lifecycle hooks. It confirms control-plane modifications satisfy strict refinement routing and checkpoint requirements.

Why does my refinement routing change fail the workflow sequence extension registry check?▼

Checkpoint failures occur when checkpoints conflate with workflow-local handoffs. Separating these transitions and keeping declarative families on the workflow sequence restores correct re-entry behavior.

Can I use control-plane refinement for patch, design, feature, and core changes?▼

Change-impact discovery pinpoints affected contract, config, and runtime guidance files. It maps control-plane modifications to artifact ownership routing and checkpoint behavior before validation.

What is the best way to route refinement changes across multiple workflow classifications?▼

Test-first validation guides execution of the narrowest matching pytest targets. It validates pack path resolution and build lifecycle hooks, producing targeted test execution guidance for the change.