Agent skill
aads-orchestrator
Coordinate multi-track AADS-ULoRA work by sequencing triage, architecture decisions, domain implementation tracks, and integration gates. Use when requests span modules, require explicit handoffs, or need dependency-aware validation planning.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/aads-orchestrator
SKILL.md
AADS Orchestrator
Workflow
- Decompose into tracks.
- Split request into independent workstreams.
- Mark dependencies and parallel candidates.
- Route tracks to skills.
- Status/scope:
aads-status-triage - Implementation:
aads-coder - Config/pipeline contracts:
aads-config-pipeline-guardrails - Router/OOD:
aads-router-ood-guardrails - Training:
aads-training-lifecycle - Docs/notebooks/scripts sync:
aads-colab-doc-sync - Architecture/contracts:
aads-architect
- Define checkpoints.
- Add merge checkpoints after each major track.
- Require explicit validation gate per track.
- Attach one owner file list and one owner test list per track.
- Run integration gates.
- Choose smallest cross-track validation set that proves end-to-end safety.
- Emit orchestration summary.
- Include track outcomes, unresolved risks, and next actions.
Output Contract
Return sections in this order:
- Track breakdown
- Dependency/order map
- Validation gates per track
- Integration checks
- Final risk register
- Recommended execution order
References
- Use
references/orchestration-matrix.mdfor routing logic and gate templates.
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?