skill-compliance

Skill routing stops wrong language defaults in a monorepo by identifying the task type, affected files, and active languages first, then loading the correct workflow and language-specific skills without cross-contaminating defaults.

Mandatory acknowledgement in workflow compliance requires reading telemetry first, then loading and confirming all relevant skills and references to the user before any code edits or generation begin.

To start a task using polyglot pre-routing, ask the agent to begin and require it to first confirm the task summary, loaded skills, routing basis including files and languages, and any exclusions before it edits or generates any code.

Workflow compliance handles pre-existing violations by treating silence as unacceptable, requiring the agent to either fix the violation or explicitly report it with next steps when the issue is out of scope.

Reading telemetry first satisfies procedural requirements to confirm loaded skills and routing basis, preventing incorrect or missing development discipline by forcing the agent to identify the task and affected files before doing any work.

You need explicit task routing for development discipline in a monorepo when starting tasks in mixed-language contexts where wrong language defaults can leak, ensuring the correct workflow and language standards apply.