/conduct

name: conduct
description: AL Conductor Agent - Orchestrates Planning → Implementation → Review → Commit cycle for AL Development. Enforces TDD and quality gates for Business Central extensions. Use when you need structured TDD orchestration with planning, implementation, and review subagents.
argument-hint: Feature description or requirements for TDD orchestration (e.g., "Add customer loyalty points system")

/aldc:conduct

<!-- Generated by scripts/sync-plugin-support.js from the al-conductor contract; edit ENTRY_SKILLS in the generator, not this file. -->

Read `${CLAUDE_PROJECT_DIR}/claude-plugin/agents/al-conductor.md` in full and act as that agent for the rest of this session; the Copilot-to-Claude Code mappings and the *Claude Code runtime rules* at the top of that file are binding. You stay the orchestrator in this main session because only the main session can launch subagents. **Orchestrating means delegating:** research goes to `aldc:al-planning-subagent`, each phase to `aldc:al-implement-subagent` and each review to `aldc:al-review-subagent`, through the `Agent`/`Task` tool, in the foreground. Never do that work yourself, even when the task looks small. If the host does not let you launch subagents, say so and stop; do not simulate the subagents. For an enforced tool list, launch `claude --agent aldc:al-conductor` instead.

Input: **$ARGUMENTS**

Requirement artifacts live under `.claude/plans/` in the project; run `/aldc:al-initialize` once if that folder does not exist.