Setup — install ProductOS and adopt your plan

ProductOS lives inside your app's repository, and this skill is how it gets installed there — the first thing to run after receiving your copy. It wires the repo, and if your copy came from your coach it carries your custom programme inside: setup moves that plan to docs/PLAN.md, where every ProductOS skill expects it.

Session shape: minutes, not a meeting. The only files this skill writes are the root CLAUDE.md/AGENTS.md, .gitignore, and docs/PLAN.md (moved from the seed). All checks are idempotent — re-running costs seconds and fixes whatever drifted.

Workflow

1. Verify the repo

Check that this folder is productos/ inside a git repository (git rev-parse --is-inside-work-tree from the parent). If ProductOS is checked out standalone — no surrounding repo — pause and set it up: help the user create (or pick) the app repo, git init it if new, and move this folder into it as productos/ exactly. From scratch is no exception; the repo exists before the product does.

2. Wire the root guidelines

The app repo root needs the coding-agent guidelines from productos/setup/:

• Root CLAUDE.md/AGENTS.md don't exist → copy them from productos/setup/ whole.
• The repo already has them → never overwrite. Append only the <!-- BEGIN PRODUCTOS -->…<!-- END PRODUCTOS --> block from the setup templates, plus one pointer line to productos/setup/CLAUDE.md for the full guidelines. If the markers are already present, replace the block between them.