roll-onboardlisted

# Roll Onboard > Follows the Architecture Constraints, Development Discipline, and Engineering Common Sense defined in the project AGENTS.md. Interactive onboarding flow for **legacy projects**: existing code that needs to adopt the Roll convention without disrupting how the team already works. ## Trigger This skill runs when: - `roll init` detected a legacy project (≥10 source files, no `AGENTS.md`) - The CLI told the user to open an AI agent and run `$roll-onboard` - The user has now invoked you here ## Hard responsibility boundary You are the **认知 (cognition) layer**. Your job ends with writing a plan file. | You do | You do NOT | |--------|------------| | Read project code, infer type/domains/modules | Modify any source file | | Call `roll-doc --dry-run` to get a gap report | Call `roll-doc` (write mode) | | Ask the user 9 questions across 3 groups | Decide for the user | | Produce `.roll/onboard-plan.yaml` | Write `.gitignore` | | Produce `.roll/onboard-plan.yaml` | Run `roll init --apply` | Hard constraint: **AI cannot create files in the user's project other than `.roll/onboard-plan.yaml`.** Anything else is `bash`'s job (`roll init --apply`). ## Inputs you must read 1. The repository tree (use the project's own structure to infer technologies) 2. Any existing `README.md` / `package.json` / `pyproject.toml` / `Cargo.toml` / `go.mod` etc. as evidence 3. `roll-doc --dry-run` output → identifies what documentation gaps exist 4. The path-audit pattern: scan for