What problem does it solve? Setting up a new development toolkit in an existing project is often confusing: users do not know what the tool writes locally, what data it logs, or where to start. This Skill runs a structured, seven-step first session that discloses local usage logging before anything is written, proposes real starter tasks found in the actual codebase, and never writes anything without an explicit yes. ## Core Features & Use Cases - Transparent disclosure: Explains the local usage log at .marvin/usage/events.jsonl, what it contains, and offers an opt-out that edits .marvin/config.json only after showing the exact lines to be written. - Repository-aware starter tasks: Scans source, manifests, and documentation for genuine candidates (missing tests, stale README claims, dated TODOs, outdated dependencies) with file:line evidence. - Delegated side effects: Creates at most one task board card via /marvin:track-new and one commit via /marvin:commit, each behind explicit consent, with no branches or pushes. - Use Case: A developer just installed the marvin plugin and types "walk me through marvin" — the Skill reads the repo, discloses logging, proposes three real tasks, and ends with one concrete next command. ## Quick Start Ask the assistant to walk you through marvin in this project, for example by saying "I just installed marvin, set it up here".
