Agent skill
aads-router-ood-guardrails
Handle router, ROI, policy-taxonomy, and OOD updates in AADS-ULoRA while preserving stage-order behavior and Phase 5 latency guardrails. Use for changes under src/router, src/ood, policy regression scripts, or phase5 performance guardrail scripts and config.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/aads-router-ood-guardrails
SKILL.md
AADS Router and OOD Guardrails
Workflow
- Scope behavior impact.
- Classify change as routing logic, taxonomy/policy behavior, OOD behavior, or performance.
- Load
references/router-guardrails.md.
- Preserve invariants.
- Preserve stage ordering unless explicitly requested.
- Preserve focus-mode fallback semantics.
- Preserve taxonomy normalization semantics.
- Implement with minimal churn.
- Touch only required router/OOD files.
- Run required validation.
- Router unit tests, OOD tests, and policy regression bundle.
- Add profile sanity checks for policy profile changes.
- Run performance gates when runtime path changed.
- Benchmark and guardrail checker.
- Emit behavior delta summary.
- Explicitly classify changes as breaking or non-breaking.
Output Contract
Return sections in this order:
- Changed router/OOD surfaces
- Invariants checked
- Validation commands and results
- Performance gate results (or skip reason)
- Breaking/non-breaking classification
- Residual risk notes
References
- Read
references/router-guardrails.mdfor invariants and command matrix.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?