zoho-contract-lifecycle

name	zoho-contract-lifecycle
description	NDA、MSA、SOW、契約レビュー、承認、署名依頼、更新・保管を支援する。

zoho-contract-lifecycle

Purpose / 目的

NDA、MSA、SOW、契約レビュー、承認、署名依頼、更新・保管を支援する。

When to use / 利用場面

• Use this skill for NDA, MSA, SOW, amendment, renewal, termination, signature routing, contract approval packets, and contract-template selection.
• Use this skill when legal entity names, signers, governing terms, redlines, or signature requests are central to the work.

When not to use / 使用しない場面

• Do not use for invoice, PO, bill, or payment-status tasks unless contract terms are needed as context.
• Do not provide final legal advice; route legal terms to authorized reviewer.
• Do not send signature requests without approval from the business/legal owner.

Skill-specific procedure / 固有手順

1. Classify contract type: NDA, MSA, SOW, amendment, renewal, termination, or certificate.
2. Confirm parties, legal names, signers, template source, governing law, effective date, and related opportunity/project.
3. Prepare contract approval packet: draft/version, key terms, deviations, missing items, and reviewer routing.
4. After approval, prepare signature request payload and audit log; send only after explicit approval.

Hard rules / 厳守ルール

• This skill is operational support, not legal, tax, accounting, or financial advice. 法務・税務・会計判断は必ず担当者または専門家承認を得る。
• Never send quotes, invoices, purchase orders, bills, RFQs, signature requests, or external emails without explicit human approval.
• Before writing to Zoho Books / Zoho Contracts through MCP or API, produce a draft and a change summary; require approval for create/update/send actions.
• Separate facts, assumptions, missing information, risks, and recommended next actions.
• Minimize personal/confidential data in outputs. Mask bank, tax, payment, and sensitive contract details unless needed for the task.
• Confirm market/entity context: US entity, Japanese parent/subsidiary, currency, tax treatment, payment terms, and approval authority.
• For Zoho product capabilities, API/MCP availability, pricing, and workflow behavior, verify against current official Zoho sources before asserting.

Procedure / 手順

1. Intake — 顧客、案件、契約、見積、請求、ベンダー、金額、通貨、期日、承認者、関連 Zoho レコードを確認する。
2. Classify workflow — Quote-to-Cash / Procure-to-Pay / Contract Lifecycle / Recurring Invoice / Acceptance のどれかに分類する。
3. Retrieve context — Zoho MCP/API、既存テンプレート、過去案件、メール文面、契約テンプレートを参照する。取得できない情報は Missing として列挙する。
4. Draft only — Quote、SO、Invoice、PO、Bill、SOW、NDA、MSA、Acceptance Certificate、RFQ メール等はドラフトを作成し、変更点とリスクを添える。
5. Control gates — 金額、支払条件、税、契約条項、顧客送付、署名依頼、会計計上、外部メールは承認ゲートを通す。
6. Execute after approval — 承認後のみ Zoho やメールへ反映し、レコードID/URL/送信先/日時を監査ログへ残す。
7. Follow-up — 入金・未署名・未承認・期限超過・作業完了請求などの次アクションを提示する。

Inputs / 入力

• Company / customer / vendor name
• Zoho Books organization and record IDs when available
• Deal / project / contract type: Quote, SO, Invoice, PO, Bill, SOW, NDA, MSA, Acceptance Certificate
• Amount, currency, tax treatment, payment terms, billing split, due date
• Approval owner and external recipient
• Templates, clauses, customer/vendor instructions, email thread summary

Outputs / 出力

• Draft artifact or action plan
• Missing information checklist
• Approval checklist
• Risk notes
• Zoho MCP/API action plan with proposed create/update/send operations
• Audit log summary after execution

Quality gates / 品質ゲート

• No external-facing artifact is sent without human approval.
• Draft includes source record IDs or states that IDs are missing.
• Accounting/legal/tax assumptions are separated from facts.
• Customer/vendor-specific terms are not generalized into the reusable template.
• For Example Customer use, apply the company overlay skill after this generic skill.

Related skills / 関連スキル

• zoho-finance-contract-orchestrator

Contract lifecycle checklist

• Contract type: NDA / MSA / SOW / amendment / renewal / termination / certificate.
• Parties and signers: legal entity names, addresses, signer authority, counterpart contacts.
• Approval: business owner, legal reviewer, finance reviewer when pricing/payment terms are included.
• Signature request: prepare draft package and routing; send only after approval.

Output format example / 出力フォーマット例

Example: customer NDA signature packet.

• Facts: Mutual NDA; counterparty ABC Corp; template "standard mutual NDA v2026.1".
• Assumptions: Standard template, no deviations unless legal flags otherwise.
• Missing: Signer name/title, legal entity, governing-law confirmation.
• Draft (not sent): Contract packet with template/version and a deviation summary; signature routing prepared.
• Approval gates: legal terms · signature-request send.
• Next actions: obtain signer/entity; obtain legal approval; do not send the signature request until approved.

Approval checklist (Contract lifecycle)

• Contract type and template/version confirmed
• Counterparty legal entity and signer confirmed
• Deviations from the standard template flagged for legal
• Governing law / liability / IP clauses reviewed
• Legal or authorized approver captured
• Signature-request send approved (separate gate)

Zoho payload example

Illustrative contract/signature-routing object. Verify availability, fields, and scopes against the current Zoho Contracts / Zoho Sign capabilities. Keep as a draft; send the signature request only after approval.

{
  "contract_type": "NDA (mutual)",
  "template": "standard-mutual-nda-v2026.1",
  "counterparty": { "name": "ABC Corp", "legal_entity": "<entity>", "signer": "<name / title>" },
  "deviations": [],
  "routing": [
    { "order": 1, "role": "Counterparty signer" },
    { "order": 2, "role": "Our authorized signer" }
  ],
  "status": "draft — not sent",
  "approval_required": true
}