twenty-partner-design-doc

Generates partner-scoping design docs translating qualified CRM leads into Twenty terms.

Updated Aug 3, 2026
One-click install
npx skills add https://github.com/masoodtalha/twenty --skill twenty-partner-design-doc-masoodtalha
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: twenty-partner-design-doc
Source: https://github.com/masoodtalha/twenty/tree/main/packages/twenty-apps/internal/twenty-partners/src/skills/twenty-partner-design-doc
Command: npx skills add https://github.com/masoodtalha/twenty --skill twenty-partner-design-doc-masoodtalha

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Sales and partnerships teams need to turn raw lead materials (call summaries, braindumps, client docs) into a structured design doc that an implementation partner can scope and quote from, without inventing requirements or making unverified product capability claims. ## Core Features & Use Cases - Zero-inference partner briefs: Default mode produces a one-page brief containing only what the client explicitly said, with placeholders for undiscussed sections and no invented fields or scope. - Full inference mode: The --full flag enables a richer design doc with tagged inferences (🔮 inf.), a Source column in the data-model table, and longer output. - Live capability verification: Load-bearing claims about Twenty (permissions, dashboards, hosting, integrations) are verified against live docs.twenty.com pages before being stated as fact, with a references appendix mapping claims to sources. - Use Case: After an intro call with a prospective CRM client, point the skill at the lead folder to produce a 12-section partner brief, a verification appendix, and a partner-match-criteria file for the handoff. ## Quick Start Point the skill at a lead folder containing a call summary and ask it to draft a partner design doc in zero-inference mode.

Frequently Asked Questions about twenty-partner-design-doc

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

FAQPage Schema
How do I create a partner design doc from a sales call summary?▼

Point the skill at the lead folder containing the call summary and any client docs, then ask it to draft a design doc. It reads all materials, extracts grounded facts, and produces a 12-section brief saved as YYYY-MM-DD-<lead>-partner-brief.md.

What is the difference between default mode and --full mode?▼

Default mode is zero-inference: only what the client explicitly said appears, with placeholders for empty sections and a one-page target. The --full flag allows tagged inferences, adds a Source column to the data-model table, and permits longer output saved as a design-doc file.

Does the skill verify Twenty product capabilities before claiming them?▼

Yes. Any load-bearing claim about what Twenty can or cannot do is verified live against docs.twenty.com pages before being stated as fact. Unverifiable claims are marked as open questions and listed in the references appendix.

What inputs does the design doc skill require?▼

It needs a lead folder containing a twenty-lead-intro-call-summary output plus any braindump or client documents. If only a raw transcript exists, run the intro-call-summary skill first, since this skill chains after it.

What happens when the client brief is thin or incomplete?▼

The skill under-reaches rather than fills gaps: it models only the few most certain objects, marks everything else as open questions, and states plainly that the model is a minimal starting sketch to validate with the client.