n/a

Project documentation coordination assembles context across a multi-phase pipeline, detects project type (backend, frontend, database, Docker), and delegates work to specialized workers that produce structured outputs: root docs, core docs, architecture specs, API specs, and runbooks as a consolidated status summary.

Documentation automation detects your project type during single-context gathering, routes tasks to type-specific workers, and aggregates results into structured documentation outputs covering architecture, APIs, and operational runbooks in one workflow.

A multi-phase pipeline performs context assembly, project-type detection, work delegation to specialized processors, and results aggregation to produce root documentation, core documentation, architecture diagrams, API specifications, and runbooks.

Documentation merging combines existing legacy content with newly gathered project context during the single-context assembly phase, enabling structured output generation that preserves historical documentation while incorporating current project structure.

A documentation pipeline outputs root docs, core documentation, architecture specifications, API specifications, and runbooks, returned as a concise status summary after context gathering and project-type detection.