Landscape Site Analysis Drafter

intent

converts site data and field observations into a draft landscape site analysis report aligned to standard pre-design practice. the analysis structures inventory findings into a clear opportunities-and-constraints matrix that feeds schematic design decisions. all output is a draft, the signing registered landscape architect must verify field conditions, confirm regulatory requirements with the AHJ, and seal the document before client presentation or submission. use this skill at the outset of any landscape architecture project when you need to systematize site reading before schematic design begins.

inputs

required data sources:

• project name, location (city, state, parcel ID or address), and approximate site area (acres or SF)
• project type (urban park, residential garden, corporate campus, streetscape, ecological restoration, school grounds, mixed-use development)
• project phase (feasibility, schematic, design development) to calibrate analysis depth
• client goals, program priorities, and stated aesthetic direction

external connections and data:

• USDA NRCS Web Soil Survey (public, no auth required, online query at websoilsurvey.sc.egov.usda.gov)
• FEMA Flood Insurance Rate Map (FIRM) panels (public, no auth required, query.fema.gov)
• local municipal GIS portals (varies by jurisdiction, typically public)
• USDA Plant Hardiness Zone database (public, no auth required)
• local zoning codes and AHJ contact information (planning department, building department)
• title report or county assessor records (may require client to provide or public record request)

optional data the user may already have:

• survey drawings or CAD files
• soils report or geotech investigation
• aerial imagery (Google Earth, county orthophoto, drone imagery)
• existing site plans or engineering drawings
• environmental assessment or wetland study
• utility records or 811 one-call response

context and constraints:

• this skill assumes the user has site access or can document field conditions through field visits or photos. if only desktop research is available, flag that clearly.
• all regulatory requirements (setbacks, buffer widths, zoning overlays) must be verified by the LA with the local AHJ and title report. this skill cannot substitute for jurisdiction-specific due diligence.
• any geotechnical or wetland delineation findings require licensed consultant sign-off and are out of scope for this skill.

procedure

step 1: project intake (conversational, one question at a time)

ask each question below sequentially. do not present the full list at once. wait for the user's answer before proceeding to the next question.

1. project name and location (city, state, general address or parcel ID)
2. site area (approximate acreage or square footage)
3. project type (e.g., urban park, residential garden, corporate campus, streetscape, ecological restoration, school grounds, mixed-use development)
4. project phase (feasibility, schematic, design development, construction documents)
5. client goals and program priorities (key uses, aesthetic direction, sustainability targets)
6. data already available (survey, soils report, aerial imagery, municipal GIS, existing drawings, environmental studies)
7. known regulatory constraints (jurisdiction, zoning district, ADA requirements, special overlays already identified)

output: completed intake form with project parameters and initial data inventory.

---

step 2: physical site inventory (nine sub-steps, flag data gaps explicitly)

2A: topography and grading

collect:

• high and low points, general slope gradient and aspect (north-facing, south-facing, etc.)
• significant grade changes, ridgelines, swales
• existing grading constraints (retaining walls, slopes >3:1, drainage patterns)

if user has no data: flag as "topography: requires field survey or aerial contours."

output: topographic summary narrative (2-3 sentences) or data gap note.

---

2B: soils and geology

collect:

• USDA NRCS Web Soil Survey map units if available (ask user to note map unit symbols and names)
• soil texture, drainage class, depth to seasonal high water table (if available from soils report)
• any known contamination, fill areas, or geotechnical concerns

decision point: if user reports potential contamination or unstable soil: note "geotechnical engineer referral required" in data gaps. do not make bearing capacity or slope stability findings.

if user has no data: flag as "soils and geology: requires USDA Web Soil Survey query or soils report by licensed geotech."

output: soils summary narrative (2-3 sentences), map unit identification, or data gap note.

---

2C: hydrology and drainage

collect:

• watershed context and drainage patterns (sheet flow direction, swales, detention areas)
• 100-year and 10-year floodplain presence (FEMA FIRM panel number if known)
• wetlands, streams, riparian buffers, stormwater infrastructure
• existing impervious surface area estimate (percent of site)

decision point: if user reports wetland indicators (standing water, hydrophytic vegetation, saturated soils): flag as "wetland delineation by licensed wetland scientist required before design." do not delineate or make jurisdictional calls.

decision point: if site is in FEMA floodplain: note floodplain elevation, zone (AE, X, etc.), and flag "confirm 100-year and 10-year floodplain boundaries and design standards with AHJ and FEMA FIRM."

