grimoire-audit

To audit a codebase for undocumented architecture decisions, use a structured workflow to map features, identify ADR gaps, and propose grimoire artifacts that capture critical knowledge for team onboarding.

A grimoire artifact in codebase documentation is a proposed record that captures undocumented features and architecture decisions discovered during an audit, guiding collaborative decision-making and knowledge onboarding.

You can find undocumented features and ADR gaps by applying a structured audit workflow that maps existing features, discovers undocumented behavior across the repository, and presents batch findings for collaborative review.

Yes, you can use a guided interview-based scope definition to begin a codebase audit, which helps gather discovery targets and draft artifact outlines in a single pass to ensure accurate onboarding documentation.

The best way to onboard teams using undocumented architecture decisions is to audit the codebase, map feature and decision gaps, and draft targeted grimoire artifacts that present batch findings for collaborative decision-making.

Yes, the codebase audit workflow supports batch findings by presenting manageable prompts that facilitate collaborative decision-making before drafting targeted grimoire artifacts and summaries after user confirmation.