Enforce a specification-first workflow with role-based transitions in dx-managed repositories.
npx skills add https://github.com/dewitt/dx --skill dx-orchestrator
Please help me install this Agent Skill. Skill: dx-orchestrator Source: https://github.com/dewitt/dx/tree/main/skills/dx-orchestrator Command: npx skills add https://github.com/dewitt/dx --skill dx-orchestrator
This skill prevents semantic drift and silent failures in AI-assisted software development by enforcing a strict, declaration-first workflow where the specification acts as the single source of truth.
Invoke the dx-orchestrator skill to analyze the current repository and determine the appropriate role for the requested development task.
High-intent search queries and answers about installing and using this skill.
To enforce specification-first workflows in AI-assisted coding, use a declarative orchestration skill that routes tasks through role-based phases to ensure code conformance with defined invariants. This prevents semantic drift by making the specification the single source of truth.
AI-generated code drifts from architectural design due to ad-hoc coding without explicit assumption logging or contract verification. An orchestrator prevents this by enforcing role-based transitions between design, implementation, and rigorous verification against defined contracts.
The best way to manage role-based transitions for AI coding agents is using a declarative orchestrator that automatically directs the AI to appropriate roles like architect, implementer, or judge based on the requested development task.
Prevent silent failures in AI-assisted software development by enforcing strict linting, assumption logging, and contract-based testing protocols. An orchestration workflow ensures all code generation is followed by rigorous verification against defined contracts.
Yes, you can use declarative orchestration to verify code against defined contracts by routing the task to a judge role that rigorously verifies the implementation against new contracts after the implementer writes the code.
Yes, in a declarative workflow you must log assumptions before generating code. Workflow enforcement ensures all code generation is preceded by explicit assumption logging to maintain system integrity and prevent semantic drift.
8DionysusIdentify and resolve documentation ambiguity to establish a single source of truth.
anderskevReview BubbleTea TUI code for Elm architecture conformance and Lipgloss styling.
alex-robert-frDefine and enforce a standardized AI-driven workflow contract between plugin and project.
RodrigoVeraCandiaRefactor legacy Angular components to standalone components, signals, and inject().
