add-contextlisted

# /add-context One entry point for adding context. Reads the input, classifies it (transcript / doc / note / chat), and routes to the existing writer skill. **Scope (v0.2):** thin router only. The four `/ctx-*` writers stay as they are. Downstream UX alignment + frontmatter standardisation tracked separately (T2.5, T2.6). --- ## Invocation shapes ``` /add-context <file-path> /add-context <file-path> -- <hint> /add-context # then prompt for content /add-context --type <transcript|doc|note|chat> <file-path> ``` - **`<file-path>`** preferred over pasted content. Pasted content sits in the conversation window and is expensive for long files. If the user pastes a long block, suggest they save it to a file first. - **`-- <hint>`** is anything after a literal `--` separator. Fed into the classifier as a hint. - **`--type X`** hard override. Skips classification, logs `override=true` in telemetry. --- ## Step 1 — Resolve project Read the active project: 1. If your Claude Code session ID is in context (injected by the SessionStart hook), read `[workspace-root]/.sessions/<session-id>`. 2. Fall back to `[workspace-root]/.current-session` if the per-session file doesn't exist. 3. If neither exists or both are `(no project)`, stop and say: `No active project. Run /os-start to pick one, then re-run /add-context.` Look up the project in `projects.md` to get `PROJECT_ROOT`. For portfolios, parse left of ` / ` as portfolio name and use the portfolio roo