Skip to content

t1k:marketing:b2b:agreements

FieldValue
Moduleb2b
Version0.2.4
Effortlarge
Tools—
/t1k:marketing:b2b:agreements

Flagship B2B skill for Playable Labs commercial agreements. Three modes: draft, review, propose. Covers SOW (per-playable + package), MSA, NDA, kill-fee addendum, IP-usage-rights clause, and revision-policy clause.

Cross-kit dependencies: theonekit-core:t1k-extended ≥ 1.102.3 — ships t1k:contract, t1k:contract-review, t1k:negotiation.

Legal reminder: All templates ship as DRAFT scaffolds. The1Studio legal sign-off is required before any template is used with a real client.


Keywords (from module.json): sow, msa, nda, agreement draft, agreement review, agreement propose, playable labs agreement, kill fee, ip rights clause, revision policy

Invocation forms:

/t1k:marketing:b2b:agreements draft sow-per-playable client=<name> deliverables=<N> fee=<amount>
/t1k:marketing:b2b:agreements draft sow-package tier=<bronze|silver|gold> client=<name>
/t1k:marketing:b2b:agreements draft msa client=<name>
/t1k:marketing:b2b:agreements draft nda client=<name>
/t1k:marketing:b2b:agreements review path=<incoming-doc-path>
/t1k:marketing:b2b:agreements propose draft=<path> client=<name>

Parse the first positional argument after the skill name to determine mode.

Purpose: Fill a template with known defaults + client-supplied parameters to produce a near-ready document for legal review.

Step 1 — Identify document type Read the second positional argument or infer from context:

  • sow-per-playable → per-playable SOW
  • sow-package → Bronze/Silver/Gold package SOW
  • msa → Master Services Agreement
  • nda → Mutual NDA
  • kill-fee-addendum → Kill-fee schedule (typically appended to SOW)
  • ip-usage-rights → IP usage rights clause
  • revision-policy → Revision policy clause

If ambiguous, ask: “Which document type? SOW per-playable / SOW package / MSA / NDA / kill-fee addendum / IP-rights clause / revision policy clause”

Step 2 — Load defaults Read references/playable-labs-defaults.json. Apply all fields to the template as [PLAYABLE_LABS_DEFAULT] pre-fills. Annotate substituted values so the reviewer can confirm or override.

Step 3 — Collect client parameters Prompt for any [CLIENT TO CONFIRM] fields not already supplied in the invocation:

  • Client legal name and jurisdiction
  • Fee / rate
  • Deliverable count and scope
  • Milestone schedule
  • Execution date

Step 4 — Fill template Follow references/playbooks/draft-mode.md for the parameter-fill guide and pre-finalize checklist.

Step 5 — Output Produce filled Markdown. Prepend:

## Draft Status
Document: <type>
Client: <name>
Filled by: t1k:marketing:b2b:agreements (draft mode)
Legal sign-off: REQUIRED before client use
Outstanding [CLIENT TO CONFIRM] items: <list any remaining>

Purpose: Adversarially review an incoming redlined or counter-proposed document using Playable Labs context.

Step 1 — Read the document Read the file at path=. If PDF, extract text. Identify document type (SOW, MSA, NDA, other).

Step 2 — Load Playable Labs context From references/playable-labs-defaults.json: load standard positions on payment terms, IP ownership, kill-fee thresholds, revision caps, liability limits, jurisdiction.

Step 3 — Delegate to t1k:contract-review Invoke t1k:contract-review with:

  • The full document text
  • The Playable Labs context block (payment terms, IP policy, kill-fee floor, jurisdiction, liability cap)
  • Instruction: rate each clause red / amber / green; flag clauses that deviate from Playable Labs standard positions

Step 4 — Build review output Follow references/playbooks/review-mode.md. Produce:

  • Red clauses (reject / must-renegotiate)
  • Amber clauses (negotiate if possible, accept if deal-critical)
  • Green clauses (acceptable as-is)
  • Negotiation priority list (highest-risk reds first)
  • Recommended counter-language for each red clause

Purpose: Wrap a finalized draft in a client-ready proposal package with cover note, pricing rationale, and a send checklist.

Step 1 — Load the draft Read the file at draft=. Confirm it has passed legal sign-off (prompt user to confirm if not noted in the document).

Step 2 — Generate cover note Personalize for client=. Include:

  • Playable Labs engagement summary (2–3 sentences)
  • Reference to attached agreement type
  • Call to action (sign by date / book call to discuss)
  • Contact name (use default from playable-labs-defaults.json or prompt)

Step 3 — Pricing rationale block Summarize fee justification aligned to value delivered:

  • Deliverable count and complexity
  • Reference to market rates (Playable Labs pricing-models context)
  • Any discounts or package inclusions noted

Step 4 — Send checklist Follow references/playbooks/propose-mode.md. Gate items:

  • Legal sign-off obtained
  • NDA in place (or included in this package)
  • Signature workflow set (DocuSign / PandaDoc / email-PDF)
  • Pricing approved by Playable Labs stakeholder
  • Client POC and legal contact confirmed

Step 5 — Hand off to t1k:negotiation (if multi-round expected) If the client is known to negotiate, invoke t1k:negotiation with the draft, BATNA, and walk-away thresholds from playable-labs-defaults.json.


  • references/templates/ — 7 DRAFT document templates
  • references/playbooks/draft-mode.md — parameter-fill guide + pre-finalize checklist
  • references/playbooks/review-mode.md — adversarial review delegation guide
  • references/playbooks/propose-mode.md — cover note + pricing rationale + send checklist
  • references/playable-labs-defaults.json — Playable Labs standard positions
SkillModulePurpose
t1k:contracttheonekit-core:t1k-extendedRender filled MD → PDF/DOCX for client output
t1k:contract-reviewtheonekit-core:t1k-extendedAdversarial clause review on incoming redlines
t1k:negotiationtheonekit-core:t1k-extendedMulti-round negotiation playbook