if user has no data: flag as "hydrology: requires FEMA FIRM query, field walk to assess drainage patterns, and wetland delineation if indicated."

output: hydrology summary narrative (3-4 sentences), floodplain zone and elevation, or data gap note.

---

2D: existing vegetation

collect:

• tree canopy coverage and notable specimen trees (species, approximate DBH, condition rating: good, fair, poor)
• invasive species presence and coverage percentage
• groundcover, shrub layer, meadow, or turf areas
• existing vegetation to be preserved vs. removed (client and design intent)

if user has no data: flag as "vegetation inventory: requires field walk and tree survey (species, DBH, condition, location)."

output: vegetation summary narrative (3-4 sentences), notable tree list, or data gap note.

---

step 3: microclimate analysis

collect:

• USDA Plant Hardiness Zone (query planthardiness.ars.usda.gov with latitude/longitude)
• average annual extreme minimum temperature
• average first and last frost dates for the site location
• prevailing wind direction(s), seasonal variations if known
• solar access: describe shading from existing buildings, trees, or topography; cardinal orientation of site
• heat island factors (urban paving, building mass, proximity to water bodies)
• precipitation: annual average, wet/dry season pattern

if user has no data: flag as "microclimate: requires USDA hardiness zone lookup and weather station query (NOAA, local NWS office)."

output: microclimate summary narrative (4-5 sentences) with USDA zone, prevailing winds, solar orientation, and frost/heat notes, or data gap note.

---

step 4: visual and contextual analysis

collect:

• views from the site (views to keep/enhance: vistas, landmarks, water bodies) and views into the site (views to screen/frame: unsightly adjacencies, noise sources)
• adjacencies: surrounding land uses, building types, street conditions, pedestrian and bicycle connections
• noise and odor sources: traffic corridors, mechanical equipment, refuse areas, industrial uses
• cultural and historic features: existing structures, memorials, public art, heritage trees, archaeological sensitivity
• character and identity: architectural context, neighborhood character, client-stated aesthetic direction

if user has limited site familiarity: flag as "visual and contextual: requires site visit and photo documentation."

output: visual and contextual summary narrative (4-5 sentences) with view analysis, adjacency description, and character notes, or data gap note.

---

step 5: regulatory inventory

collect and cross-reference with title report and AHJ:

• zoning classification and applicable setbacks (front, rear, side)
• easements: utility, drainage, access, conservation (from title report or GIS if available)
• wetland and stream buffers: jurisdiction-specific buffer widths
• ADA / accessibility requirements: applicable standard (ADA, PROWAG, local code)
• utility corridors: overhead lines, underground utilities (note 811 one-call relevance)
• special overlays: historic district, flood zone, wildland-urban interface, stormwater management district, tree protection ordinance

decision point: if any regulatory item is uncertain or not yet verified: flag as "verify with AHJ before design."

if user has no data: flag as "regulatory inventory: requires zoning code query, title report, municipal GIS review, and AHJ consultation."

output: regulatory summary table or narrative (3-4 sentences), list of items requiring AHJ verification, or data gap note.

---

step 6: opportunities-and-constraints matrix

synthesize inventory findings from steps 2-5 into a two-column matrix. for each site feature or condition, classify it as:

• opportunity: asset to design toward
• constraint: limitation to work around
• both: dual-use condition

example rows:

Feature / Condition	Classification	Notes
South-facing slope	Opportunity	Solar access for passive heating, native plantings
FEMA 100-yr floodplain edge	Constraint	No occupied structures; design for wet-tolerant planting
Mature oak grove	Both	Preserve canopy; limits grading within drip line

aim for 10-20 matrix entries covering topography, soils, hydrology, vegetation, microclimate, views, adjacencies, and regulatory items.

output: completed opportunities-and-constraints matrix.

---

step 7: design program recommendations

derive 4-8 evidence-based recommendations directly from the opportunities-and-constraints synthesis. each recommendation must trace to an inventory finding or constraint.

use action verbs:

• "orient primary circulation to maximize solar access and views of..."
• "locate active uses on south-facing slope to..."
• "screen the northern edge from traffic noise using..."
• "preserve all trees with DBH >12" within the drip line to..."
• "design bioretention swales along the existing drainage spine to..."

note sustainability strategies supported by site conditions (bioretention, passive solar, wind buffering, native planting zones).

output: numbered list of 4-8 design program recommendations (2-3 sentences each).

---

step 8: data gap list

enumerate all items flagged as data gaps during the inventory (steps 1-5):

