claude-md-generator

Generate a CLAUDE.md file by consuming a repository audit file, performing a guided interactive interview to fill information gaps, validating commands against package manifests, and writing the final concise documentation to the project root.

The best way to create concise documentation from a repo audit is to classify audit sections as inferred, partial, or unknown, then use a guided interview to ask focused questions and solicit tacit gotchas before synthesizing the results.

Yes, you need the repository audit output located at docs/repo-audit/current.md before generating project onboarding documentation, as the tool reads and classifies this file to minimize redundant developer questions.

Yes, you can validate package manifest commands during the generation process, ensuring the actionable output is accurate and preventing broken commands from being written to the CLAUDE.md file.

An interactive interview improves repository documentation generation by asking one focused question at a time with pre-populated options from the audit, capturing tacit developer knowledge and resolving unknown sections efficiently.