docs-writer

Automating technical writing for markdown and MDX files involves mapping code changes to doc impact, scaffolding new documentation, and improving existing files across repositories. This workflow provides a structured process for discovering, planning, writing, and verifying documentation updates.

Maintaining Next.js documentation standards when adding features requires profile-based guidance to scaffold API documentation and update guides. This approach ensures all changes adhere to specific Next.js documentation conventions across your project repositories.

Yes, this documentation workflow supports Angular projects through profile-based behavior. It adapts to Angular documentation conventions, allowing you to scaffold new documentation and update existing markdown files according to Angular project standards.

Mapping code changes to documentation impact across repositories requires an automated workflow that discovers, plans, writes, and verifies documentation updates. This process ensures high-quality technical documentation that remains consistent and accurate across diverse projects.

No, this documentation workflow does not require any specific dependencies or external environments. It operates self-contained to facilitate writing, reviewing, and updating technical documents across repositories without prerequisite setup.