sdd-plan-auditlisted

# Plan SDD audit An `architectural-analysis` report becomes **workstreams**: each workstream is an SDD feature in `tasks/prd-[slug]/`, executable by `sdd-orchestrate-tasks`. Contracts and tasks are written by the owning skills; this skill slices, delegates, and maintains the **destination map**, which links each finding to the workstream and task that resolves it. The report is immutable and no code is changed. 1. **Fix the report.** Resolve `.audits/architectural-analysis-[timestamp].md` by argument; without one, use the most recent by timestamp and report the choice. An argument that does not resolve while other reports exist: list them and request a choice. With no report at all, stop without writing anything and tell the user to run `architectural-analysis`, which only they invoke. Read the resolved report once. Look for the map `.audits/architectural-analysis-[timestamp].destinations.md`: if it exists, reuse IDs, workstreams, and states, and change it only with `--update`. Locate `sdd-plan-refactoring`, `sdd-create-prd`, `sdd-create-techspec`, and `sdd-plan-tasks` in the installed catalog or `SKILLS/`. A missing skill blocks only the route that depends on it. **Output:** exact report, previous map reconciled, and each route's skills located; or a stop with no files written and the missing report reported. 2. **Inventory findings.** Walk the five dimensions — dead code, duplication, anti-patterns, types and nullability, smells — by content, not by headings: real r