Agentic Contract Skill

Purpose

Generate a configurable CompleteTech LLC Agentic Development Services Agreement PDF with optional cover page, letterhead, header, footer, watermark, and legacy #10 addressed envelope output.

System Boundary

This skill owns agreement content and contract package generation from approved terms. Use agentic-proposal-skill for commercial scope before signature, agentic-invoice-skill for payment requests, agentic-envelope-skill for recipient metadata, attachment manifests, delivery-readiness, and standalone mailing packages, agentic-delivery-skill after approval, and counsel-reviewed source terms for real legal commitments. Do not use this skill to invent legal terms, client facts, pricing, authority, or signature approval.

Resource Guide

• generate_contract.py - contract and envelope generator.
• references/agentic_development_agreement.md - packaged contract template with Jinja2 placeholders.
• config.ini - declarative provider, client, agreement, agentic-development, branding, and envelope settings.
• client_config.example.ini, examples/minimum_client_override.ini - override examples.
• assets/logo.png - primary CompleteTech logo.

Required Inputs

1. Provider business details: legal name, trade name, entity type, formation state, mailing address, email, phone, website, signatory name and title.
2. Client details: legal name, entity type, address, signatory name and title.
3. Project details: contract ID, effective date, project name, services summary, timeline, fee amount, payment terms.
4. Agentic development details: system description, autonomy level, human-in-the-loop requirements, model or stack, deployment environment, evaluation plan, monitoring plan, excluded uses.
5. Branding and rendering settings: watermark text, monogram, accent color, letterhead on/off, header on/off, footer on/off, envelope on/off.

Do not invent real legal or company facts. Use TBD for unknown values unless the user explicitly asks for a demo placeholder.

Quality Rules

• Do not invent legal terms, company facts, client facts, authority, acceptance, pricing, or signature approval.
• Preserve demonstration disclaimers unless the user supplies replacement counsel-reviewed terms.
• Keep unknown provider, client, agreement, delivery, and agentic-development values as TBD.
• Treat generated PDFs and Markdown as draft artifacts until the user confirms the terms and facts.
• Keep contract generation separate from proposals, invoices, delivery records, security signoff, customer success notes, email copy, and delivery packaging decisions.
• Do not overwrite user-specific config or generated output without checking whether it contains client-specific facts that should be preserved.

Configuration Toggles

In [branding]:

watermark_enabled = yes
watermark_text = DEMO DRAFT
letterhead_enabled = yes
header_enabled = yes
footer_enabled = yes
envelope_enabled = yes

Set any toggle to no to disable that feature. The envelope is generated as a separate #10 envelope PDF when envelope_enabled = yes.

Generator

pip install -r requirements.txt

python generate_contract.py --config config.ini \
  --out output/agentic_development_contract.pdf

python generate_contract.py \
  --config config.ini examples/minimum_client_override.ini \
  --out output/acme_agentic_development_contract.pdf \
  --envelope-out output/acme_envelope.pdf

python generate_contract.py --config config.ini --out output/no_envelope_contract.pdf --no-envelope

Agent Operating Guidance

1. Read the user's business profile or provided inputs.
2. Update config.ini or create an override INI. Keep unknown details as TBD.
3. Ensure demonstration disclaimers remain visible unless the user supplies replacement legal text.
4. Run generate_contract.py.
5. Return links to the PDF, Markdown source, and ZIP or folder as appropriate.
6. Remind the user that the document is a demonstration template, not legal advice, unless the user already states that their own reviewed legal terms are being inserted.
7. Preserve existing client-specific outputs unless the user asks to regenerate or replace them.

Customizing the Contract

Edit references/agentic_development_agreement.md to change clauses, add jurisdiction-specific language, or include business-specific statement-of-work text. The generator supports a practical Markdown subset:

• #, ##, and ### headings.
• Paragraphs.
• - bullet lists.
• Simple Markdown tables.
• **bold** inline emphasis.
• Block quotes beginning with >.
• [PAGE_BREAK] for manual page breaks.

Dependencies

Install dependencies with:

pip install -r requirements.txt

The generator uses reportlab for PDF creation and jinja2 for contract template rendering.

Certificate Receipt Guidance

The skill remains usable without a classroom key. When certificate credit is needed, use scripts/request_receipt.py after the skill run. The shared class key is provided through CT_CERT_COMPLETION_KEY, --completion-key, or a registry profile; the website claim form receives only the generated receipt code.

Receipt requests include this skill ID: agentic-contract-skill. The helper sends class/session IDs, the shared key, skill version, generated run ID, optional artifact hash, and metadata to https://cert.complete.tech/api/skill-runs. The student claims the certificate at https://cert.complete.tech/claim with the returned receipt.

Do not print, store, or commit real classroom completion keys.