AGENT SKILL

legal-ops-edho-ferdian

Draft agreement paperwork from one template plus a JSON spec per counterparty (NDA, referral fee, non-circumvention, master services), add deals by Schedule A, and prepare e-sign envelopes as drafts. Not legal advice. Use for "bikin perjanjian dari template", "master agreement", "NDA untuk banyak partner", "siapkan envelope e-sign".

License 许可
MIT
所属仓库
edhoferdian/EEF
最近更新
2026-10-30
Stars
★ 22
Forks
0

01 前言 Front Matter

name
legal-ops-edho-ferdian
metadata
{ "last_reviewed": "2026-09-24" }
description
Draft agreement paperwork from one template plus a JSON spec per counterparty (NDA, referral fee, non-circumvention, master services), add deals by Schedule A, and prepare e-sign envelopes as drafts. Not legal advice. Use for "bikin perjanjian dari template", "master agreement", "NDA untuk banyak partner", "siapkan envelope e-sign".

02 资源文件 5

03 SKILL.md 正文

Legal Ops — Edho Ferdian Mode

Two linked workflows that turn paperwork into tracked, diffable source:

  1. Drafting — one counsel-approved template, one JSON spec per counterparty, one build step. references/agreement-drafting.md.
  2. Envelope preparation — placing signature/date/text fields in a web e-signature composer through an already signed-in browser session, then saving a draft for the operator. references/esign-field-placement.md.

Non-negotiables

  • Not legal advice. This skill produces documents and automation; it does not decide whether terms are enforceable, appropriate, or compliant in a jurisdiction. Every clause must come from, or be reviewed by, qualified counsel. Say so to the user whenever you hand over a document.
  • Everything is a DRAFT. A successful build or conversion proves an artifact exists — not legal completeness, signing authority, or readiness to send. There is no "execution copy" mode; an execution version is a separate, reviewed record.
  • The agent never signs, declines, voids, sends, or enters credentials. Sending an envelope requires an explicit operator instruction bound to the exact envelope (see the hard gate in the e-sign reference), consistent with safe-execution-edho-ferdian Gate 2.
  • Notices to counterparties go through approval. A Schedule A notice or any contractual message reaches a counterparty only via counterparty-comms-edho-ferdian's approval loop.
  • Signed documents are immutable. Later changes produce a new draft or a notice; the executed file is never edited or regenerated in place.

Workflow at a glance

  1. Put the counsel-approved template and each counterparty's spec under version control; generated .md/.docx output stays out of it.
  2. Build with scripts/build-agreement.js (Node 18+, no dependencies; pandoc optional for .docx). Diff the Markdown against the previous draft before anyone reviews it.
  3. After counsel review, prepare the envelope in the e-sign composer: calibrate, place fields per recipient, capture evidence, save as draft.
  4. The operator reviews the draft envelope and the evidence screenshot, then sends it themselves or gives a bound send instruction.
  5. For later deals under an executed agreement, follow the Schedule A notice procedure — confirm authority first, approve the exact notice, record delivery evidence, then rebuild an internal consolidated draft view.

References

  • references/agreement-drafting.md — template placeholders, spec format and validation, role table, build command and failure modes, signature page geometry, and the Schedule A notice procedure.
  • references/esign-field-placement.md — trusted browser target checks, recipients and signing order, coordinate calibration, per-recipient field placement, evidence capture, the hard gate, and a checklist.
  • references/master-template.example.md — skeleton template with bracketed placeholders for counsel-approved clauses.
  • references/spec.example.json — example counterparty spec.

External docs (fixed — see skill-authoring-edho-ferdian's canonical contract)

pandoc options and a specific e-signature provider's composer UI change over time — resolve them live (Context7 or the provider's current docs) before automating against them. Full contract: skill-authoring-edho-ferdian §9.

Surgical changes (fixed — see skill-authoring-edho-ferdian's canonical contract)

When editing a template or spec, change only the clause or field the task names and rebuild; never reflow or "tidy" counsel-approved wording as a side effect — a cosmetic diff in legal text still needs review. Full contract: skill-authoring-edho-ferdian §10.

Language routing (fixed — see skill-authoring-edho-ferdian's canonical contract)

Communication to the user in Bahasa Indonesia; code, comments, and generated files in English — fixed, never ask. The agreement's own language is the one counsel chose for the template, not this rule. Full contract: skill-authoring-edho-ferdian §7.

04 同仓库更多 Skills

edhoferdian
edhoferdian/EEF

video-style-edho-ferdian

Measure a reference video's look and pacing (colour grade as a 3D LUT, cut rhythm, overlays) and reproduce it: grade, cut and composite new footage, verify numerically, hand off an NLE timeline. Use for "tiru look video ini", "samakan grading", "bikin video dengan gaya referensi", "LUT dari referensi", "cut rhythm".

★ 22
edhoferdian
edhoferdian/EEF

test-authoring-edho-ferdian

Write unit and component tests well: React Testing Library, pytest, Go and Vue, plus regression-test patterns. Use for "tulis test untuk component ini", "bagaimana test hook ini", "test yang bagus untuk fitur X", "tulis test pytest/Go/Vue", or dev-kickoff's TEST stage.

★ 22
edhoferdian
edhoferdian/EEF

system-design-edho-ferdian

Mid-project architecture decisions: ADRs, trade-off analysis, non-functional requirements, scaling tiers and blast radius. Use for "desain arsitektur", "keputusan teknis besar", "bikin ADR", "trade-off antara X dan Y", "microservices atau monolith", "apa yang rusak kalau X diubah", or a capacity question.

★ 22
edhoferdian
edhoferdian/EEF

spec-mining-edho-ferdian

Extract behavioural specs from a codebase with none: WHEN/THEN requirements and invariants, each anchored to the code that enforces it, unclear behaviour recorded as uncertainty. Use for "ekstrak spec", "buat spec dari kode", "reverse-engineer the spec", "repo ini tidak ada dokumentasi", or a missing BEHAVIOR_SPEC in dev-kickoff.

★ 22
edhoferdian
edhoferdian/EEF

skill-authoring-edho-ferdian

Create and govern this ecosystem's skills: search before building, a quality bar, compliance checks, promoting repeated principles to rules, and packaging dist/*.skill. Use for "bikin skill baru", "ada skill buat X gak", "fork skill ini", "skill gue kepake gak sih", "package skill ini", "buatkan .skill-nya".

★ 22
edhoferdian
edhoferdian/EEF

skill-audit-edho-ferdian

Audit this repo's skills/ for staleness, redundancy, broken cross-references and weak descriptions (not the ~/.claude setup: that is config-hygiene). Use for "audit skill saya", "cek skill yang sudah dibuat", "ada yang redundan gak", "skill mana yang basi".

★ 22