documentation

Generate structured markdown documentation with YAML frontmatter by using predefined templates that enforce complete metadata fields and strict separation of concerns. This ensures proper structure and adherence to project validation rules.

Maintain technical writing standards by enforcing metadata validation rules and predefined templates for database, API, and ADR docs. This prevents cross-contamination of concerns and ensures content organization compliance.

Yes, you can use templates to create multiple types of technical documentation including feature design, API, database schema, and ADR documents. Each type follows strict guidelines for structure and metadata.

Update existing feature design documents by invoking the documentation generation process with MCP tools for context and search. This leverages approved templates to maintain proper structure and YAML frontmatter compliance.

Yes, the documentation generation process enforces separation of concerns by guiding content placement into appropriate document types. This prevents cross-contamination between feature design, API, and database schema documentation.

Generated documentation fails validation rules when required YAML frontmatter fields are missing or incorrectly formatted. Ensure all metadata fields are present and content follows strict separation of concerns guidelines.