meridianscanlisted

# /meridian:scan — Codebase Audit & Work Discovery Analyze a codebase with parallel agents to discover issues, tech debt, and work items. Produces a prioritized audit report and optionally creates a milestone with phases/plans from findings. ## Arguments - `<focus>` — narrow scan to "security", "tests", "performance", "architecture", "deps", etc. - `--create-milestone` — auto-create milestone with phases from findings - `--milestone-name <name>` — custom milestone name (default: "Audit Remediation") ## Prerequisites - Project must be initialized with `/meridian:init` (`.meridian/state.db` exists) - Must be run from a project root with source code to analyze ## Procedure ### Step 1: Validate Project Confirm `.meridian/state.db` exists. If not, tell the user to run `/meridian:init` first. ```bash ls .meridian/state.db ``` ### Step 2: Prepare Audit Directory ```bash mkdir -p .meridian/audit ``` ### Step 3: Parse Arguments - If user provided `<focus>`, narrow all agents to that dimension only (spawn 1 agent instead of 4) - If `--create-milestone` is present, set flag to create milestone after aggregation - If `--milestone-name` is present, use that name; otherwise default to "Audit Remediation" ### Step 4: Launch Parallel Analysis Agents Spawn **4 agents in parallel** using the Agent tool. Each agent writes its findings to `.meridian/audit/`. If `<focus>` is set, only spawn the relevant agent. **IMPORTANT**: All agents must use the finding format defined below. Each