What problem does it solve? Driver specs written from source code quickly become unverifiable: nobody can check whether a claim matches the code, and the spec silently goes stale when the code moves. This Skill produces implementation specs where every source-derived fact carries a file:line anchor at a pinned commit, so reviewers can check the spec against the tree and drift is mechanically detectable. ## Core Features & Use Cases - Anchored spec authoring: Defines an anchor grammar ([src:], [tgt:], [doc:]) plus hardware-vs-driver labels ([hw-required], [driver-choice], [as-implemented]) and a required 12-section spec structure covering register maps, init sequences, interrupts, DMA, and target-OS integration. - Mechanical verification: Ships anchor_check.py to resolve anchors at the pinned commit, render claim-by-claim review sheets, and detect or rewrite drift when the pin moves; inventory_check.py cross-checks the spec against register headers and device-tree nodes for omissions, value mismatches, and contradictions. - Orchestrated workflow: Provides fill-in templates for fan-out spec-drafting subagents and an independent verifier subagent that re-derives claims blind and recomputes counts and negative claims. - Use Case: You own a 2,400-line Ethernet MAC driver and need a spec another engineer can implement from. The Skill fans out investigators over the source, drafts a spec where every register offset and init step cites its defining lines, then verifies it mechanically and with an independent reviewer before landing it in docs/. ## Quick Start Ask the agent to produce a source-anchored implementation spec for a peripheral from your driver source tree, pinned at a specific commit, using the anchored-peripheral-spec skill.
