log-crlisted

# Log CR — Skill Instructions ## What this skill does Given a completed interview, produce one Obsidian `entretien` note with `categorie: "Compte-rendu"` in `CRM-JobSearch/Entretiens/`, filled with the CR debrief — Notes clés, Questions posées, and Renaud's own Fit read (see `docs/bant-cr-template.md` for the canonical template). The BANT (employer's read) is never written into the CR body: it is aggregated onto the matching `opportunite-js` instead (Step 7), so the company's BANT lives in one traceable, growing place instead of being re-typed and scattered across every CR. When the interview was recorded by Granola, the BANT, the questions and the next steps come from the transcript (Step 1bis) — Renaud is only asked for what the transcript cannot contain. Then: 1. Advance the matching `opportunite-js` to `statut: "🔄 Relance à faire"`, and `prochain_rdv` when a follow-up date is confirmed. 2. Aggregate this meeting's BANT onto the `opportunite-js`'s `## 🏢 BANT (agrégé)` section — dated, attributed, appended, never overwritten. 3. Close the prep hal task created by `interview-prep` (if found). 4. Create a post-interview relance hal task in the resolved jobsearch workspace. All vault I/O flows through `jobsearch-vault`. This skill NEVER writes to the vault filesystem directly. ## Step 0 — Domain check If the user mentions a Blue Green client, partner, or sales context, redirect immediately: > "Ce CR semble être un meeting Blue Green. Utilise `/crm log` dans Cowork blu