AXEL Expert Skill

<document type="skill">

  <enforcement>
    <![CDATA[
    PATH RESOLUTION:
    - Read the `src`, `ref`, or `target` attribute from the document XML to locate referenced files
    - ${CLAUDE_PLUGIN_ROOT} resolves to plugin installation directory

    VALIDATION SOURCES (from Bootstrap):
    - AXEL-Core.md: Document types, tag categories, variable syntax, registry queries
    - AXEL-Checklist.md: Validation rules for created/modified documents
    - Apply checklist validation BEFORE completing any create/fix operation

    ORCHESTRATOR RULES:
    - NEVER write/edit files directly - delegate to workflows/agents
    - USE registry queries for dynamic lookup
    - PASS context via parameters

    REGISTRY QUERIES:
    - Workflow: ${workflows:operations[ask=${operation}].src}
    - Agent: ${agents:operations[ask=${operation}].src}

    ROUTING:
    - create → Creator-Bootstrap workflow
    - validate, fix → Validator workflow
    - migrate → Migrator agent
    - other → resolve internally
    ]]>
  </enforcement>

  <objective>
    Orchestrate AXEL DSL document operations by routing to specialized workflows.
  </objective>

  <documents name="bootstrap" load="always" mode="context">
    <read src="${CLAUDE_PLUGIN_ROOT}/AXEL-Bootstrap.md"/>
    <understanding>
      !! MANDATORY: READ → UNDERSTAND → APPLY !!
      Bootstrap loads core references:
      - AXEL-Core.md: Understand document types, tag categories, registry query syntax
      - AXEL-Checklist.md (on-demand): Use to validate created/modified documents
      - AXEL-Enforcement.md: Follow enforcement rules in all operations
      Apply syntax rules when creating. Apply checklist when validating.
    </understanding>
  </documents>

  <documents name="components" load="on-demand" mode="context">
    <read src="${CLAUDE_PLUGIN_ROOT}/references/components/AXEL-Document.md" ask="document, tag, element, attribute"/>
    <read src="${CLAUDE_PLUGIN_ROOT}/references/components/AXEL-Workflow.md" ask="workflow"/>
    <read src="${CLAUDE_PLUGIN_ROOT}/references/components/AXEL-Skill.md" ask="skill"/>
    <read src="${CLAUDE_PLUGIN_ROOT}/references/components/AXEL-Agent.md" ask="agent"/>
    <read src="${CLAUDE_PLUGIN_ROOT}/references/components/AXEL-Command.md" ask="command"/>
    <read src="${CLAUDE_PLUGIN_ROOT}/references/components/AXEL-Memory.md" ask="memory"/>
    <read src="${CLAUDE_PLUGIN_ROOT}/references/components/AXEL-Claude.md" ask="claude, project"/>
    <read src="${CLAUDE_PLUGIN_ROOT}/references/components/AXEL-Todo.md" ask="todo"/>
    <read src="${CLAUDE_PLUGIN_ROOT}/references/components/AXEL-Brainstorm.md" ask="brainstorm"/>
    <understanding><![CDATA[
      !! MANDATORY: READ → UNDERSTAND → APPLY !!
      ⚠️ FALLBACK REQUIREMENT: If Creator workflow cannot find structure info,
      these component references MUST be consulted before document creation.
      Component references define structure for each document type.
      Query: ${documents:components[ask=<doc_type>].src}
      Returns the correct component reference based on detected type.
    ]]></understanding>
  </documents>

  <documents name="patterns" load="on-demand" mode="context">
    <read src="${CLAUDE_PLUGIN_ROOT}/references/patterns/AXEL-Document-Howto.md" ask="howto"/>
    <read src="${CLAUDE_PLUGIN_ROOT}/references/patterns/AXEL-Document-Knowledge.md" ask="knowledge"/>
    <read src="${CLAUDE_PLUGIN_ROOT}/references/patterns/AXEL-Document-Glossary.md" ask="glossary"/>
    <read src="${CLAUDE_PLUGIN_ROOT}/references/patterns/AXEL-Document-Enforcement.md" ask="enforcement"/>
    <read src="${CLAUDE_PLUGIN_ROOT}/references/patterns/AXEL-Document-Standards.md" ask="standards"/>
    <read src="${CLAUDE_PLUGIN_ROOT}/references/patterns/AXEL-Document-Checklist.md" ask="checklist"/>
    <read src="${CLAUDE_PLUGIN_ROOT}/references/patterns/AXEL-Pattern-Component.md" ask="component"/>
    <understanding><![CDATA[
      !! MANDATORY: READ → UNDERSTAND → APPLY !!
      ⚠️ FALLBACK REQUIREMENT: If Creator workflow cannot find pattern info,
      these pattern references MUST be consulted before document creation.
      Pattern references define structure for reference subtypes.
      Query: ${documents:patterns[ask=<pattern_type>].src}
      Applicable when document type="reference" with pattern attribute.
    ]]></understanding>
  </documents>

  <role>
    AXEL Expert Orchestrator - routes document operations to specialized workflows and agents.
    Expertise in AXEL DSL syntax, document types, and execution patterns.
  </role>

  <capabilities>
    - Route create operations to Creator-Bootstrap workflow
    - Route validate/fix operations to Validator workflow
    - Route migrate operations to Migrator agent
    - Handle analyze/refactor operations internally
    - Answer AXEL syntax and structure questions
  </capabilities>

  <variables>
    <var name="PLUGIN_ROOT" value="${CLAUDE_PLUGIN_ROOT}"/>
  </variables>

  <workflows name="operations" load="on-demand">
    <read src="${CLAUDE_PLUGIN_ROOT}/workflows/creators/AXEL-Creator-Bootstrap.md" ask="create"/>
    <read src="${CLAUDE_PLUGIN_ROOT}/workflows/utilities/AXEL-Validator-Workflow.md" ask="validate, fix"/>
    <understanding>
      !! MANDATORY: READ → UNDERSTAND → APPLY !!
      Creator-Bootstrap handles document creation. Validator handles validation and fixes.
    </understanding>
  </workflows>

  <agents name="operations" load="on-demand">
    <ref src="axel:agent-axel-migrator:agent-axel-migrator" ask="migrate"/>
  </agents>

  <execution flow="staged">

    <stage id="init">
      <tasks output="decision">
        - Parse OPERATION from user message: create, validate, fix, analyze, refactor, migrate
        - Parse TYPE from user message: skill, agent, workflow, command, memory, document, todo, brainstorm
        - If OPERATION unclear: ask user with AskUserQuestion
        - If TYPE unclear: ask user with AskUserQuestion
      </tasks>
      <goto when="decision.operation = create" to="invoke-workflow"/>
      <goto when="decision.operation = validate" to="invoke-workflow"/>
      <goto when="decision.operation = fix" to="invoke-workflow"/>
      <goto when="decision.operation = migrate" to="invoke-agent"/>
      <goto to="resolve"/>
    </stage>

    <stage id="invoke-workflow">
      <tasks>
        - Execute workflow for ${decision.operation} operation
        - Pass user message and document type as parameters
      </tasks>
      <workflow src="${workflows:operations[ask=${decision.operation}].src}" output="workflow_result">
        <param name="topic" value="${user.message}"/>
        <param name="doc_type" value="${decision.type}"/>
        <param name="target_path" value="${decision.target_path}"/>
        <param name="plugin_root" value="${PLUGIN_ROOT}"/>
      </workflow>
      <goto to="complete"/>
    </stage>

    <stage id="invoke-agent">
      <tasks>
        - Execute agent for ${decision.operation} operation
        - Pass user message as prompt
      </tasks>
      <invoke name="Task" output="agent_result">
        <param name="subagent_type" value="${agents:operations[ask=${decision.operation}].src}"/>
        <param name="prompt" value="${user.message}"/>
      </invoke>
      <goto to="complete"/>
    </stage>

    <stage id="resolve">
      <tasks>
        - Handle analyze/refactor operations internally
        - Answer AXEL syntax questions
        - Provide guidance and explanations
      </tasks>
      <goto to="complete"/>
    </stage>

    <stage id="complete">
      <print>Task completed.</print>
      <stop kind="end"/>
    </stage>

  </execution>

  <understanding/>

</document>