docs

You can sync README and docs with your current codebase state by requesting a full documentation sync that updates README.md and relevant docs/*.md files. The process reads concrete implementation artifacts like index.ts, services.ts, and commands to ensure docs reflect the actual public surface.

The best way to update feature documentation safely is through targeted single-file edits that align docs with the real implementation. This feature-specific doc expansion checks the feature's index.ts, services.ts, and commands/ directory to accurately document the actual public surface without touching unrelated files.

To verify CLI flags and command behavior before writing documentation, the process requires running commands with the --help flag and performing grounded reads of project files like AGENTS.md and CLAUDE.md. This verification-driven approach prevents documenting unverified claims about CLI behavior.

Yes, you can refresh a single explicitly named documentation file such as AGENTS.md or CLAUDE.md without triggering a full repository sync. The targeted single-file edit capability refreshes only the specified file and leaves unrelated documentation untouched, ensuring surgical local edits.

Updating repository documentation does not automatically open a pull request or commit changes directly. The process applies safe working-tree changes by editing files locally and leaving them in the working tree for you to review and commit manually, ensuring user control over version control.

A key limitation during documentation sync is that surgical local edits must not touch protected Maestro or Claude memory and missions. The process strictly updates README and docs based on the current codebase while preserving these protected files from any modifications.