1. Detect confirmation of a solved problem or manual invocation.
2. Gather context from conversation history (module, symptom, root cause, solution).
3. Check existing documentation for similar issues.
4. Generate a filename based on the symptom and module.
5. Validate YAML frontmatter against a predefined schema.
6. Create the documentation file with gathered context and validated YAML.
7. Cross-reference related issues and detect critical patterns.
8. Present a decision menu for further actions (e.g., add to required reading).