carocut-shared-schema

What problem does it solve?

CaroCut's agent ecosystem relies on inconsistent data contracts across Planner, Media, Builder, and Orchestrator. This skill defines a centralized protocol registry and formal schemas to coordinate inputs, outputs, and validations, enabling reliable cross-component integration.

Core Features & Use Cases

• Resource Types Registry: standardizes resource definitions and consumption rules across all agents.
• Storyboard Schema & Dispatch Context: formalizes storyboard_schema.md and dispatch-context.md as canonical contracts used during planning and execution.
• Amendment Map: defines dependencies and impact chains for incremental changes across steps, improving traceability and rollback capabilities.
• Use Case: when adding new asset types or updating interaction rules, teams rely on the shared schema to maintain compatibility and reduce integration risk.

Quick Start

Enable all agents to share a canonical protocol by adopting the resources registry, storyboard schema, dispatch context, and amendment map.