ip-clean-room

Enforces clean-room implementation and dependency license review for outbound licensing compliance.

7|3|Updated Sep 23, 2025
One-click install
npx skills add https://github.com/islamu-ngo/Event --skill ip-clean-room-islamu-ngo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ip-clean-room
Source: https://github.com/islamu-ngo/Event/tree/main/.agents/skills/ip-clean-room
Command: npx skills add https://github.com/islamu-ngo/Event --skill ip-clean-room-islamu-ngo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It prevents intellectual property contamination when researching competitors, implementing features informed by external products, or adding dependencies whose licenses could block intended outbound distribution models. ## Core Features & Use Cases - Clean-Room Handoff Workflow: Defines how to observe external behavior, write sanitized functional specifications, and separate research from implementation contexts. - SSO/Provenance Review: Provides an Abstraction-Filtration-Comparison checklist to verify independent design of structure, sequence, and organization. - Dependency License Gate: Records license obligations per dependency and blocks components that conflict with intended outbound offerings, including the AutoMapper/MediatR dual-version precedent. - Use Case: Before implementing a feature inspired by a competitor's product, produce a source-free handoff with an audit record, then run the SSO review and dependency gate before merging the PR. ## Quick Start Load the ip-clean-room skill before researching a competitor's event platform feature and generate a sanitized implementation handoff with an audit record.

Frequently Asked Questions about ip-clean-room

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I implement a feature inspired by a competitor without copying code?▼

Observe only public behavior and documentation, write a sanitized functional specification with inputs, outputs, and constraints, then implement in a fresh context using repository-native design. Record the source register, attestation, and SSO review in an audit record linked to the PR.

What is a clean-room implementation workflow?▼

A clean-room workflow separates researchers who observe external behavior from implementers who receive only sanitized specifications. No third-party source, snippets, ASTs, or internal structure may enter the implementation context, and contamination triggers a documented restart procedure.

How do I check if a new dependency is license-compatible?▼

Record the component, version, license, and obligations for each intended outbound model, then run the validate-dependency-license-policy script as mandatory metadata evidence. Unknown terms, commercial contracts, or source-available licenses require separate human legal review.

Does a passing automated license scan prove legal compliance?▼

No. The scanner validates metadata policy only and is not legal certification. Commercial contracts, assembled distribution obligations, assets, and generated output still require documented human review and approval.

What happens if external source code enters the implementation context?▼

Stop immediately, discard unmerged output from that context, record the incident without reproducing the material, and assign an unexposed reviewer to recreate the specification. Implementation restarts in a fresh, source-free context.