cv-update

Topics in the source

• CV update check
• 1. Read the CV
• 2. Decide
• 3. Tell Quinn
• 4. Update (only after Quinn says apply)

CV: cv/quinnneihauscv.md under the projects root named in /.claude/CLAUDE.md. No projects root there, or no CV at that path → say which and stop. Done when: you have read the whole CV. Compare what this session shipped (/send: the commits and PR) or learned (/teach: the lesson topic and learning records) against the CV. Update only if one of these is true: A technology, tool or skill is now used for real and is not on the CV yet (or moved from "Exploring" to working knowledge). A concrete, notable achievement: a measurable result, a feature or module now owned, a migration or architecture decision led. A fact on the CV is now wrong (role, dates, numbers). Routine bug fixes, small tickets, refactors and a single beginner lesson are not enough. When in doubt, don't update. Done when: you have a verdict: no update, or one proposed change. Never edit on your own. Every run ends with exactly one sentence to Quinn giving the verdict and the reason: No update → "No CV update needed: ." e.g. "No CV update needed: this was a routine bug fix in an area the CV already covers." Then stop. Update suggested → "CV update suggested: because ." Show the proposed line as a one-line diff, then ask wi

This is an excerpt. Refer to the complete source and its current requirements.