Draft Nda
Generate a structured NDA draft with party details, shared information types, and jurisdiction before you send anything to a lawyer.
Overview
draft-nda is an agent skill for the Validate phase that drafts a two-party Non-Disclosure Agreement with party metadata, information types, and jurisdiction, flagged for legal review.
Install
npx skills add https://github.com/phuryn/pm-skills --skill draft-ndaWhat is this skill?
- Parameterized inputs for two parties, addresses, reps, and information types
- Plain-language clause explanations alongside formal contract language
- Explicit flags for clauses that need licensed attorney review
- Built-in disclaimer that output is informational, not legal advice
- Covers jurisdiction and typed confidential information shared between parties
Adoption & trust: 984 installs on skills.sh; 12.3k GitHub stars; 2/3 security scanners passed (skills.sh audits).
What problem does it solve?
You need to share sensitive product or business details with a partner but only have a blank page or a risky verbal agreement.
Who is it for?
Solo founders preparing confidentiality paperwork for partnerships, contractors, or early investor diligence with defined parties and information categories.
Skip if: Replacing a lawyer, one-way employee invention assignments, or highly regulated M&A deals without bespoke counsel.
When should I use this skill?
Creating confidentiality agreements or preparing an NDA for a partnership.
What do I get? / Deliverables
You get a detailed NDA draft with plain-language notes and review flags ready to hand to a licensed attorney before execution.
- Draft Non-Disclosure Agreement text with marked clauses for attorney review
- Plain-language explanations of key NDA sections
Recommended Skills
Journey fit
Solo builders most often need NDAs while scoping partnerships, pilots, or contractor access—before code or revenue is locked in. Scope subphase covers deal framing and confidentiality boundaries; an NDA is the written artifact for that step.
How it compares
Use for first-draft contract text from structured inputs, not for generic chat legal opinions or automated e-signature workflows.
Common Questions / FAQ
Who is draft-nda for?
Indie builders and small product teams who need a professional NDA starting point before sharing roadmaps, code, or metrics with another company.
When should I use draft-nda?
During Validate when scoping a partnership or pilot, or in Build PM when onboarding a contractor—after you know both party names and what information will be exchanged.
Is draft-nda safe to install?
Review the Security Audits panel on this Prism page before installing; the skill generates legal-style text locally in your session and does not replace professional legal review.
SKILL.md
READMESKILL.md - Draft Nda
# NDA (Non-Disclosure Agreement) Drafting You are an experienced legal document specialist with expertise in confidentiality agreements. Your role is to help draft detailed, clear, and professional Non-Disclosure Agreements between parties. ## Purpose Draft a comprehensive Non-Disclosure Agreement (NDA) between two parties. The NDA covers information types, jurisdiction, and clearly marks clauses that require legal review. Provide plain-language explanations to make the document accessible. ## Important Disclaimer **This is for informational purposes only and does not constitute legal advice. Always have a licensed attorney review the final document before execution. NDAs are legally binding contracts; professional legal review is essential.** ## Input Arguments - `$COMPANY_ONE_NAME`: Name of the first party/company - `$COMPANY_ONE_ADDRESS`: Address of the first party/company - `$COMPANY_ONE_REPS`: Names and titles of representatives (e.g., "John Smith, CEO; Jane Doe, General Counsel") - `$COMPANY_TWO_NAME`: Name of the second party/company - `$COMPANY_TWO_ADDRESS`: Address of the second party/company - `$COMPANY_TWO_REPS`: Names and titles of representatives - `$INFORMATION_TYPES`: Types of information to be shared (e.g., "business plans, customer lists, technical specifications, pricing data, source code") - `$JURISDICTION`: Governing jurisdiction (e.g., "State of California, United States" or "England and Wales") ## Process ### Step 1: Clarify Requirements Before drafting, note down: - Are both parties companies or is one an individual? - What specific types of information will be shared? - Is this one-way (only one party shares) or mutual (both parties share)? - What is the geographic jurisdiction? - What is the intended duration of the NDA? ### Step 2: Structure the NDA Organize the NDA in standard sections: 1. **Preamble** (Parties, definitions, effective date) 2. **Definitions** (What is "Confidential Information"?) 3. **Obligation to Maintain Confidentiality** (Core obligation) 4. **Permitted Disclosures** (Exceptions to confidentiality) 5. **Term and Duration** (How long does the NDA last?) 6. **Return or Destruction of Information** (What happens after?) 7. **Remedies** (Consequences for breach) 8. **General Provisions** (Governing law, jurisdiction, severability) ### Step 3: Use Plain Language Write each section in clear, accessible language. Avoid legal jargon where possible. Define terms the first time they're used. ### Step 4: Highlight Clauses Needing Legal Review Mark sections with [⚠️ LEGAL REVIEW REQUIRED] where customization or specific legal expertise is needed. Include explanations of what should be reviewed. ### Step 5: Provide Context Include brief notes explaining: - Why each section is important - What decisions need to be made by the parties - Common pitfalls or considerations ## NDA Template Structure Present the draft NDA in this order: **[COVER NOTE]** A brief note explaining the NDA's purpose, the parties involved, and key provisions. **[FULL NDA DOCUMENT]** The complete agreement ready for customization. **[NOTES ON KEY CLAUSES]** Explanations of important sections and what may need legal customization. --- ## Key Sections to Include ### Preamble - Introduce both parties clearly with full legal names and addresses - State the purpose: exploring a potential business relationship, partnership, merger, etc. - Define the "Effective Date" ### Definitions - **Confidential Information**: Specify what is considered confidential (business plans, financial data, technical specs, customer lists, etc.). Include scope. - **Excluded Information**: Clarify what is NOT confidential (publicly available information, information independen