draft-nda▌
phuryn/pm-skills · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
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.
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:
- Preamble (Parties, definitions, effective date)
- Definitions (What is "Confidential Information"?)
- Obligation to Maintain Confidentiality (Core obligation)
- Permitted Disclosures (Exceptions to confidentiality)
- Term and Duration (How long does the NDA last?)
- Return or Destruction of Information (What happens after?)
- Remedies (Consequences for breach)
- 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 independently developed, information received from third parties without confidentiality obligations)
Obligations
- Describe the receiving party's duty to keep information confidential
- Specify approved uses of the information
- Outline permitted disclosures (to employees, advisors, on a need-to-know basis)
- [⚠️ LEGAL REVIEW REQUIRED] Standard of care (e.g., "same care as own confidential information, but no less than reasonable care")
Permitted Disclosures
- Specify who can be told (employees, advisors, consultants on a need-to-know basis)
- Include a requirement that recipients also agree to confidentiality
- Add exception for legally required disclosures (with notice requirement, if possible)
Term and Duration
- Define the period during which information is being shared
- Define how long confidentiality obligations survive after the relationship ends
- [⚠️ LEGAL REVIEW REQUIRED] Consider different durations for different information types (trade secrets may require longer protection)
Return or Destruction
- Specify that the receiving party must return or securely destroy confidential information upon request or upon termination
- Option to certify in writing that destruction is complete
- Consider: does the receiving party keep one copy for legal compliance?
Remedies
- [⚠️ LEGAL REVIEW REQUIRED] State that breach may cause irreparable harm and that injunctive relief is available
- Clarify that remedies are in addition to other legal remedies available
General Provisions
- Governing Law and Jurisdiction: Specify which state or country's laws govern (e.g., California or England)
- [⚠️ LEGAL REVIEW REQUIRED] Dispute resolution process (litigation, arbitration, mediation)
- Severability: If one provision is invalid, others remain in force
- Entire Agreement: This NDA supersedes prior discussions
- Amendments: Specify that NDA can only be modified in writing, signed by both parties
- Counterparts: Parties can sign separate copies
Content Guidelines
- Plain Language: Write for a primary-school-educated reader. Avoid Latin phrases, unnecessary legal terms.
- Clarity over Precision: Choose clear language first. Legal precision can be refined by attorneys.
- Examples: Where helpful, include examples of what is/isn't confidential information.
- Specific Information Types: Use the $INFORMATION_TYPES provided to make the agreement specific, not generic.
- Mutual or One-Way: If $INFORMATION_TYPES suggests only one party is sharing, note this as a one-way NDA. If both, use mutual language.
Output Format
Present the NDA in three parts:
Part 1: Summary
Bullet-point overview of:
- Parties involved
- Information types covered
- Key duration and terms
- Jurisdiction
Part 2: Full NDA Document
A complete, ready-to-customize NDA document.
Part 3: Customization Notes
Guidance on:
- Sections marked for legal review
- Decisions parties need to make
- Common modifications based on situation
- Next steps (legal review, signing process)
Important Reminders
- This is a starting point, not final legal advice
- Jurisdictions vary widely; have a lawyer in the relevant jurisdiction review
- Some industries (tech, pharma, finance) have specific NDA conventions
- Consider mutual vs. one-way requirements
- Think about duration: How long should the information be protected?
- Always have an attorney review before any party signs
How to use draft-nda on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add draft-nda
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches draft-nda from GitHub repository phuryn/pm-skills and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate draft-nda. Access the skill through slash commands (e.g., /draft-nda) or your agent's skill management interface.
Security & Verification Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
User Story & Requirements Generation
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Competitive Analysis
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
Make data-driven prioritization decisions faster
Stakeholder Communication
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Installation Steps
- 1.Install product management skill
- 2.Start with user story generation for known feature
- 3.Progress to competitive analysis: research 2-3 competitors
- 4.Use for roadmap prioritization: apply RICE/ICE scoring
- 5.Draft stakeholder communications and refine based on feedback
- 6.Build template library for recurring PM tasks
- 7.Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices▌
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This▌
✓ Use When
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid When
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path▌
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.6★★★★★72 reviews- ★★★★★Sophia Kapoor· Dec 28, 2024
Keeps context tight: draft-nda is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Yusuf Ghosh· Dec 28, 2024
draft-nda reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Aisha Rao· Dec 24, 2024
draft-nda is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Pratham Ware· Dec 16, 2024
Registry listing for draft-nda matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Mateo Mensah· Dec 12, 2024
I recommend draft-nda for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Liam Bansal· Dec 4, 2024
Solid pick for teams standardizing on skills: draft-nda is focused, and the summary matches what you get after install.
- ★★★★★Chinedu Kim· Dec 4, 2024
We added draft-nda from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Sophia Dixit· Nov 19, 2024
draft-nda is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Evelyn Mensah· Nov 19, 2024
Registry listing for draft-nda matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Aisha Gill· Nov 15, 2024
Keeps context tight: draft-nda is the kind of skill you can hand to a new teammate without a long onboarding doc.
showing 1-10 of 72