Agent Configuration Migration Task

An Agent Configuration Migration Task is a data migration task that converts tool-specific agent configurations to universal standards.

• AKA: Config Migration Task, Agent Setting Conversion, Configuration Standardization, Format Translation Task.
• Context:
  • It can typically parse source configuration formats like CLAUDE.md, .cursorrules, or .windsurfrules.
  • It can typically generate target configuration formats following AGENT.md standard or other universal formats.
  • It can typically preserve configuration semantics including instruction intent and behavioral directives.
  • It can typically validate migration results through schema compliance and functional equivalence tests.
  • It can typically handle format incompatibilitys through intelligent mapping and default values.
  • It can often support batch migrations processing multiple configuration files simultaneously.
  • It can often generate migration reports showing conversion success, warnings, and manual intervention needs.
  • It can often maintain version history enabling rollback if migration issues occur.
  • It can range from being a Simple Agent Configuration Migration Task to being a Complex Agent Configuration Migration Task, depending on its format difference.
  • It can range from being a One-Time Agent Configuration Migration Task to being a Continuous Agent Configuration Migration Task, depending on its execution pattern.
  • It can range from being a Lossless Agent Configuration Migration Task to being a Approximate Agent Configuration Migration Task, depending on its fidelity level.
  • It can range from being a Automated Agent Configuration Migration Task to being a Semi-Manual Agent Configuration Migration Task, depending on its human involvement.
  • ...
• Examples:
  • Legacy Format Agent Configuration Migration Tasks, such as:
    • CLAUDE.md to AGENT.md Migration Task, converting Claude-specific instructions.
    • Multiple Vendor Format Consolidation Task, merging various tool configurations.
  • Version Upgrade Agent Configuration Migration Tasks, such as:
    • AGENT.md v1 to v2 Migration Task, updating to new schema version.
    • Configuration Modernization Task, adding new capability declarations.
  • ...
• Counter-Examples:
  • Code Refactoring Task, which lacks configuration focus.
  • Database Migration Task, which lacks agent configuration aspect.
  • File Copy Operation, which lacks format transformation.
• See: CLI Agent Template Framework, AI Agent Configuration Standard, Cross-Tool Agent Compatibility System, Data Migration Process, Configuration Management Task, Format Conversion Algorithm, Tool Interoperability Task.

---