investigate-directorylisted

# Investigate Directory Skill **Primary output:** A plain-language description of what the directory actually does — derived from its file tree, content, and project context — so the caller understands its real purpose, not just its label. **Secondary output:** An assessment of code quality signals (naming consistency, test coverage, dead files, convention adherence) and how well the directory serves the project's pillar(s) — not just which pillars apply, but whether the implementation lives up to them. **This skill is read-only — it never modifies files or creates tasks.** ## Step 0: Start Cost Tracking ```bash tusk skill-run start investigate-directory ``` Capture `run_id` from the output — needed in Step 6. > **Early-exit cleanup:** If any check below causes the skill to stop before Step 6 (e.g., the user never provides a directory in Step 1, the resolved path does not exist, or `tusk setup` / `tusk pillars list` fails), first call `tusk skill-run cancel <run_id>` to close the open row, then stop. Otherwise the row lingers as `(open)` in `tusk skill-run list` forever. ## Step 1: Capture the Directory Argument The user provides a directory path after `/investigate-directory`. It may be: - An absolute path (e.g., `/Users/me/project/src/auth`) - A path relative to the project root (e.g., `src/auth`, `skills/tusk`) If no argument was provided, ask: > Which directory should I investigate? Provide a path relative to the project root (e.g., `src/auth`) or an absolute pa