What problem does it solve? Writing a from-scratch driver for a differently-licensed OS from encumbered source code creates legal contamination risk. This Skill produces a clean-room implementation spec per peripheral, with an enforced transfer protocol, independent verification, leak scanning, and a provenance ledger so the process is evidentiary and defensible. ## Core Features & Use Cases - Structured spec generation: Produces a two-half spec (hardware facts with provenance tags, plus target-OS integration with file:line citations) covering register maps, init sequences, interrupts, DMA, and milestones. - Transfer protocol and verification gate: Spec text is written by a delegated subagent to a scratch path and only lands in docs/ after a fresh independent verifier subagent returns PASS, keeping unverified text out of the orchestrator. - Evidentiary provenance: Maintains a provenance ledger with content hashes, scan reports, and a spec-gap protocol so implementers never need to read the original source. - Use Case: Porting a DWC3 USB controller driver from Linux to Fuchsia — delegate the spec to a subagent, verify it against the pinned kernel commit, land it in docs/, and let implementers write Rust code from the spec alone. ## Quick Start Ask the agent to produce a clean-room implementation spec for a specific peripheral, naming the IP block, target OS, and board, and let it orchestrate the subagent and verifier workflow.
