user-guide

Writes the user guide of the system in docs/user_guide/ from the use case specifications: one chapter per primary actor (or per module in a project split by module), one task section per use case written in the second person from its main success scenario, alternative flows, preconditions, business rules, and postconditions, in the terms of docs/glossary.md and the language of the specifications. Covers the use cases that are Tested or Done; keeps the sections the team added by hand; never invents screens, buttons, or menu paths the specification does not name. Use when the user asks to "write the user guide", "create the user manual", "document the system for end users", "update the user guide for UC-004", "write help pages", "prepare training material", or mentions the Transition phase, end-user documentation, or docs/user_guide. It never edits a specification.