docs-writer

To update project documentation, review existing markdown files and rewrite them to align with current implementation details, naming conventions, and workflow rules. This ensures documentation accurately reflects the active codebase behavior and repository-specific standards.

Maintaining consistent technical writing style across README files requires applying a standardized style guide to review and edit content. This process checks readability, formatting, and terminology consistency to ensure all markdown-based knowledge assets match project conventions.

Checking markdown documentation for formatting and link consistency involves reviewing the target files for structural cleanup and link validation. This review process identifies formatting errors, broken links, and incomplete sections across the Docs directory.

Yes, applying a style guide standardizes markdown conventions for a Docs directory by enforcing repository-specific formatting rules. This aligns all design notes, setup instructions, and release notes with the project's structural and terminology requirements.

Rewriting technical documentation is needed when a feature change alters setup instructions, design notes, or release notes. Updating the markdown pages ensures the documentation reflects the modified implementation details and maintains accurate workflow descriptions.

Technical writing for markdown requires strict alignment with formatting rules to maintain documentation completeness and structural consistency. Adhering to these repository-specific conventions ensures the knowledge assets remain accurate, readable, and properly linked.