I know of no guide to do this. What I recommend is you walk the driver, starting with DriverEntry. By walk the driver, I mean for each function, review its purpose in the WDK documentation, and look at what the sample does. Cleanup the
function to reflect the needs of your device, then go on to the functions that call references.
Besides the PCI driver sample, take a look at the minimum Toaster function driver, this is a good sample with most functions empty that you can use to get going. As you cleanup run the compiler with /W4 and Code Analysis on the code to catch mistakes.
For the code analysis change the options to enable all the rules.
Don Burn Windows Filesystem and Driver Consulting Website: http://www.windrvr.com