closing-bible-archiv
Wenn es um Closing Bible Archiv in Großkanzlei Corporate/M&A geht: ordnet Akteninhalt, Belege, Lücken und Nachforderungen; liefert einen Einreichungsplan mit Form-, Portal- und Nachweischeck.
npx skills add Klotzkette/claude-fuer-deutsches-recht --skill closing-bible-archiv --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
What it does
The skill focuses on organizing and delivering a Closing Bible and Archive after signing/closing in a Großkanzlei Corporate/M&A context. It instructs to sort by entity, roles, deadlines, and corresponding documents, and to produce a structured Closing Bible with a Inhaltsverzeichnis, Signaturkettenprotokoll, Registerstandsnachweisen, and a Deal-Archiv. It emphasizes output in a verifiable, document-backed format, including a Fakten-Norm-Beleg-Wertung-Nächster Schritt matrix and, if needed, a written text block.
How it works
- Determine the deal context: role, phase, transaction structure, target, and recipient of the output. If missing, ask a single clarifying question; proceed with a placeholder assumption when deadline pressure exists.
- Inventory sources: list all documents with date, version, source, data-room ID, and confidentiality level; tag uploads as [Mandant], registers as [Register], primary sources as [Primärquelle], and [Modellwissen - prüfen] for model-based knowledge.
- Separate interfaces: assign items to Corporate, Commercial, Tax, Regulatory, Finance, IP/IT, HR, Litigation, Real Estate, ESG, PMO; do not mix DD findings, contractual consequences, and closing tasks in one sentence.
- Set materiality threshold: apply limits from LOI, SPA, due diligence scope or playbook; if missing, propose a qualitative traffic-light (Dealbreaker, Price/Indemnity, Signing/Closing Condition, Disclosure-only, Housekeeping).
- Norm audit: check effectiveness, approvals, closing obstacles, liability, disclosure, deadlines, and evidentiary sources specific to the deal steps.
- Build source chain: every key assertion must have a source, document, citation, and uncertainty marker; if not retrievable, mark as [zu verifizieren].
- Risk matrix: for each point, include facts, legal question, norm, subsumption, risk level, economic impact, recommended action, owner, deadline, and follow-on skill.
- Draft or review gate: provide output if facts are sufficient; otherwise offer an information-request list or a Senior-Review-Memo with open decisions.
- Handoff: transfer findings into Data Room Q&A, SPA markup, CP-Tracker, Board Paper, or Mandantenmail; reference the downstream skills.
- Final check: ensure no unresolved case numbers, no blind cites from BeckRS, no external communications, and no confidential info outside need-to-know.
When to use it
Typical triggers include requests for a credible next step in a Closing Bible/archive, M&A mandates from Buy-side/Sell-side/Target perspectives, turning outputs into partner/mandant materials with risks and open points, or identifying missing documents, register extracts, or approvals.
What it can touch
- Tools: claude-code
- Data elements: deal_name, rolle, deal_phase, target, gegenpartei, jurisdiktionen, frist_oder_closing, materiality_threshold, owner, source_tag
Caveats
- Output must follow a structured, fully formed sentence format; placeholders like [Name der Mandantin] must be clearly marked.
- Norms and sources must be verifiable with allowed sources; avoid non-verifiable model knowledge.
- No automatic external communications or finalizing signing/closing decisions without partner review.
- The skill explicitly separates closing tasks from mandate-tac, and does not render final tax, competition, or sanctions conclusions without specialists.
# Closing Bible und Deal-Archiv erstellen: Anwendungsfall Mandant oder Counsel braucht nach Signing/Closing vollständige Dokumentensammlung aller executed Agreements, Signaturseiten und Registerbelege ## Arbeitsweg - Rolle, Ziel und gewünschtes Arbeitsprodukt klären: Wer handelt, welche Entscheidung steht an, welche Frist läuft und welcher Output wird gebraucht? - Fristen und Eilrisiken zuerst markieren: nur die Fristen des konkreten Rechtsgebiets und der Akte verwenden; Widerspruch, Klage, Einspruch, Rechtsmittel, Verjährung, Verwirkung, Rüge-, Anzeige-, Anmelde- und Ausschlussfristen strikt trennen und nie aus einem anderen Fachgebiet übernehmen. - Tragende Normen verifizieren: BRAO, BORA, FAO, BNotO, StBerG, WPO, PAO; AO Paragraf 38, 42, 90, 93, 153, 162, 164, 169-171, 173, 233a, 370-378, UStG, EStG, KStG, GewStG, GrEStG, ErbStG, FGO; UmwG; UmwStG; StaRUG — Fundstellen über gesetze-im-internet.de, dejure.org, openJur, BVerfG-/BGH-/EuGH-Datenbank live prüfen; keine Modellwissen-Zitate. - Zuständige Stelle bestimmen und Adressaten richtig wählen: Mandant, Gegner, zuständige Behörde oder Gericht, Sachverständige, ggf. EU-/internationale Stelle (siehe Skill-Detail). - Dokumente und
- Arbeitsweg
- Closing Bible und Archiv
- Fachlicher Kern — Gesellschaftsrecht und Corporate Law
- Fachkern: Closing Bible und Archiv
- Wann wird dieser Skill aufgerufen
- Voraussetzungen und Kontext laden
- Workflow
- Prüfraster im Gutachtenstil
- Output-Module
- Quellen und Zitierregel
- Hand-Off zu anderen Skills
- Was dieser Arbeitsgang nicht macht
- Berufsrechtliche Hinweise
- Bisheriger Skill-Kern, integriert und weiterzuverwenden
What does the closing-bible-archiv skill do?
Wenn es um Closing Bible Archiv in Großkanzlei Corporate/M&A geht: ordnet Akteninhalt, Belege, Lücken und Nachforderungen; liefert einen Einreichungsplan mit Form-, Portal- und Nachweischeck.
How do I install it?
Run `npx skills add Klotzkette/claude-fuer-deutsches-recht --skill closing-bible-archiv --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From Klotzkette/claude-fuer-deutsches-recht, a repository with 1,422 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.
