Skill Claude CodeCodex
Apply the relevant Dwi lenses together when several observed workflow problems co-occur. Select only the lenses the task needs, preserve a silent fast path for clear reversible work, and keep authority and evidence explicit. Prefer a focused module when one issue dominates.
Skill Claude CodeCodex
Structure genuinely multi-agent coding work into bounded cells with one writer per scope, explicit integration, and independent review. Use when several disjoint workstreams justify coordination. Do not use for small tasks, overlapping writers, speculative agent fleets, or process artifacts without demonstrated value.
Skill Claude CodeCodex
Coordinate bounded work between native Claude and Codex workflows with explicit authority, scope, and evidence. Use for read-only consultation or explicitly authorized execution delegation. Do not create a new connector, share secrets, treat messages as authorization, or allow recursive delegation.
Skill Claude CodeCodex
Set and report practical token, context, time, tool-call, and coordination boundaries for coding-agent work. Use when resource use is unclear or needs a checkpoint. Do not invent measurements, monetary savings, cache benefit, or precision that the harness does not expose.
Skill Claude CodeCodex
Make coding-agent communication clear, kind, and answerable. Use when questions are opaque, terms are unfamiliar, choices need a safe default, or a concrete interaction failure needs optional evidence-based repair. Do not use to invent feelings, assign blame, seek reassurance, or bypass permissions.
Skill Claude CodeCodex
Label coding-agent claims by evidence status, preserve provenance and failures, and separate static, runtime, and human proof. Use before completion, comparison, promotion, or handoff. Do not upgrade observations into guarantees or fabricate missing measurements and approvals.
Skill Claude CodeCodex
Keep planning, implementation, and testing proportionate to the actual coding task. Use when work is expanding into speculative architecture, broad exploration, repeated review, or excessive tests. Do not use to skip required safety, migration, release, or acceptance evidence.