[Epic]: Frictionless integration (<30m onboarding) into existing repos + robust new-project bootstrap (v1.0.0)

Stub Epic for v1.0.0 readiness (builds on #615).

Criteria

• Any existing repository can reach healthy PLATE state in under 30 minutes of (mostly automated) work
• Brand new projects are fully scaffolded with one command or template + zero manual steps beyond git push
• Includes full labels, wiki/Goals, SPEC/CURRENT, workflows, .plate config, bootstrap of initial Questions/Epics
• Safe payload import, conflict resolution, CI coexistence, health verification
• Guided or autonomous adoption that produces the first Q&A session automatically

Roadmap: #654
Related children: #615 (current payload import Epic), bootstrap research/design, new-repository-checklist.md, plate_bootstrap + plate_migrate.

Status: Stub; refine adoption metrics and success signals in follow-up.

PM-enabled <30m adoption stories (added per Q&A)

Story: PM-orchestrated bootstrap for brand new project (<15m to first Q&A)

1. User creates repo from template or runs gh plate bootstrap.
2. PM detects new repo, orchestrates full scaffold: template payload, .plate with low-risk autonomy, labels, wiki/Goals stub, initial Questions (value prop, users, risks) via curiosity sub-agent.
3. PM surfaces in feed: "Bootstrap complete. Initial Questions seeded. Ready for product planning Q&A? (est 5m)."
4. User starts Q&A; PM coordinates planner/researcher sub-agents.

Story: PM-guided adoption for existing mature repo (<30m)

1. User runs gh plate bootstrap --adopt on complex repo.
2. PM analyzes (health, CI conflicts), proposes plan via feed: "Safe import: 10m files + labels + .plate. Risk: medium (CI coexistence). Approve phases?"
3. PM uses simulation for risky steps, delegates import sub-agent, GitHub setup sub-agent, first Q&A bootstrap.
4. Checkpoints for human decisions (e.g., "Adopt driver:collaborative for core Epic?"). Webhooks keep real-time.
5. Ends with health green, feed with first Questions, transparent logs.

Adoption metrics via PM (proposed): Time to green health, % automated steps, first Q&A latency, budget used, driver label adoption post-bootstrap.

Specific Success Metrics / ACs for PM-enabled adoption (added per Q&A)

• New/greenfield projects: Full healthy PLATE state (labels, .plate, wiki/Goals, initial Questions in feed, health green) in <15 minutes; first Q&A session surfaced and started within 5 minutes of bootstrap complete.
• Existing/mature repos: Healthy state in <30 minutes (phased, with simulation for conflicts); includes safe CI coexistence, payload import without breaking existing workflows, and first Q&A feed item (e.g., product planning prompt) ready for user.
• Done signal: Health report green (all core files, labels, protection, .plate), feed populated with at least 3 seeded Questions/Tasks, driver labels set (e.g., collaborative for initial Epics), usage report logged, SPEC/Goals references updated.
• Metrics tracked by PM: wall-clock time, % steps automated (vs human checkpoint), post-adoption feed engagement (e.g., first answer within 1h), budget burn < expected for scope, % of driver labels matching vision (Epics collaborative, etc.).

PM in adoption edge cases (added per Q&A)

Story: Monorepo with complex structure
PM detects monorepo (multiple packages, shared CI). Uses specialized sub-agent for analysis. Proposes scoped import (e.g., only root + one package first). Simulation shows impact on shared workflows. Surfaces phased plan with checkpoints per sub-project. PM orchestrates parallel sub-agents for labels in subdirs if supported, or central .plate with extensions. Total <30m for core, with plan for full.

Story: Repo with pre-existing .plate or custom setup
PM detects existing .plate. Runs compatibility check (version, extensions). Proposes migration or merge (e.g., add autonomy section without overwriting). Uses import sub-agent with dry-run. If conflicts (e.g., custom labels), surfaces for human review via feed. Ensures first Q&A respects existing config.

Story: Existing CI conflicts (e.g., complex GitHub Actions)
PM scans CI. Identifies conflicts (e.g., PLATE workflows clashing with custom deploy). Uses simulation + conflict-resolution logic (from #615 learnings). Proposes coexistence (e.g., conditional jobs, separate dirs). Surfaces diff and risk in feed. On approve, PM applies changes, verifies with health post-import. Driver label set to collaborative for CI-related Epic.

Update this stub with more flows or ACs as Q&A continues.

Start with #615 and #654, then read the bootstrap research/design, new-repository-checklist.md, plate_bootstrap, and plate_migrate references. Map the existing-repository and new-project flows, including .plate, workflows, labels, health verification, and initial Questions. Done means the stated under-15-minute and under-30-minute adoption metrics and the green health, feed, and usage-report signals are defined and demonstrably met.