docs-writer

You can generate documentation automatically by analyzing code diffs, implementation summaries, and project plans. This process creates decision logs, feature documents, and flow documents to capture project knowledge after code changes pass quality gates.

From implementation context, you can create decision logs detailing architectural choices, feature documents explaining new functionality, and process flow documents. These types ensure comprehensive project knowledge management based on code changes.

To automate decision log creation, provide the implementation context and code changes to a documentation generation tool. It analyzes the context to produce a decision document detailing architectural choices made during the feature implementation.

Yes, automated documentation generation works with existing project plans by analyzing them alongside code changes and implementation summaries. It uses this combined context to produce accurate feature descriptions and process flows.

The best way to maintain project knowledge without manual writing is using automated code generation tools. They analyze code changes and project plans to continuously generate and index essential documentation, ensuring knowledge is captured efficiently.

Yes, you need specific documentation tools to save and index generated feature documents. The generation process requires these tools to ensure the automated output is properly stored and searchable within your project's knowledge management system.