ln-110-project-docs-coordinator

Documentation coordination gathers project context once, auto-detects your codebase structure (backend, frontend, database, Docker), then delegates specialized writing tasks to five workers and aggregates results into unified documentation artifacts.

Yes. The coordinator detects project type flags across package.json, Docker, docker-compose, and repo structure, then dispatches to specialized workers for root docs, core architecture, backend APIs, frontend guides, and DevOps setup—merging legacy content if provided.

Project-type detection scans your repository structure and configuration files to identify hasBackend, hasDatabase, hasFrontend, and hasDocker flags, routing context to the appropriate specialized documentation workers for accurate, component-specific output.

Use a coordinator that gathers context once from your entire project, detects component types automatically, distributes work to specialized writers, then aggregates all outputs—eliminating redundant context gathering and ensuring consistency across documentation artifacts.

Yes. The coordinator supports explicit context passing to workers and merges legacy documentation when provided, combining your existing docs with newly generated specialized content from backend, frontend, and DevOps workers.

No. One-time context gathering creates a Context Store from your project structure, which the coordinator automatically passes to all five specialized workers, eliminating manual per-worker configuration and ensuring consistent project understanding.