documentation-writer

Generate structured technical documentation by providing project context and a request or PRD to produce ready-to-publish docs with explicit source-context tracking. It uses templates and linkable artifacts to ensure traceability across requirements and implementation guides.

Create Architecture Decision Records (ADRs) with cross-linking by feeding project context into the skill to automatically link decisions back to source artifacts. This maintains traceability and prevents misalignment between your architecture choices and implementation materials.

Keep requirements docs linked to source materials by using automated source-context tracking during docs-generation. Supply a PRD or project context, and the tool produces requirements documentation with linked references to maintain continuous traceability.

Yes, you can use templates to automate implementation docs generation by providing project context and a prompt. The skill applies predefined templates from its library to produce structured, ready-to-publish implementation documents linked to source artifacts.

Teams struggle with consistent technical docs across requirements and ADRs due to manual processes causing duplication and misalignment. Automating structured documentation generation with source-context tracking ensures cross-linked, traceable, and standardized artifacts.

To start generating structured technical docs, provide a project request or PRD alongside source materials. This input context feeds into templates to automatically produce requirements, implementation docs, and ADRs with precise source-artifact linking.