Setup (tobico skills)

Owns the per-project git-workflow conventions the tobico skills read. Everything lives in one committed file, docs/agents/git-workflow.md, with one section per convention:

• ## Branch naming — the feature-branch pattern (read by /to-tasks)
• ## Review process — how a finished feature branch is landed (read by /next-task)

Sections are filled on demand: a section counts as configured only when it has real content, not just a heading.

Asking questions

Whenever you put a question to the user — a convention menu, the handle prompt, or an ad-hoc question when something is unclear — ask it and wait for their answer before carrying on. See the menu note below for how this applies to the convention menus.

Invocation

• Directly (/setup-tobico-skills) — proactive full setup: walk every section, showing the current value where one exists and offering keep-or-change, and write the complete file.
• Scoped (delegated by another skill) — configure only the section that skill named (branch-naming or review-process), then return so the caller continues. This is the normal path; /to-tasks and /next-task invoke it when their section is missing.

Determine the scope from how you were invoked. If a caller named a section, do only that one. A bare direct invocation does all sections.