document-guideline

You can enforce documentation standards by applying guidelines that mandate folder README.md presence and source file markdown interfaces, validating them through a pre-commit linting process before implementation.

Yes, pre-commit hooks validate source code interfaces and test documentation coverage by enforcing linting checks against established documentation guidelines during the commit workflow.

Maintaining documentation-first workflows requires instructing AI agents to produce design docs and interface documentation before implementation, integrating with planning skills to drive consistency.

Yes, this guideline provides cross-skill guidance and standards used by plan-guideline and milestone skills to ensure documentation compliance across the AI planning and development ecosystem.

To ensure each source file has a corresponding markdown document, define guidelines requiring MD files that outline external public interfaces and internal helpers, validated by pre-commit lints.

Automated documentation linting validates structural compliance and file presence for READMEs and interfaces, but may not assess the semantic quality or accuracy of the written content itself.