What problem does it solve? Creating a new project that reuses an existing repository's agent infrastructure, lint discipline, build shape, and architectural conventions normally requires manual, error-prone copying. This Skill automates the triage of what should travel versus what stays behind, then seeds the new repository with a reviewed structure. ## Core Features & Use Cases - Three-way triage: Sorts every path in the source repo into stack scaffolding, agent infrastructure, or product, deciding per path whether it travels as a copy, a rewrite, or stated architectural intent when stacks differ. - Watermark and lineage management: Writes the new repo's sync watermark pointing at the root template, carrying the caller's lastSyncedSha and lineage array so future syncs compose correctly. - Reviewed seeding split: Lands already-reviewed copies on main and routes all rewrites through a draft PR, so the new repo passes through the same reviewed adoption path as any other project. - Use Case: You have a mature Next.js project with a working agent loop and want to start a sibling project in Python. Invoke /spinoff owner/new-repo, and the Skill carries the architectural decisions as intent, seeds main with the agent loop, and opens a draft PR with the rewritten foundation. ## Quick Start Invoke the skill by typing /spinoff owner/new-repo-name in a session rooted in the adopter repository, then answer the prompts about visibility and target stack.
