agent-md-refactor

To refactor monolithic agent instructions using progressive disclosure, move detailed instructions into linked, categorized sub-files. This keeps the root file concise while categorizing details into separate Markdown files to improve clarity and maintainability.

Organizing a massive CLAUDE.md file involves splitting it into a clean root file with links to separate files like code-style.md, testing.md, and git-workflow.md. This restructuring categorizes details to make configurations easier to manage.

Contradiction resolution in agent configuration refactoring identifies and flags conflicting instructions for user review. This ensures that contradictory content is caught and resolved before the file is restructured into linked Markdown files.

Yes, you can clean up AGENTS.md files for better maintainability by identifying essential root-level instructions and moving remaining details into a structured hierarchy of linked Markdown files, keeping the root configuration focused.

A limitation of progressive disclosure for agent instructions is that it requires manual review when redundant or contradictory content is flagged. Users must evaluate these flagged conflicts before the restructuring process can be safely completed.

Your agent instruction file needs to be split into linked Markdown files because overly long configurations reduce clarity. Progressive disclosure principles move details out of the main file to improve overall agent configuration management and understanding.