Menü
After a redline cycle, propose an update to the playbook.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
Draft a board (or shareholder) consent for a routine action.
Apply a triggering event to the cap table and emit the diff.
Summarize a case (or set of cases) on a named question.
Add a newly observed clause to the clause library with its classification, source, and the playbook position it relates to.
Sequence handoffs when legal work spans multiple teams.
Draft offer letters and employment agreements from a hiring brief.
| slug | playbook-update |
| name | Playbook Update |
| description | After a redline cycle, propose an update to the playbook. |
| version | 0.1.0 |
| metadata | {"sources":[{"mode":"port-original","author":"ClaudeCoder","added_in":"0.1.0"}]} |
Port-original skill. Hand-authored for Legal & Contracts. Owned by
clause-library-curator.
A redline cycle (or a partner ask) suggests the firm's playbook needs adjustment — a position should move from preferred to acceptable, a new non-negotiable should be added, an outdated clause should be retired.
Required: the playbook entry to change (contract type + clause type), the proposed change, the supporting evidence (redline outcomes, partner reasoning, regulatory updates). Optional: per-client / per-matter scope if the change is not firm-wide.
A playbook-update memo:
# Playbook Update — <contract type> / <clause type> — <date>
**Proposed by:** clause-library-curator (port-original v0.1)
**Supporting evidence:** <links to redlines / matter notes / regulatory updates>
## Current position
<preferred / acceptable / non-negotiable wording>
## Proposed position
<new wording>
## Rationale
<2-3 sentences>
## Scope
<firm-wide | client-specific (which) | matter-specific (which)>
## Risks of not updating
<one line>
**Pending attorney sign-off before merge.**
The agent proposes; the attorney / partner approves. The playbook is the firm's source of truth and changes only on human sign-off.
Do not bundle multiple unrelated changes in one update — each playbook position gets its own memo so each can be approved or rejected separately.
Updates driven by a single matter are flagged as such; the agent does not over-generalize from N=1.
UPL line. This skill is designed against the unauthorized-practice-of-law line. Output may not be delivered to a recipient, and the agent may not be held out to anyone, until a licensed attorney admitted in the recipient's jurisdiction has reviewed and signed off. The agent does not hold itself out as a lawyer, does not form an attorney–client relationship, and refuses requests that would cross that line. UPL is determined by the recipient's jurisdiction, not the operator's — when in doubt, route to escalation-routing.
Write the memo to playbook-updates/<date>-<slug>.md. Post a comment on the source work item naming the memo and the attorney who needs to sign off. Do not modify the live playbook.