Astra orchestrator

Managing complex code changes requires precise coordination to avoid overlapping edits and wasted compute. The Astra Orchestrator skill manages implementation tasks by delegating work to native subagents with strict contracts and independent verification. It eliminates the friction of manual multi-file coordination by planning the route, spawning specialized workers, and conducting a final review before merging.

What it does

• Route selection determines the most efficient path between primary agents, implementers, and reviewers based on task size.
• Contract delegation provides subagents with exact file ownership, behavior requirements, and boundary constraints to prevent scope creep.
• Native subagent spawning utilizes host tools to launch specialized profiles for implementation (Luna) and independent review (Astra).
• Automated verification runs acceptance checks on diffs and generated files before proceeding to formal review.
• Independent review cycles trigger a fresh Astra reviewer to validate changes against the original goal without allowing self-repair.

How it works

1. Plan the implementation by inspecting the working tree and selecting the appropriate worker route.
2. Delegate specific behaviors and file paths to a Luna subagent using native spawn tools.
3. Verify the output by inspecting diffs and running defined checks, requesting repairs if necessary.
4. Review the final result using an independent Astra reviewer to get a final accept or fix verdict.

Frameworks & tools

This skill is designed for environments supporting native subagent tools (spawn, message, wait) and specific worker profiles like astra_luna_worker and astra_review. It integrates directly with host permissions and file systems.

Why this beats prompting it yourself

Manual orchestration often leads to agents overwriting each other's work or losing context during delegation. This skill enforces strict file ownership and independent review stages, ensuring that code is not just written, but verified by a separate model instance before you ever see it.

Use cases

• Multi-file features where one agent implements logic while another handles documentation or integration.
• Critical path updates that require an independent Astra review for high-assurance code quality.
• Codebase refactoring where specific subagents are assigned bounded directories to prevent global side effects.
• Parallel development of independent modules that need central coordination and verification.

Known limitations

Requires a host with native subagent tool support. Cannot switch the primary model of an existing conversation or access token usage data without specific host tool support.