Contract Intelligence Workflow Reviewer Carl Ditzler
Contract intelligence and contract operations workflow skill for Claude and Codex.
Install
npx skills add lawve-ai/awesome-legal-skills --skill contract-intelligence-workflow-reviewer-carl-ditzler -g -a claude-code -y- Repository
- lawve-ai/awesome-legal-skills919
- Category
- Testing
- Updated
- 16d ago
- License
- See repository
- Context cost
- Mediumabout 3,000 tokens
- Runs scripts
- Yes, review before use
What it does
Contract intelligence and contract operations workflow skill for Claude and Codex. Guides the full contract lifecycle review process from intake and playbook normalization through clause review, deviation scoring, negotiation planning, approval routing, QA, and action recommendations. Reviews legal, business, operational, compliance, privacy, security, technology, and AI-related risks across contracts and legal documents. Supports NDAs, SaaS agreements, DPAs, procurement contracts, commercial agreements, contract comparisons, redlines, approval packages, clause research, and drafting. Warning-Comprehensive reviews can consume significant Claude/OpenAI tokens, especially for large agreements, playbooks, exhibits, schedules, and multi-document reviews.
Contract Intelligence & Workflow Reviewer
Use this skill when the user needs a full contract workflow: review, redline package, negotiation plan, fallback positions, approval routing, clause research, drafting, summarization, or a machine-readable next action.
This skill is designed for Codex and Claude. It is intentionally strict. The legal workflow mirrors a legal team process:
- Intake
- Playbook
- Review
- Negotiation
- Approvals
- QA
Before that legal workflow starts, run setup and persistence checks if the workspace has not been configured yet.
For operational work, also track workflow state:
- Setup
- Intake
- Triage
- Review
- Redline
- Negotiation
- Internal approvals
- Signature-ready
- Closed
Do not skip a stage. Do not jump to the answer because the user asks for speed. If the user wants a quick turnaround, compress the explanation, not the workflow.
Load Order
Read these files in order and apply them as hard requirements:
- references/setup-and-persistence.md
- references/filesystem-workflow.md
- references/document-structure-and-attention.md
- references/security-and-privacy.md
- references/mcp-integrations.md
- references/playbook-ingestion.md
- references/intake-form.md
- references/playbook-schema.md
- references/playbook-deviation-scoring.md
- references/priority-matrix.md
- references/execution-playbook.md
- references/failure-modes.md
- references/test-plan.md
- references/benchmarking.md
