Summary

Closes #163. Defaults the split-portfolio sibling repo name to <fork>-portfolio (e.g. your-org/apexyard-portfolio for the canonical fork name). The previous default — your-org/ops plus a bare portfolio/ directory — was too generic: adopters running multiple ops setups hit naming collisions, and a bare portfolio/ dir gives no signal about which framework it belongs to.

The new default makes the relationship to the public fork self-documenting on disk and on GitHub. If the fork is renamed (your-org/cos, your-org/apex), the portfolio defaults to cos-portfolio / apex-portfolio. Adopters who picked a different name keep working — the portfolio: config block resolves whatever path they configured.

Mechanism unchanged. This is a default-suggestion + example-prose update only.

Files changed

• docs/multi-project.md — split-portfolio layout diagrams, setup walkthrough, config-block / symlink examples, daily-workflow cd commands, cross-machine clone command. The two remaining your-org/ops references at lines 52 + 64 are FORK-rename examples (renaming the fork itself); those stay valid (renaming a fork to ops would just produce ops-portfolio for the sibling, still self-documenting).
• .claude/skills/setup/SKILL.md — Step 2b's "default suggestion" for the private repo name is now your-org/<fork>-portfolio, computed dynamically via gh repo view --json name -q .name so the suggestion stays correct even when the fork was renamed. Clone command drops the second arg (repo name IS the directory name now).
• .claude/skills/split-portfolio/SKILL.md — Step 3's suggested-name template is now <account>/<fork>-portfolio with the same dynamic-fork-name resolution.

Testing

• Grep verification — grep -rn "your-org/ops" docs/ .claude/skills/ returns only the two intentional FORK-rename examples (docs/multi-project.md:52, :64, docs/getting-started.md:20). No prose references to your-org/ops remain in the split-portfolio walkthrough.
• Path consistency — grep -rn "../portfolio/" docs/ .claude/skills/ returns 0 matches. All split-portfolio config-block / symlink examples use ../apexyard-portfolio/.
• AgDR-0010 unchanged — historical decision record reference to "ops-fork" is generic terminology (the framework fork's role), not a name; kept as-is.
• apexyard.projects.yaml.example unchanged — uses "ops repo" as generic terminology for the framework fork; not a name.
• Visual review of the rendered docs (manual) — confirm the layout diagrams + walkthrough flow read cleanly with the new naming.

Glossary

🤖 Generated with Claude Code