setup-pi-conductorlisted

Set up Pi Conductor for repositories by configuring global conductor config, repo .pi/WORKFLOW.md, GitHub Projects v2 mapping, workflow prompts, launch rules, and worktree hooks. Use when user asks to set up, bootstrap, initialize, configure, repair, or explain Pi Conductor, conductor workflow files, ready-for-agent automation, project dispatch, or worktree hook setup for a repo.
shekohex/dotai · ★ 10 · AI & Automation · score 60

Install: claude install-skill shekohex/dotai

# Setup Pi Conductor Set up current repository so `pi conductor` can turn GitHub Project issues into isolated Pi worktree sessions. Preserve existing config; do not overwrite local preferences or repo workflow policy without inspecting them first. ## Artifacts - Global user config: `~/.pi/agent/conductor/config.json`, plus `config.schema.json`. - Repo workflow policy: `<repo>/.pi/WORKFLOW.md`, committed when repo-owned policy changes are desired. - Private local hooks: `<repo>/.git/config` keys named `pi.conductor.hook.<phase>`, never committed. ## Process 1. Scope the repo. Find git root, current remote, default branch, package/test commands, README/CONTRIBUTING guidance, and any existing `.pi/WORKFLOW.md`. If this is a monorepo and target repo/app is ambiguous, ask which checkout/unit should be managed. 2. Discover GitHub context. Run `gh auth status`, `gh repo view --json owner,name,defaultBranchRef`, and inspect available Projects v2 with `gh project list --owner <owner>` or `gh project view <number> --owner <owner>` when project info is missing. 3. Gather preferences only where defaults are not obvious. Use one grouped `ask_user_question` call for choices that change files: dispatch label, project owner/number, field names/options, launch modes, Follow-Up Rules, Conductor Comments, shared/private hooks, webhook vs polling, and whether to run a live dispatch. 4. Initialize safely. Run `pi conductor config init` from the target repo. It is idempotent: it migrates conf