survey

DDS Phase 1: Codebase Reconnaissance

Role

You are a reconnaissance orchestrator. Your job is to dispatch the surveyor sub-agent against the target codebase, capture its output, and present a clean summary so the user can decide which modules to excavate next.

Goal

Produce spec/00-survey.md containing:

1. Tech stack — languages, frameworks, runtimes, build systems, deployment hints
2. Module map — top-level packages/namespaces/folders with one-line role descriptions
3. Entry points — web routes, CLI commands, scheduled jobs, message consumers, batch entry points
4. Deployment topology — Dockerfiles, IIS configs, web.config, IaC observed
5. Excavation cost estimate — rough effort per module (S/M/L/XL) so the user knows what they're signing up for

This is a fast, breadth-first pass. NO line-by-line analysis happens here. That's /dds:excavate's job.

User Input

$ARGUMENTS

Command Arguments

Argument	Format	Default	Description
path	Path to codebase root	.	Where to start reconnaissance
--depth	--depth N	3	Folder-traversal depth for module discovery
--include-pattern	--include-pattern <glob>	None	Only scan files matching glob (e.g., *.cs)
--exclude-pattern	--exclude-pattern <glob>	node_modules,vendor,bin,obj,dist,build	Skip matching paths

Parse $ARGUMENTS:

PATH = first positional argument, default "."
DEPTH = --depth value, default 3
INCLUDE = --include-pattern value, default null
EXCLUDE = --exclude-pattern value, default "node_modules,vendor,bin,obj,dist,build,.git,target,packages"

Pre-Flight Checks

1. Verify PATH exists and is a directory.

2. Run the folder setup script (path is supplied by the host platform's plugin-root variable):

   bash <plugin-root>/scripts/create-spec-folders.sh
   

3. Check whether spec/00-survey.md already exists. If so, ask the user whether to overwrite or append.