# Research Non Compete Enforceability Colorado > Guides the analyst in producing a comprehensive advisory memorandum on non-compete enforceability under the applicable Colorado framework, including choice-of-law analysis, statutory prerequisites, and consideration adequacy assessment. - Skill: `finchipaiorg/research-non-compete-enforceability-colorado` (Agent Skill) - Install (CLI): `npx skillmds@latest add finchipaiorg/research-non-compete-enforceability-colorado` - Raw SKILL.md: https://api.skillmd.com/api/skills/finchipaiorg/research-non-compete-enforceability-colorado/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Research & Search - Author: FinchipAIOrg (https://skillmd.com/u/finchipaiorg) - Updated: 2026-09-22 - Page: https://skillmd.com/skills/finchipaiorg/research-non-compete-enforceability-colorado --- # Skill: Research Non-Compete Enforceability Under Colorado Law ## 1. Subject-matter triage - Identify the controlling state-law framework before doing any reasonableness analysis. - Determine whether the agreement is governed by Colorado law, whether a contractual choice-of-law clause is displaced by a mandatory Colorado rule, and whether the relevant restraint is a non-compete, non-solicit, garden-leave, confidentiality, or invention-assignment provision. - If the record contains more than one potentially relevant restraint or more than one governing-law candidate, enumerate each item separately before analysis and state which provisions are within the scope of the memo. - If there is only one agreement and one covered individual, say so affirmatively and proceed on that basis. ## 2. Failure modes the skill is correcting - Analyst applies an outdated common-law reasonableness test without first identifying the controlling statutory framework and its enforceability prerequisites. - Analyst treats a contractual governing-law clause as dispositive without separately testing for a Colorado mandatory override for work performed primarily in Colorado. - Analyst assumes garden leave or similar continued-pay language creates enforceable consideration without checking whether it is actually promised, definite, and tied to the restraint period. - Analyst overlooks notice, disclosure, and attorney-consultation timing requirements that can independently affect enforceability. - Analyst states a bottom-line conclusion without naming the statute, section, or doctrine supporting it. - Analyst gives a legal conclusion without mapping it to the agreement’s actual terms, the employee’s role or pay structure, and the relevant statutory exception. - Analyst blurs enforceability with equitable discretion; statutory compliance must be analyzed first, then any equitable overlay separately. - Analyst fails to distinguish between complete invalidity, partial invalidity, and possible reformation or blue-penciling under the controlling forum’s law. ## 3. Legal frameworks / domain conventions that apply - Governing statute first: identify the current Colorado statute governing restrictive covenants and the specific subsection that addresses employee non-competes, exceptions, and procedural conditions. - Presumptive voidness: start from the statute’s baseline rule that restrictive covenants are unenforceable unless the employer proves an applicable exception and compliance with statutory prerequisites. - Coverage and exceptions: test whether the restricted person falls within a statutory category that may permit a non-compete, using the person’s role, compensation, and the nature of the protected interest. - Notice and disclosure: analyze any statutory advance-notice requirement, including timing, form, and any required advisement of the right to seek legal counsel, with attention to the actual signing timeline. - Choice-of-law override: if a contract selects another state’s law, analyze whether Colorado’s mandatory public policy for work primarily performed in Colorado displaces that selection for non-compete enforcement. - Consideration: assess whether the restraint is supported by consideration recognized under the controlling statute and whether any promised benefit is definite, binding, and temporally linked to the restriction. - Tailoring and scope: evaluate duration, geography, activity restrictions, and protected interests against the statute’s narrow-tailoring requirement and any express limits on what may be restricted. - Reformation and severability: explain whether the forum permits narrowing, severing, or refusing to enforce overbroad language, and what happens if the covenant does not fit within a statutory exception. - Equitable overlay: separately note any factual assertions, resignation conduct, or credibility issues that might matter to injunctive relief without letting them substitute for statutory analysis. ## 4. Analytical scaffolds - Framework statement: open with the controlling statute, its operative standard, and the enforcement posture it creates. - Scope of review: identify the agreement, the covered person, the relevant job changes, and any competing governing-law provision. - Threshold analysis: determine whether the individual is within a statutory class that can be restrained; if not, stop and state unenforceability under the statute. - Notice and timing analysis: check the date of offer, disclosure, acceptance, and signature against any statutory timing rule. - Consideration analysis: identify the specific consideration given for the restraint and test whether it is real, definite, and legally sufficient under Colorado law. - Scope analysis: test temporal, geographic, and activity restrictions against the statutory text and the employer’s stated interest. - Reformation analysis: assess whether any overbreadth can be cured or instead defeats enforcement under the controlling rule. - Equitable overlay: discuss any separate factual equities only after the statutory analysis is complete. - Bottom-line assessment: conclude with an enforceability view, litigation risk, and negotiation or remedial steps. ## 5. Vertical / structural / temporal relationships - If multiple restraints exist in the same agreement, analyze each restraint separately and then state how they interact. - If the agreement was signed, amended, renewed, or triggered on multiple dates, analyze each relevant date in sequence and tie statutory notice or consideration to the operative date. - If the employee moved roles, changed compensation, or relocated work into or out of Colorado, analyze the timing of each change against the covenant’s applicability. - If the agreement cross-references another document for notice, equity, or consideration, follow that chain and confirm the referenced document actually supplies what the covenant needs. - If there are multiple jurisdictions in play, separate the analysis by forum and governing-law candidate before drawing the conclusion. ## 6. Output structure conventions - Write as a comprehensive advisory memorandum with the enforceability conclusion stated at the outset. - Use conventional memo headings: governing law; statutory standard; threshold/coverage; notice and disclosure; consideration; scope and tailoring; reformation/severability; equitable considerations; conclusion; recommended actions. - Include a short table summarizing each statutory element: Requirement | Status | Consequence. - Cite the controlling authority for every legal proposition by name and section or other pinpoint authority. - Keep the analysis tied to the actual facts, document language, and operative dates; do not drift into abstract doctrine. - End with a Recommended Actions section that gives concrete next steps, assigns them to counsel or the relevant business owner where appropriate, and ties them to the litigation or transaction timeline. - If a statutory prerequisite is missing, say so directly and explain the practical consequence rather than softening the conclusion. - If the deliverable involves only advisory analysis, do not format it as a checklist of generic law; make it a decision-oriented memo that can guide action.