Capture Learning

Choose the branch before selecting a model. Routine capture work runs in the current role. Before dispatching an independent reviewer, use shared/references/model-preview.md and bind its one approved route snapshot.

Create one source-grounded solution document that a later engineer can find and use. The next consumer is someone facing the same problem. Done means the document is written, validated, and does not state an unverified claim as fact.

Scope

Capture one learning per run. It must describe a solved, verified, and non-obvious problem. If the evidence does not meet that bar, do not write a weak document. In mode:headless, return Documentation skipped with the reason. In an interactive run, ask only when the solved problem itself is unclear.

This skill writes only the solution document. When an existing CONCEPTS.md has a qualifying missing term, update that entry too. Do not create a glossary, edit project instructions, search unrelated memory, or turn this run into a documentation audit.

Workflow