• items requiring field verification before design decisions are finalized
• specialty consultants needed (wetland scientist, geotechnical engineer, environmental consultant, cultural-resource specialist, arborist)
• regulatory items requiring AHJ confirmation

output: bulleted list of data gaps and consultant referrals.

---

step 9: assemble and present draft report

compile the full site analysis report using the output format below, clearly labeled DRAFT , FOR REGISTERED LA REVIEW. include the review block at the bottom with signature and stamp lines.

output: complete site analysis report as PDF or formatted text document.

---

decision points

if user reports geotechnical concerns (slope stability, retaining wall design, soil bearing capacity):

• do not make structural or geotechnical findings. require the user to engage a licensed geotechnical engineer before design development.

if user reports wetland indicators (standing water, hydrophytic vegetation, saturated soils, hydric soils):

• do not delineate wetlands or make jurisdictional determinations. flag all potential wetland indicators and require a licensed wetland scientist to perform formal delineation and Army Corps of Engineers jurisdictional determination.

if site is located in a known floodplain (FEMA zone AE, A, AO, X, etc.):

• note the FEMA FIRM zone and elevation. direct the LA to confirm design standards and freeboard requirements with the AHJ and local floodplain administrator.

if user has no field access or has only desktop data:

• clearly label all findings as "desktop research only" and flag that field verification is mandatory before design. do not present desktop-only analysis as field-verified.

if user lacks regulatory data (zoning, easements, overlays):

• do not assume or infer regulatory requirements. flag "requires AHJ verification" and require the user to consult the zoning code, title report, and municipal GIS before proceeding to design.

if user reports historical or archaeological sensitivity:

• flag "cultural resources: requires archaeological assessment and consultation with State Historic Preservation Office (SHPO) and Tribal authorities if applicable."

if user reports endangered species or critical habitat:

• flag "biological resources: requires U.S. Fish and Wildlife Service and state wildlife agency consultation if federally listed species are present or suspected."

output contract

deliverable: one formatted landscape site analysis report document (PDF or text) containing all nine sections below.

file location: user specifies (typically saved to project folder on user's system or shared drive).

data format:

• narrative text (2-5 sentences per section)
• one opportunities-and-constraints matrix (table format, min. 10 rows)
• one design program recommendations list (numbered 1-8, 2-3 sentences per item)
• one data gaps and specialist referrals list (bulleted)
• one review block with signature, date, and stamp fields

document must include:

• project title, location, site area, project type, date prepared
• all nine sections: project summary, physical inventory (2A-2D), microclimate, visual/contextual, regulatory, O&C matrix, design program, data gaps, review block
• warning label: "DRAFT ONLY , Do not present to client or submit to any authority without registered landscape architect review, field verification, and professional seal."
• prepared-with-AI-assistance note in review block

regulatory compliance: all items flagged "verify with AHJ" must be confirmed by the LA before the report is signed and sealed. no report should be sealed or presented without field verification of all physical site conditions and AHJ confirmation of all regulatory requirements.

outcome signal

the user knows the skill worked when:

1. intake is complete: the user has answered all seven intake questions and confirmed project parameters.

2. inventory is systematic: the user has data for each of steps 2-5 (physical inventory, microclimate, visual/contextual, regulatory) or has clear data gap flags for items requiring field verification or consultant input.

3. matrix is populated: the opportunities-and-constraints matrix contains 10-20 entries and each entry clearly links a site condition to a design implication (opportunity, constraint, or both).

4. recommendations are evidence-based: each of the 4-8 design program recommendations traces back to a specific entry in the O&C matrix or inventory finding, not to generic design preference.

5. data gaps are explicit: every gap (missing survey, no soils report, wetland potential unverified, regulatory items unconfirmed) is listed by name with the consultant or source needed to fill it.

6. report is draft-labeled: the document clearly states "DRAFT , FOR REGISTERED LA REVIEW" and includes the review block with signature, license number, firm, and professional stamp fields.

7. no assumptions passed as findings: the LA can hand the report to their own consultant team or client with confidence that every assertion is either field-verified, data-sourced, or flagged as a gap or assumption requiring verification.

8. regulatory items are flagged: all zoning, buffer, easement, and overlay items that rely on local code or title report are marked "verify with AHJ" and the user is directed to consult the planning department and title report before finalizing design.

---

original author: archlab-space. enriched and standardized to Implexa quality guidelines.

feedback: if you have an unmet need or this skill does not cover your design workflow, open an issue at https://github.com/archlab-space/Open-Skill-Hub/issues.