Propagate design tokens across components
panim-ds-rolloutworkflowsetup L3★3
Y4NN777/mishkan-cc-harness ↗What it does
Propagate design token changes
Best for
Propagating design token changes across component consumers with a11y and visual regression gates.
Inputs
- · {args: workflow_config}
- · {token_change: {token, from, to}}
Outputs
- · [{components: changed, verdicts: reviewed}]
- · {summary: string, results: array}
Requires
- · multi-agent orchestration
Preconditions
- · agent harness configured
- · design system with discoverable consumers
Failure modes
- · worktree merge conflict unresolvable
- · one parallel agent fails -> cascade
- · verification gate rejects all changes
- · output fails JSON schema validation
Trust signals
- · Built-in adversarial verification step
- · Multi-lens review (orthogonal expert panels)
- · Explicit JSON schemas with required fields