Loading...
Loading...
Compare original and translation side by side
| Question | Why It Matters |
|---|---|
| Document type? | Contract, proposal, SOW, NDA, MSA |
| Jurisdiction? | US-Delaware, EU, UK, DACH |
| Engagement model? | Fixed-price, hourly, retainer, revenue-share |
| Parties? | Legal names, roles, registered addresses |
| Scope summary? | 1-3 sentences describing the work |
| Total value or rate? | Drives payment terms and liability caps |
| Timeline? | Start date, end date or duration, milestones |
| Special requirements? | IP assignment, white-label, subcontractors, non-compete |
| Personal data involved? | Triggers GDPR DPA requirement in EU/DACH |
| 问题 | 重要性说明 |
|---|---|
| 文档类型? | 合同、提案、SOW、NDA、MSA |
| 司法管辖区? | 美国-特拉华州、欧盟、英国、DACH |
| 合作模式? | 固定价格、按小时计费、保留服务、收益分成 |
| 参与方? | 法律名称、角色、注册地址 |
| 范围摘要? | 1-3句话描述工作内容 |
| 总金额或费率? | 影响付款条款和责任上限 |
| 时间线? | 开始日期、结束日期或时长、里程碑 |
| 特殊要求? | 知识产权转让、白标、分包商、竞业禁止 |
| 是否涉及个人数据? | 触发欧盟/DACH地区的GDPR数据处理附录要求 |
| Document Type | Engagement Model | Template |
|---|---|---|
| Dev contract | Fixed-price | Template A: Fixed-Price Development |
| Dev contract | Hourly/Retainer | Template B: Consulting Retainer |
| Partnership | Revenue-share | Template C: SaaS Partnership |
| NDA | Mutual | Template NDA-M |
| NDA | One-way (discloser/recipient) | Template NDA-OW |
| SOW | Any | Template SOW (attaches to MSA or standalone) |
| Proposal | Any | Template P: Project Proposal |
| 文档类型 | 合作模式 | 模板 |
|---|---|---|
| 开发合同 | 固定价格 | 模板A:固定价格开发合同 |
| 开发合同 | 按小时/保留服务 | 模板B:咨询服务保留协议 |
| 合作协议 | 收益分成 | 模板C:SaaS合作协议 |
| 保密协议 | 双向 | 模板NDA-M |
| 保密协议 | 单向(披露方/接收方) | 模板NDA-OW |
| 工作说明书 | 任意 | 模板SOW(可附加于MSA或独立使用) |
| 项目提案 | 任意 | 模板P:项目提案 |
[BRACKETED][REQUIRED - description][BRACKETED][REQUIRED - description][BRACKETED][BRACKETED]| Model | Standard Terms | Risk Notes |
|---|---|---|
| Fixed-price | 50% upfront, 25% at beta, 25% at acceptance | Best for defined scope |
| Hourly | Net-30, monthly invoicing | Requires time tracking |
| Retainer | Monthly prepaid, 1st of month | Include overflow rate |
| Milestone | Per-milestone invoicing | Define milestones precisely |
| Revenue-share | Net-30 after month close, minimum threshold | Requires audit rights |
| 模式 | 标准条款 | 风险提示 |
|---|---|---|
| 固定价格 | 50%预付款,25%在Beta阶段支付,25%在验收后支付 | 最适合范围明确的项目 |
| 按小时计费 | 月结,账期30天 | 需要时间跟踪 |
| 保留服务 | 每月预付,每月1日支付 | 包含超额费率 |
| 里程碑式 | 按里程碑开票 | 需精确定义里程碑 |
| 收益分成 | 月结后30天支付,设有最低门槛 | 需要审计权限 |
| Jurisdiction | Default IP Ownership | Key Requirement |
|---|---|---|
| US (Delaware) | Work-for-hire doctrine | Must be in writing, 9 qualifying categories |
| EU | Author retains moral rights | Separate written assignment needed |
| UK | Employer owns (if employee) | Contractor: explicit assignment required |
| DACH (Germany) | Author retains Urheberrecht permanently | Must transfer Nutzungsrechte (usage rights) explicitly |
| 司法管辖区 | 默认知识产权归属 | 核心要求 |
|---|---|---|
| 美国(特拉华州) | 职务作品原则 | 必须以书面形式呈现,共9类符合条件的作品 |
| 欧盟 | 作者保留精神权利 | 需要单独的书面转让协议 |
| 英国 | 雇主拥有(若为雇员) | 承包商:需明确的转让条款 |
| DACH(德国) | 作者永久保留著作权(Urheberrecht) | 必须明确转让使用权限(Nutzungsrechte) |
| Risk Level | Cap | When to Use |
|---|---|---|
| Standard | 1x total fees paid | Most projects |
| High-risk | 3x total fees paid | Critical infrastructure, regulated industries |
| Uncapped (mutual) | No cap, mutual indemnification | Enterprise partnerships |
| 风险等级 | 上限 | 使用场景 |
|---|---|---|
| 标准 | 已支付总费用的1倍 | 大多数项目 |
| 高风险 | 已支付总费用的3倍 | 关键基础设施、受监管行业 |
| 无上限(双向) | 无上限,双向赔偿 | 企业级合作 |
| Type | Notice Period | Financial Treatment |
|---|---|---|
| For cause | 14-day cure period | Pay for work completed |
| For convenience (client) | 30 days written notice | Pay for work completed + 10-20% of remaining value |
| For convenience (either) | 30-60 days | Pay for work completed |
| Immediate (material breach uncured) | 7 days post-notice | Pro-rata payment |
| 类型 | 通知期限 | 财务处理 |
|---|---|---|
| 因故终止 | 14天整改期 | 支付已完成工作的费用 |
| 客户方便终止 | 30天书面通知 | 支付已完成工作的费用 + 剩余金额的10-20% |
| 双方方便终止 | 30-60天 | 支付已完成工作的费用 |
| 立即终止(未纠正的重大违约) | 通知后7天 | 按比例支付费用 |
| Jurisdiction | Recommended Forum | Rules |
|---|---|---|
| US | Binding arbitration | AAA Commercial Rules, Delaware venue |
| EU | ICC arbitration or local courts | ICC Rules, venue in capital of governing law |
| UK | LCIA arbitration, London | LCIA Rules, English law |
| DACH | DIS arbitration or Landgericht | DIS Rules, German law |
| 司法管辖区 | 推荐论坛 | 规则 |
|---|---|---|
| 美国 | 有约束力的仲裁 | AAA商业规则,特拉华州地点 |
| 欧盟 | ICC仲裁或当地法院 | ICC规则,管辖法律所属国首都地点 |
| 英国 | LCIA仲裁,伦敦 | LCIA规则,英国法律 |
| DACH | DIS仲裁或州法院 | DIS规则,德国法律 |
undefinedundefined| Sub-Processor | Location | Purpose |
|---|---|---|
| [AWS/GCP/Azure] | [Region] | Cloud infrastructure |
| [Stripe] | [US/EU] | Payment processing |
| 分包处理方 | 地点 | 用途 |
|---|---|---|
| [AWS/GCP/Azure] | [Region] | 云基础设施 |
| [Stripe] | [US/EU] | 支付处理 |
---
---undefinedundefined| Phase | Deliverables | Duration | Dates |
|---|---|---|---|
| Discovery | Requirements document, architecture plan | 1 week | [Dates] |
| Development | Core features, API integration | 4 weeks | [Dates] |
| Testing | QA, UAT, bug fixes | 1 week | [Dates] |
| Launch | Deployment, monitoring, handoff | 1 week | [Dates] |
| 阶段 | 交付物 | 时长 | 日期 |
|---|---|---|---|
| 发现阶段 | 需求文档、架构规划 | 1周 | [Dates] |
| 开发阶段 | 核心功能、API集成 | 4周 | [Dates] |
| 测试阶段 | QA、用户验收测试、Bug修复 | 1周 | [Dates] |
| 上线阶段 | 部署、监控、交接 | 1周 | [Dates] |
| Item | Cost |
|---|---|
| Discovery & Planning | [Amount] |
| Development | [Amount] |
| Testing & QA | [Amount] |
| Project Management | [Amount] |
| Total | [Amount] |
| 项目 | 费用 |
|---|---|
| 发现与规划 | [Amount] |
| 开发 | [Amount] |
| 测试与QA | [Amount] |
| 项目管理 | [Amount] |
| 总计 | [Amount] |
---
---undefinedundefined
---
---| Pitfall | Consequence | Prevention |
|---|---|---|
| Missing IP assignment language | Unclear ownership, disputes | Always include explicit IP clause per jurisdiction |
| Vague acceptance criteria | Endless revision cycles | Define "accepted" = written sign-off within X days |
| No change order process | Scope creep on fixed-price | Include change order clause with pricing mechanism |
| Jurisdiction mismatch | Unenforceable clauses | Match governing law to where parties operate |
| Missing liability cap | Unlimited exposure | Always cap liability at 1-3x contract value |
| Oral amendments | Unenforceable modifications | Require written amendments signed by both parties |
| No DPA for EU data | GDPR violation, up to 4% global revenue fine | Always include DPA when processing EU personal data |
| Missing force majeure | No protection against unforeseeable events | Include for engagements over 3 months |
| 陷阱 | 后果 | 预防措施 |
|---|---|---|
| 缺少知识产权转让条款 | 所有权不明确,引发纠纷 | 始终包含符合司法管辖区要求的明确知识产权条款 |
| 验收标准模糊 | 无限期修订循环 | 定义“验收”= X天内书面签字确认 |
| 无变更订单流程 | 固定价格项目出现范围蔓延 | 包含带有定价机制的变更订单条款 |
| 司法管辖区不匹配 | 条款无法强制执行 | 管辖法律与参与方运营地点匹配 |
| 缺少责任上限 | 无限风险敞口 | 始终将责任上限设为合同金额的1-3倍 |
| 口头修改 | 修改内容无法强制执行 | 要求双方签署书面修改协议 |
| 欧盟数据处理未包含DPA | 违反GDPR,最高可处全球年收入4%的罚款 | 处理欧盟个人数据时始终包含DPA |
| 缺少不可抗力条款 | 无法抵御不可预见事件 | 对于时长超过3个月的合作需包含该条款 |
| Skill | Use When |
|---|---|
| ceo-advisor | Strategic decisions about partnerships and business models |
| cfo-advisor | Financial terms, pricing strategy, revenue recognition |
| launch-strategy | Contract timing around product launches |
| 技能 | 使用场景 |
|---|---|
| ceo-advisor | 关于合作和商业模式的战略决策 |
| cfo-advisor | 财务条款、定价策略、收入确认 |
| launch-strategy | 产品发布前后的合同时间安排 |
python scripts/contract_clause_checker.py contract.json --jurisdiction us-delaware
python scripts/contract_clause_checker.py contract.json --jurisdiction eu --json| Flag | Required | Description |
|---|---|---|
| Yes | JSON file with contract clauses and metadata |
| No | Jurisdiction to check against: us-delaware, eu, uk, dach (default: us-delaware) |
| No | Contract type: fixed-price, hourly, retainer, nda, msa (default: fixed-price) |
| No | Output results as JSON |
python scripts/contract_clause_checker.py contract.json --jurisdiction us-delaware
python scripts/contract_clause_checker.py contract.json --jurisdiction eu --json| 参数 | 是否必填 | 描述 |
|---|---|---|
| 是 | 包含合同条款和元数据的JSON文件 |
| 否 | 要检查的司法管辖区:us-delaware, eu, uk, dach(默认:us-delaware) |
| 否 | 合同类型:fixed-price, hourly, retainer, nda, msa(默认:fixed-price) |
| 否 | 以JSON格式输出结果 |
python scripts/proposal_cost_estimator.py --hourly-rate 150 --hours 200 --phases 4
python scripts/proposal_cost_estimator.py --hourly-rate 150 --hours 200 --phases 4 --json| Flag | Required | Description |
|---|---|---|
| Yes | Hourly rate in dollars |
| Yes | Estimated total hours |
| No | Number of project phases (default: 3) |
| No | Desired profit margin percentage (default: 20) |
| No | Currency code (default: USD) |
| No | Output results as JSON |
python scripts/proposal_cost_estimator.py --hourly-rate 150 --hours 200 --phases 4
python scripts/proposal_cost_estimator.py --hourly-rate 150 --hours 200 --phases 4 --json| 参数 | 是否必填 | 描述 |
|---|---|---|
| 是 | 小时费率(美元) |
| 是 | 预计总工时 |
| 否 | 项目阶段数量(默认:3) |
| 否 | 期望利润率(默认:20) |
| 否 | 货币代码(默认:USD) |
| 否 | 以JSON格式输出结果 |
python scripts/contract_comparison_analyzer.py contract_v1.json contract_v2.json
python scripts/contract_comparison_analyzer.py contract_v1.json contract_v2.json --json| Flag | Required | Description |
|---|---|---|
| Yes | JSON file with first contract version |
| Yes | JSON file with second contract version |
| No | Output results as JSON |
python scripts/contract_comparison_analyzer.py contract_v1.json contract_v2.json
python scripts/contract_comparison_analyzer.py contract_v1.json contract_v2.json --json| 参数 | 是否必填 | 描述 |
|---|---|---|
| 是 | 第一个合同版本的JSON文件 |
| 是 | 第二个合同版本的JSON文件 |
| 否 | 以JSON格式输出结果 |
| Problem | Likely Cause | Solution |
|---|---|---|
| Placeholders left in final document | Rushed filling process | Use contract_clause_checker.py to scan for unfilled [BRACKETED] placeholders before sending |
| IP clause is unenforceable in EU/DACH | Using US work-for-hire language in EU context | Switch to explicit Nutzungsrechte transfer for DACH; use separate written assignment deed for EU |
| Client disputes scope after signing | Vague acceptance criteria or missing change order process | Define "accepted" = written sign-off within X business days; include change order clause with pricing mechanism |
| Payment disputes on hourly contracts | No time tracking requirement or unclear invoicing terms | Specify time tracking tool, invoicing frequency (monthly), and payment terms (net-30) in the contract |
| GDPR non-compliance penalty risk | Missing DPA for EU/DACH engagements involving personal data | Always include Art. 28 DPA when processing EU personal data; use the template block in this skill |
| Contract fails legal review | Jurisdiction mismatch or missing mandatory clauses | Run contract_clause_checker.py against the target jurisdiction before legal review |
| 问题 | 可能原因 | 解决方案 |
|---|---|---|
| 最终文档中仍有占位符 | 填充过程仓促 | 发送前使用contract_clause_checker.py扫描未填充的[BRACKETED]占位符 |
| 知识产权条款在欧盟/DACH地区无法强制执行 | 在欧盟语境下使用美国职务作品术语 | 对于DACH地区切换为明确的Nutzungsrechte转让条款;对于欧盟使用单独的书面转让契约 |
| 客户签署后对范围提出异议 | 验收标准模糊或缺少变更订单流程 | 定义“验收”= X个工作日内书面签字确认;包含带有定价机制的变更订单条款 |
| 按小时计费的合同出现付款纠纷 | 无时间跟踪要求或开票条款不明确 | 在合同中指定时间跟踪工具、开票频率(月度)和付款条款(月结30天) |
| 存在GDPR不合规处罚风险 | 涉及个人数据的欧盟/DACH合作缺少DPA | 处理欧盟个人数据时始终包含第28条DPA;使用本技能中的模板块 |
| 合同未通过法律审核 | 司法管辖区不匹配或缺少强制性条款 | 法律审核前使用contract_clause_checker.py针对目标司法管辖区进行检查 |