Document Code

You point it at a file, folder, function, or API, and it validates the target, searches existing knowledge first, analyzes dependencies while avoiding loops, then writes a markdown doc following a fixed template in docs/ai/implementation/. It optionally generates a standalone HTML artifact with a card based layout if you ask for one, though the markdown is the source of truth. The hard rule is no documentation gets written until validation and analysis finish. It's opinionated about stopping you from skipping the discovery phase, which is probably the right trade off if you've ever documented code in a hurry and regretted it later.