legal-ip-review
Review the intellectual property terms in an agreement — background and foreground IP, assignment and work-for-hire, license grants, open-source conflicts, freedom to operate and common IP traps. Use
SKILL.mdskills/legal-ip-review/SKILL.md
GitHubIP Review
Review intellectual property provisions for "$ARGUMENTS". Analyze ownership structures, license grants, assignment provisions, and open-source implications to identify IP-related risks and traps.
Note: AI-generated legal content does not constitute legal advice. Consult a qualified attorney.
Arguments. $ARGUMENTS may contain the project name and optional flags. Take the first token as <project> and treat --skip-checks as a flag; never include flags in file paths. All paths below use <project>. If --skip-checks is present, skip the prerequisite check and, before writing any artifact, append one line to .singularskills/log.jsonl: {"ts":"<ISO timestamp>","skill":"legal-ip-review","workflow":"legal","phase":2,"project":"<project>","event":"skipped","artifact":"02-review.md","note":"<reason or \"none given\">"}.
Prerequisites
Part of a workflow. This skill is phase 2 (Review) of the Legal Lifecycle workflow (legal); cross-domain workflows run it too. First check .singularskills/log.jsonl for an open run for this project: a run-started line with "project":"<project>" and no later run-finished line for the same workflow and project. If one exists, the conductor is running you: continue here. Otherwise, if the user asked to start, run, continue or resume a process or workflow rather than this one step, do not continue here: invoke the workflow skill with the workflow the user asked for, or legal when they named none, followed by <project>; it runs this phase in order, asks before it writes and records the run. Otherwise continue here: a later phase runs on its own, behind its gate.
Run this skill's gate before writing: sh <this skill's folder>/scripts/gate.sh <project> <project root>, where <project root> is the folder that contains .singularskills/ (use . when you are already there). If it exits non-zero, stop and tell the user what it printed, unless --skip-checks was given (see Arguments). On a refusal, before you stop, append this line to .singularskills/log.jsonl (create the folder and file if missing): {"ts":"<ISO timestamp>","skill":"legal-ip-review","workflow":"legal","phase":2,"project":"<project>","event":"refused","artifact":"02-review.md","note":"<what the gate printed>"}. Once the gate has passed, or under --skip-checks once you have appended the skipped line, append this line before you start work: {"ts":"<ISO timestamp>","skill":"legal-ip-review","workflow":"legal","phase":2,"project":"<project>","event":"started","artifact":"02-review.md","note":""}.
Check that .singularskills/legal/<project>/00-assess.md exists. If it does not exist, stop and tell the user:
"Run an Assess skill first (e.g.
/legal-risk-assessment <project>) to generate the prerequisite assessment artifact."
Process
Read inputs:
- Read
.singularskills/legal/<project>/00-assess.mdfor risk and jurisdiction context - Read IP-related provisions from the document provided by the user
- Read
Analyze ownership structure:
- Background IP — pre-existing IP each party brings to the relationship
- Foreground IP — IP created during the engagement
- Joint IP — IP created collaboratively (ownership, licensing, and exploitation rights)
- Verify clear delineation between background and foreground IP
Review work-for-hire vs. assignment provisions:
- Does the relationship qualify for work-for-hire under applicable law?
- If assignment is used, is it present assignment ("hereby assigns") or future obligation?
- Are moral rights addressed (waiver or retention)?
- Is consideration adequate for the scope of assignment?
Analyze license grants:
- Scope — what IP is licensed and for what purpose
- Exclusivity — exclusive vs. non-exclusive
- Sublicensing — right to sublicense and any restrictions
- Territory — geographic scope of the license
- Duration — term of the license (fixed, perpetual, tied to agreement)
- Revocability — can the license be revoked and under what conditions
Assess open-source implications:
- Do any open-source licenses conflict with IP assignment or exclusivity?
- Are there copyleft obligations that could affect proprietary code?
- Is there an open-source usage policy referenced or required?
- Check for license compatibility between open-source components
Evaluate freedom to operate:
- Can each party continue its business without infringing on rights granted?
- Are there restrictions that limit future product development?
- Do non-compete or non-solicit provisions affect IP exploitation?
Review invention disclosure obligations:
- Are there obligations to disclose inventions created during the engagement?
- What is the scope of disclosure (only related inventions or all inventions)?
- Are there time-limited obligations that extend beyond the agreement?
Flag common IP traps:
- Overly broad assignment (all IP, not just project-related)
- Missing background IP carve-out (existing IP inadvertently assigned)
- Perpetual irrevocable licenses without adequate consideration
- Ambiguous ownership of derivative works
- No license-back for assigned IP needed in ongoing operations
- IP representations without adequate knowledge qualifiers
Write the artifact — append to
.singularskills/legal/<project>/02-review.mdunder a## IP Reviewsection. Create the file with a# Review — <project>heading if it does not exist; if a## IP Reviewsection already exists, replace only that section. The section contains:- Ownership Analysis — background IP, foreground IP, and joint IP breakdown
- Assignment and Work-for-Hire — structure, adequacy, and moral rights
- License Grant Summary — scope, exclusivity, territory, duration per license
- Open-Source Assessment — compatibility analysis and copyleft risks
- Freedom to Operate — impact on each party's ongoing business
- Invention Disclosure — obligations and scope
- IP Traps Identified — flagged issues with risk explanation
- Recommendations — specific actions to mitigate IP risks
Output
The IP review appended to .singularskills/legal/<project>/02-review.md. Present a summary to the user highlighting:
- Ownership structure (who owns what, and is it clearly defined?)
- IP traps identified and their severity
- Open-source compatibility concerns
- Top recommendations for IP protection
Record the run. After you have written your section, append this line to .singularskills/log.jsonl (the started line of Prerequisites, with "event":"finished"): {"ts":"<ISO timestamp>","skill":"legal-ip-review","workflow":"legal","phase":2,"project":"<project>","event":"finished","artifact":"02-review.md","note":""}.
This artifact is shared by every skill of phase 2 (Review). The frontmatter is written once, by whoever creates the file: if you create it, open it with the block below (skill is the phase title, started the time of that first write; gate is passed when the gate ran clean and skipped under --skip-checks); if it already exists, leave the block alone except to update finished and to set gate to the worst value among the sections (skipped over passed).
---
skill: Review
workflow: legal
phase: 2
project: <project>
started: <ISO timestamp>
finished: <ISO timestamp>
agent: <the agent you run in, or "unknown">
gate: <passed|skipped>
---
Open your ## IP Review section with one italic line, *<skill name> · <ISO timestamp> · gate: <passed|skipped>* (your skill name is legal-ip-review).
End your section with ### Decisions and ### Open questions (one level under your ## IP Review heading, so the section stays one block), in this shape:
### Decisions
- <what was chosen> — <why> — <what was rejected>
### Open questions
- <what the next phase or a reviewer must settle>