AgentSkillsCN

orchestrator-self-auditor

当新增、移除或修改技能时，及时审计并更新开发控制器逻辑，以维护整体流程的顺畅与完整。

SKILL.md
--- frontmatter
name: orchestrator-self-auditor
description: Audits and updates the development controller logic when skills are added, removed, or modified to maintain flow integrity.
triggers: [skill-update-detected, monthly-maintenance, orchestrator-drift]
outputs: [orchestrator-diff, audit-summary]

Orchestrator Self Auditor

Purpose

Maintains the "brain" of the system by ensuring the orchestrated-development-controller is always in sync with the available skills. It prevents the system from using "ghost skills" or missing out on new capabilities.

When to use this skill

  • •After a new skill is added via skill-scaffold-generator
  • •When a skill's description or triggers are modified
  • •Periodically as part of lifecycle-health-monitor to optimize flow ordering

Audit Steps

  1. •Scan Skill Registry: Inventory all files in .agent/skills/ and global_skills/.
  2. •Cross-Reference Descriptions: Compare the orchestrator's decision trees against current skill missions.
  3. •Detect Overlaps: Identify if two skills are now covering the same task.
  4. •Detect Gaps: Identify if a spec-defined task has no supporting skill.
  5. •Optimize Ordering: Ensure skills are chained in the most efficient order (e.g., Linter before Planner).

Decision Tree

mermaid
flowchart TD
    A[Start Audit] --> B{Skills Changed?}
    B -->|Yes| C[Update Orchestrator Map]
    B -->|No| D{Orchestrator Errors?}
    D -->|Yes| E[Repair Broken References]
    D -->|No| F{Inefficient Flow?}
    F -->|Yes| G[Propose Sequence Update]
    F -->|No| H[Audit Complete - No Change]
    C --> I[Submit PR for orchestrated-development-controller]
    E --> I
    G --> I

Review Checklist

  1. •Completeness: Are all 36+ skills referenced where appropriate?
  2. •Correctness: Do the labels in the Mermaid diagrams match actual skill names?
  3. •Efficiency: Has the path to "Done" been shortened without losing safety?
  4. •Transparency: Are orchestration changes documented in the change log?

How to provide feedback

  • •Be specific: "The auditor missed that 'spec-linter' is now redundant with the new 'vision-normalizer' check."
  • •Explain why: "Running redundant checks slows down the development cycle without adding safety."
  • •Suggest alternatives: "Merge the structure-check from linter into the normalizer and deprecate the linter clause."

Never silently change orchestration logic.