init

/marc:init — opt-in onboarding & config scaffolding

You are running the mARC onboarding flow. Your job is to help the user turn a zero-config repo into one with a persistent, versioned team binding, so @techlead and the specialists stop relying on ephemeral session memory and read the repo's concrete facts from {{ agents_dir }}/team.toml (and optionally AGENTS.md) at the start of every session.

The one rule that overrides everything

Nothing is ever written silently. For every artifact you produce you MUST:

1. Discover / compose the exact content.
2. Show that exact content to the user (fenced, verbatim).
3. Ask for an explicit "yes" for that specific artifact.
4. Write only on that confirmation, to the path shown.

There are three independent, individually opt-in artifacts. The user may accept any subset (including none). Never bundle them into one confirmation. Never infer approval from silence or from a "yes" to a different artifact. If the user declines everything, the repo is left byte-for-byte unchanged and zero-config behavior is fully preserved.

Do not invent facts. Anything you cannot discover empirically becomes a clearly-marked TODO placeholder, never a guess.

---

Step 0 — Discover the repo facts at runtime (no hardcoded values)

Mirror the tech-lead skill's runtime-discovery pattern. Resolve values from gh against the checked-out repo; do not hardcode any org, repo slug, or project number in this flow.

Batch the probes into ONE block. Run all discovery in a single Bash invocation so onboarding doesn't fire a permission prompt per gh call (a dogfood run fired ~7). This block is read-only discovery — the Write confirmations below (steps 2-4 of the one rule) are the intentional safety gate and are NOT what we are reducing; every file write still stops for an explicit "yes".

# Where onboarding writes (the CONSUMING repo, not the plugin):
ROOT="${{{ project_dir_env }}:-$PWD}"

# --- ORG + REPO (from the checked-out repo) ---
GH_REPO="$(gh repo view --json nameWithOwner -q .nameWithOwner 2>/dev/null)"
GH_ORG="${GH_REPO%%/*}"

# --- PROJECT (v2) candidates for the org, if any ---
# Needs the `project` scope; if it errors with "missing required scopes", tell the
# user to run `gh auth refresh -s project,read:project` once, then retry. Do not
# fabricate a number — leave it as a TODO if it can't be read. LIST candidates
# (number + title); the guard below decides — never auto-pick .projects[0].
echo "== org/repo: ${GH_REPO:-<unresolved>} =="
gh project list --owner "$GH_ORG" --format json 2>/dev/null \
  | jq -r '.projects[] | "\(.number)\t\(.title)"'