condense-agents-md

To reorganize a large AGENTS.md file, automate restructuring by analyzing section sizes and migrating non-essential information to dedicated per-directory files. This ensures the root documentation remains concise and focused.

The best way to migrate subsystem-specific documentation is to use an audit script that classifies content and suggests a migration plan. You can then automatically move large sections to specialized per-directory AGENTS.md files based on predefined rules.

Content migration for complex agent workflows works by auditing the existing documentation, classifying content based on relevance, and moving verbose explanations or design considerations into notes/ files. This replaces lengthy sections with concise references, improving scalability.

Yes, you need Python to automate AGENTS.md documentation refactoring. The Skill requires Python scripts located in the scripts/ directory to audit the existing file structure and generate the migration plan before applying changes.

Yes, you can review changes before applying them. The workflow involves running an audit script on your current AGENTS.md file to generate a suggested migration plan, allowing you to review and approve the restructuring before any content is moved.

You should condense agent documentation when your root AGENTS.md file grows large enough to hinder navigation and maintainability. Moving subsystem-specific information to dedicated files and notes ensures clarity and scalability for complex agent workflows.