self-tracklisted

# myna-self-track If vault_path is not in context, read `~/.myna/config.yaml` first. If the file does not exist, tell the user to run `/myna:setup` and stop. Logs your contributions and lets you query them. Log what you did; query it later by category, project, or date range. ## 📋 Before You Start Read at session start: - `_system/config/workspace.yaml` — for `user.name` and `user.role` (determines contribution categories) - `_system/config/projects.yaml` — for cross-referencing project-level impact **Contributions log path:** `Journal/contributions-{YYYY-W\d\d}.md` (ISO week, e.g. `contributions-2026-W18.md`). --- ## 📂 Contribution Categories Five universal categories — role-agnostic. A junior IC and a VP both log in the same buckets. - `delivery` — things you built, shipped, or completed: features, designs, documents, processes - `decisions` — calls you made when a direction was needed: architecture, scope, escalations resolved - `feedback` — developmental input you gave to others: code reviews, written feedback, growth conversations - `people` — helping, growing, or unblocking others: mentoring, coaching, unblocking teammates, onboarding - `quality` — making things more reliable, maintainable, or efficient: documentation, process improvements, risk mitigation, issue prevention --- ## ✍️ Log Contribution **Trigger:** "log contribution: [description]", "I just [did something worth logging]" **Entry format** (content-first, newest-first within the week): ``` -