scaffold-kickoff

Scaffold a full repo by initiating a kickoff flow that classifies your run type, generates a canonical brief, and routes to downstream skills for template generation and handoff. It handles greenfield, retrofit, pivot, managed repair, and diagnosis scenarios.

Yes, you can retrofit the OpenCode operating layer into an existing repository by triggering a retrofit run type. The kickoff flow classifies the scenario, applies batched decision handling, and automatically routes to the appropriate downstream skills for integration.

Pivoting midstream changes during repo scaffolding is handled by classifying the run as a pivot scenario. The orchestrator applies a batched decision protocol to ensure traceability and routes to downstream skills for predictable handoffs.

Scaffold-kickoff works for diagnosing ongoing work by classifying the run as a diagnosis or review scenario. It enforces a batched decision protocol before handing control to downstream skills to repair workflows or assess the repository state.

No dependencies are required to start the repo scaffolding workflow. The skill operates independently as the single public entrypoint, applying a batched decision protocol and canonical brief generation before routing to downstream skills.

The kickoff flow uses a batched decision protocol to ensure traceability and predictable handoffs to downstream skills. It classifies the run type and generates a canonical brief before routing, preventing unmanaged changes during repo scaffolding.