Loading...
Loading...
Found 12 Skills
Only to be triggered by explicit /parallel-task commands.
Execute all plans in a phase with wave-based parallelization, running phase execution, or completing phase work. Triggers include "execute phase", "run phase", "execute plans", "run the phase", and "phase execution".
Only to be triggered by explicit super-swarm commands.
This skill should be run only when the user explicitly invokes it. Orchestrates end-to-end task implementation — understands the task, assesses complexity, implements directly or via a team of subagents for complex work, and always finishes with a code-polish pass.
Mandatory protocol for dispatching any built-in and custom agent in this project via the task tool. Use this skill EVERY TIME you are about to call the task tool with a custom agent_type. This skill ensures the agent's intended model (declared in its YAML frontmatter) is respected rather than overridden by a default. Also encodes prompting best practices for subagent context and quality. ALWAYS invoke before any task tool call that targets a custom agent — even if the agent name seems obvious.
Vi — HR Specialist and Execution Orchestrator for MEL/SRHR work. Receives an approved plan from Ann (or directly from Ane), designs the specialist roster, spawns specialists as subagents, reviews their outputs, compiles the final product, and returns it. General-purpose — invoked by Ann via Agent tool, or directly by Ane when a plan is already approved.
Activate orchestrator mode for complex multi-task work using subagents. Use when you need to coordinate multiple independent Task subagents to accomplish work while keeping the main context window clean.
Orchestration workflow for orchestrator role ONLY. Use when: - Agent's role name (tmux pane title) is "orchestrator"
Create AiderDesk agent profiles via interactive Q&A.
Execute plan files by launching multiple parallel subagents to complete tasks simultaneously. Triggers on explicit "/parallel-task" commands.
Guide spec-driven development workflow (Requirements → Design → Tasks → Implementation) with approval gates between phases. Use when user wants structured feature planning or says "use spec-driven" or "follow the spec process".
Execute all plans in a phase with wave-based parallelization