From documenso-pack
Implement Documenso template-based workflows and direct signing links. Use when creating reusable templates, generating documents from templates, or implementing direct signing experiences. Trigger with phrases like "documenso template", "signing link", "direct template", "reusable document", "template workflow".
How this skill is triggered — by the user, by Claude, or both
Slash command
/documenso-pack:documenso-core-workflow-bThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Create reusable templates, generate documents from templates, and implement direct signing experiences with Documenso.
Create reusable templates, generate documents from templates, and implement direct signing experiences with Documenso.
documenso-core-workflow-aimport { Documenso } from "@documenso/sdk-typescript";
// 1. Create template once
For detailed implementation code and configurations, load the reference guide:
Read(${CLAUDE_SKILL_DIR}/references/implementation-guide.md)
| Error | Cause | Solution |
|---|---|---|
| Template not found | Invalid ID or deleted | Verify template exists |
| Recipient mismatch | Wrong number of recipients | Match template roles |
| Field not found | Invalid field ID for prefill | Get field IDs from template |
| Direct link disabled | Feature not enabled | Enable in template settings |
| Duplicate failed | Template in use | Try with different title |
For error handling patterns, see documenso-common-errors.
Basic usage: Apply documenso core workflow b to a standard project setup with default configuration options.
Advanced scenario: Customize documenso core workflow b for production environments with multiple constraints and team-specific requirements.
npx claudepluginhub aiminnovations/claude-code-plugins-plus --plugin documenso-pack4plugins reuse this skill
First indexed Jul 11, 2026
Guides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Synthesizes the current conversation into a structured spec (PRD) and publishes it to the project issue tracker with a ready-for-agent label, without interviewing the user.