docs-architect

Standardize repository documentation by generating a consistent suite of README.md files and structured /docs folders. This process normalizes cross-links and creates a documentation index map, ensuring every microservice meets a high standard of clarity and usability.

A professional technical documentation suite should include sections for "The Hook & Vision", "The Tech Stack", "The Quickstart", "Information Flows", and "Use Cases". This structure ensures comprehensive coverage of project onboarding and architecture.

Normalize broken cross-links in markdown documentation by executing a comprehensive documentation overhaul. This standardizes all internal links across the repository suite and generates a unified documentation index map for reliable navigation.

Yes, you can systematically overhaul documentation for a large microservices architecture. It brings sparse, outdated service documentation up to a consistent, high-quality standard by generating uniform README.md files and structured /docs folders across all repositories.

The best way to generate a structured /docs folder is to perform a comprehensive documentation overhaul on the attached repository. This automatically creates the /docs structure with specific sections like "The Quickstart" and "Information Flows" while normalizing cross-links.

No specific dependencies are required to perform a repository documentation overhaul. The process operates directly on the attached repository to generate the Gold Standard documentation suite and normalize cross-links without external tools.