メニュー
Manage ENAC Background IP inventory and carve-out language. Use for contracts, IP ownership clauses, methodology protection, prompt or agent IP, deliverables, and Background IP schedule updates.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | background-ip-schedule |
| description | Manage ENAC Background IP inventory and carve-out language. Use for contracts, IP ownership clauses, methodology protection, prompt or agent IP, deliverables, and Background IP schedule updates. |
ENAC's intellectual property is the firm's core asset. The methodologies, frameworks, agents, prompts, and tools that ENAC has developed over years of work are what make every engagement possible. The Background IP Schedule is the legal instrument that protects them.
Background IP is all intellectual property created before or independent of a specific client engagement. It includes everything ENAC brings to the table regardless of who the client is.
Includes:
Does not include:
This is the authoritative list. Update after every engagement where new methodologies, agents, or frameworks are developed. Attach this inventory as Exhibit [X] to every government contract.
presentation-narrative-arc skill)slide-copywriting and proposal-slide-copywriting skills)pablo-presentation-voice skill)proposal-response skill)client-brief-analysis skill)alignment-document skill)case-study skill)testimonial-builder skill)narrative-workflow skill).claude/commands/.claude/skills/: the rules, frameworks, and guidance that govern how ENAC workspcopilot): Python CLI for content workbench operationsThis is the exact language to insert in every government contract and professional services agreement. Insert in the IP/deliverables section. Do not accept IP assignment language without this carve-out.
Full version (preferred):
"Contractor retains all right, title, and interest in and to its pre-existing intellectual property, methodologies, frameworks, templates, tools, prompts, and know-how ('Background IP'), including any improvements, modifications, or derivatives thereof developed during the engagement. For purposes of this Agreement, 'Background IP' means all intellectual property owned or controlled by Contractor prior to or independent of this Agreement, including but not limited to the items listed in the Background IP Schedule attached hereto as Exhibit [X], and any updates or improvements thereto. Contractor grants County a perpetual, royalty-free, non-exclusive, non-transferable license to use Background IP solely to the extent embedded in the final deliverables specifically identified in the Statement of Work for County's internal business purposes only. Final deliverables specifically prepared for and delivered to County ('Foreground IP') are owned by County, excluding Background IP incorporated therein. Contractor may use de-identified findings, learnings, and methodological improvements for portfolio, case study, and marketing purposes, subject to the confidentiality provisions herein."
Short version (use when full version is rejected: minimum acceptable):
"Contractor retains ownership of its pre-existing methodologies, frameworks, tools, and know-how ('Background IP'). County receives a non-exclusive license to use Background IP as embedded in the final deliverables for County's internal purposes. Final deliverables (excluding Background IP) are owned by County."
If the short version is also rejected: Walk away. Any IP assignment without a Background IP carve-out is a walk-away issue. Escalate to human counsel.
Any improvement or modification to ENAC's Background IP that occurs during a client engagement belongs to ENAC, not the client.
Why: ENAC's methodology pre-existed the engagement. A better version of that methodology, developed while applying it to a specific client's problem, is still ENAC's methodology. The client paid for the output (the deliverable), not for ownership of ENAC's intellectual evolution.
Practical example: If ENAC develops a refined version of the client brief framework while working on an Adams County engagement, that refinement is ENAC's Background IP. The client received the deliverable that used the refined framework: they did not receive ownership of the framework.
Required action: After every engagement, identify any methodological improvements and capture them in the skills repository. Update the Background IP Schedule to include the new or refined item.
For AI prompts, agent definitions, and proprietary workflows to qualify for trade secret protection, ENAC must take reasonable steps to protect them:
colorado-government-contracting skill)Colorado trade secret definition (C.R.S. 7-74-102): Information that: (a) derives independent economic value from not being generally known or readily ascertainable; and (b) is subject to reasonable efforts to maintain its secrecy.
ENAC's methodologies, agent definitions, and prompt libraries meet this definition. The reasonable efforts requirement is met by following the protection steps above.
The Background IP Schedule is a living document. Update it after every engagement.
After every engagement, check:
If yes to any: add the new item to the Background IP Schedule inventory above, create or update the relevant skill file, and document the development in the engagement's work product record.
Why this matters: The Background IP Schedule attached to a contract protects only the items listed on it. If a new framework developed in a prior engagement is not on the schedule when you sign the next contract, that framework is not explicitly protected. Keep the schedule current.
Every contractor and subcontractor must:
UI Designer for software interfaces. Use for visual direction, hierarchy, typography, color, spacing, component composition, design systems, visual critique, and making an interface feel intentional before UI implementation.
UX Designer for software workflows. Use for interaction design, task flows, information architecture, page states, usability, accessibility flow, form behavior, empty/loading/error/success states, and making a service concept usable before visual design or implementation.
Use when you need the Codex Copilot equivalent of Claude Copilot /update-project: refresh a project-local Codex Copilot setup from the shared framework.
Use when you need specialist role guidance for architecture, engineering, QA, security, docs, devops, service design, UX, UI design, UI implementation, or industrial design in a Codex session or delegated subagent.
Use when you need the Codex Copilot equivalent of Claude Copilot /config: inspect or explain cc configuration, known references, paths, and environment hydration.
Use when you want to invoke codex-copilot specialist agents natively in Codex, either by selecting the right specialist skill for the main session or by mapping specialists onto real Codex spawned-agent roles for delegated work.