[Verizon Samsung Galaxy S III] notta:
Yeah CM pretty much just sets everything up for you!

I wrote this up while waiting on my uploads so hopefully this will help you and possibly some others.

Copy all of below into a text document then save as REPO_LOCATION/.repo/local_manifests/d2vzw.xml

<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="CyanogenMod/android_kernel_samsung_d2" path="kernel/samsung/d2" remote="github" revision="cm-11.0" />
<project name="CyanogenMod/android_device_samsung_qcom-common" path="device/samsung/qcom-common" remote="github" revision="cm-11.0" />
<project name="CyanogenMod/android_device_samsung_msm8960-common" path="device/samsung/msm8960-common" remote="github" revision="cm-11.0" />
<project name="CyanogenMod/android_device_samsung_d2vzw" path="device/samsung/d2vzw" remote="github" revision="cm-11.0" />
<project name="CyanogenMod/android_device_samsung_d2-common" path="device/samsung/d2-common" remote="github" revision="cm-11.0" />
<project name="CyanogenMod/android_hardware_samsung" path="hardware/samsung" remote="github" revision="cm-11.0" />
<project name="CyanogenMod/android_hardware_qcom_sensors" path="hardware/qcom/sensors" remote="github" revision="cm-11.0" />
<project name="CyanogenMod/android_hardware_qcom_media-caf" path="hardware/qcom/media-caf" remote="github" revision="cm-11.0" />
<project name="CyanogenMod/android_hardware_qcom_media" path="hardware/qcom/media" remote="github" revision="cm-11.0" />
<project name="CyanogenMod/android_hardware_qcom_keymaster" path="hardware/qcom/keymaster" remote="github" revision="cm-11.0" />
<project name="CyanogenMod/android_hardware_qcom_gps" path="hardware/qcom/gps" remote="github" revision="cm-11.0" />
<project name="CyanogenMod/android_hardware_qcom_display-caf" path="hardware/qcom/display-caf" remote="github" revision="cm-11.0" />
<project name="CyanogenMod/android_hardware_qcom_display" path="hardware/qcom/display" remote="github" revision="cm-11.0" />
<project name="CyanogenMod/android_hardware_qcom_audio-caf" path="hardware/qcom/audio-caf" remote="github" revision="cm-11.0" />
<project name="TheMuppets/proprietary_vendor_samsung" path="vendor/samsung" remote="github" revision="cm-11.0" />
</manifest>

Below is a generic pa_d2vzw makefile. Copy and save to vendor/pa/products/pa_d2vzw.mk

# Copyright (C) 2012-2013 ParanoidAndroid Project
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.

# Check for target product
ifeq (pa_d2vzw,$(TARGET_PRODUCT))

# Define PA bootanimation size
PARANOID_BOOTANIMATION_NAME := XHDPI

# OVERLAY_TARGET adds overlay asset source
OVERLAY_TARGET := pa_xhdpi

# Build paprefs from sources
PREFS_FROM_SOURCE ?= false

# Include AOSPA common configuration
include vendor/pa/main.mk

# Inherit device configuration
$(call inherit-product, device/samsung/d2vzw/full_d2vzw.mk)

# Inherit telephony common stuff
$(call inherit-product, vendor/pa/configs/telephony.mk)

# Override AOSP build properties
PRODUCT_NAME := pa_d2vzw
PRODUCT_BRAND := Samsung
PRODUCT_MODEL := SCH-I535
PRODUCT_MANUFACTURER := Samsung
PRODUCT_BUILD_PROP_OVERRIDES += PRODUCT_NAME=d2vzw TARGET_DEVICE=d2vzw BUILD_FINGERPRINT="Verizon/d2vzw/d2vzw:4.1.2/JZO54K/I535VRBMF1:user/release-keys" PRIVATE_BUILD_DESC="d2vzw-user 4.1.2 JZO54K I535VRBMF1 release-keys"

endif

Update vendor/pa/products/AndroidProducts.mk with below

ifeq (pa_d2vzw,$(TARGET_PRODUCT))
PRODUCT_MAKEFILES += $(LOCAL_DIR)/pa_d2vzw.mk
endif

Update vendor/pa/vendorsetup.sh

add_lunch_combo pa_d2vzw-userdebug

Then you can run ./rom-build.sh d2vzw and hopefully depending on your hardware which can be anywhere from 30 minutes upward you will have a succesfull build. Using CM trees you will come across some of the overlays that don't have established parameters. As the errors come up the build will explain to you whats going on if you look. Simply follow those errors and remove the corresponding lines. You can delete the line or hide it by putting it inside of <!-- HERE --> for the xml's.

Hopefully this helps you out and if you run across something just ask. :)