phx:document

You can automatically generate moduledoc and doc annotations for Elixir Phoenix modules by running this documentation generation skill after code implementation to create inline documentation for new modules and public functions.

The best way to document architectural decisions in an Elixir Phoenix project is to generate Architecture Decision Records (ADRs) that explain significant technical choices, which this skill creates automatically to improve code maintainability and knowledge sharing.

Yes, you can automatically update a README with new feature descriptions after implementing a Phoenix authentication module by running this skill to add user-facing usage instructions alongside generating the required module documentation.

You need to run documentation generation for Phoenix code after completing code review and implementing new features, ensuring inline module documentation, README sections, and ADRs remain up-to-date and integrated into your development workflow.

No, you do not need to install external dependencies to generate ADRs and README sections for Elixir code, as this documentation skill operates without any required dependencies to automate the creation of project documentation.