setup-projectlisted

# Setup project Registering a project is a per-project act with a per-project lifetime. `setup-user` is a per-person act, run once. Keeping them in one skill meant every new repository cost a full personal-setup run, which is what this skill exists to end. **Slash-only on purpose.** It writes `daikenja.yaml`, and its seeding step can propose dozens of ledger entries. Nothing about "set this up" should make that fire on its own -- the user runs `/daikenja:setup-project` when they mean to. `disable-model-invocation: true` is set for that reason. **This skill never writes ledger content.** Seeding derives candidate entries and hands them to `/daikenja:project-log`, which shows the exact lines and waits for approval. `project-log` remains the only writer of a ledger, per `docs/config-writers.md` § Who writes what. ## Step 0: the preconditions Read `~/.claude/daikenja/daikenja.yaml`. Three outcomes and no others: - **It does not exist.** Stop. Say so and name the skill that creates it: ``` Daikenja is not configured yet -- there is no ~/.claude/daikenja/daikenja.yaml. Run /daikenja:setup-user first. Nothing was written. ``` - **It exists but does not parse.** **Stop.** Name the first line that does not parse. Never guess the intent and never rewrite a file you cannot parse -- the same rule every Daikenja skill follows. - **It exists but `profile.name` is unset or empty.** Stop. The configuration is incomplete, and `setup-user` is what completes it. Say so an