arch-tech-speclisted

## DEPENDENCY RESOLUTION **Reference:** `.claude/skills/orchestrator/dependency-graph.yaml` **BLOCKS** (must exist — auto-invoke if missing): - `docs/ets/projects/{project-slug}/architecture/architecture-diagram.md` — Needed for system structure to inform NFRs and ADRs. **ENRICHES** (improves output — warn if missing): - `docs/ets/projects/{project-slug}/planning/prd.md` — Business requirements improve NFR target alignment. - `docs/ets/projects/{project-slug}/discovery/project-context.md` — Constraints inform NFR targets. **Resolution protocol:** 1. Read `dependency-graph.yaml` → `tech-spec.requires: [architecture-diagram]` 2. Check: does `architecture-diagram.md` exist, non-empty, not DRAFT? 3. If missing → auto-invoke `architecture-diagram` skill → wait → continue 4. Check ENRICHES → warn if missing, proceed ## ARTIFACT SAVE RULE **MANDATORY:** This skill MUST write its artifact to disk before declaring complete. 1. Verify target directory exists → create with `mkdir -p` if needed 2. Write the complete document using the Write tool to the exact path specified in Output Document Structure 3. Displaying content in chat is NOT saving — the file MUST exist on the filesystem 4. After writing, display the CLOSING SUMMARY with the saved path 5. Only THEN propose the next step **If the Write fails:** Report the error to the user. Do NOT proceed to the next skill. ## INTERACTION PROTOCOL This skill follows the ETUS interaction standard. Your role is a thinking partner, not