epic-3-contract

Automate end-to-end Epic 3 contract lifecycle with e-signature workflows.

Updated Apr 26, 2026
One-click install
npx skills add https://github.com/wangzeping114/shareflow --skill epic-3-contract
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: epic-3-contract
Source: https://github.com/wangzeping114/shareflow/tree/main/.claude/skills/epic-3-contract
Command: npx skills add https://github.com/wangzeping114/shareflow --skill epic-3-contract

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Epic 3 contracts require coordinated lifecycle management for creation, review, signing, and archival, including templates, signatures, and link-based delivery after Epic 2 prerequisites are met.

Core Features & Use Cases

  • End-to-end lifecycle management: draft, review, send for signature, sign, and archive.
  • Template-driven contracts: render contracts from regional templates via a template factory.
  • Signature capture & verification: Canvas-based handwritten signatures with token-based signing flow and expiry.
  • Delivery & storage: generate short links for sign invites and store generated PDFs in object storage with traceable metadata.
  • Event-driven workflow: domain events emit ContractSignedEvent to trigger downstream processes (PDF generation, account provisioning, notifications).

Quick Start

Draft a new contract for a project, generate a signing link, and prepare it for investor signature.

Frequently Asked Questions about epic-3-contract

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate the contract lifecycle from draft to e-signature?

Automate contract lifecycles by using a state machine to manage state transitions from draft to review, signature, and archival. The workflow handles template rendering, token-based signing, and PDF generation.

Can I capture handwritten signatures on PDF contracts without external e-signature tools?

Yes, you can capture handwritten signatures directly using Canvas-based signature capture. The workflow implements token-based signing with expiry to securely collect and verify signatures on generated PDF contracts.

How do I generate and send contracts for signature to external parties?

Generate short links for signing invitations and deliver them to external parties. The system handles link delivery, validates the signing token, captures the signature, and stores the final PDF in object storage.

Do I need to complete Epic 2 prerequisites before managing contract signatures?

Yes, Epic 3 contract management requires completed Epic 2 prerequisites. The domain model builds upon these prerequisites to enable contract entities, state transitions, and the template factory for regional rendering.

How does the contract workflow handle downstream processes after a document is signed?

The workflow uses event-driven handling by emitting a ContractSignedEvent. This domain event triggers downstream processes automatically, including PDF generation, account provisioning, and external notifications.

What is the best way to render contracts from regional templates?

Use a template factory to render contracts from regional templates. This approach standardizes document generation by applying predefined templates to domain entities before initiating the signature workflow.