start

Collect project state and route new users to onboarding phases.

Updated Apr 24, 2026
One-click install
npx skills add https://github.com/rakhnianskii9/God-Godot --skill start-rakhnianskii9
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: start
Source: https://github.com/rakhnianskii9/God-Godot/tree/main/.github/skills/start
Command: npx skills add https://github.com/rakhnianskii9/God-Godot --skill start-rakhnianskii9

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

First-time onboarding can be confusing and time-consuming; this Skill asks key questions to understand the user's starting point and routes them to the most appropriate onboarding workflow, reducing setup friction.

Core Features & Use Cases

  • Guided onboarding flow that adapts to the user's state (no idea, vague idea, clear concept, or existing work).
  • Interactive decision routing using predefined phases to map next steps (Phase 1-5) and avoid assumptions.
  • Optional production review mode configuration and handoff to subsequent Skills for continued guidance.

Quick Start

Run the start skill to begin onboarding and be guided to the correct workflow.

Frequently Asked Questions about start

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up onboarding for a game dev project with existing design docs?

Onboarding for a game dev project with existing design docs routes you directly to the setup or production review phase. The workflow detects existing artifacts to skip initial discovery and map the next steps.

What is the best way to structure a user journey when I only have a vague project concept?

The best way to structure a user journey from a vague concept is through interactive decision routing. Guided setup asks key questions to assess your state and maps you to the appropriate discovery phase.

Can I configure workflow routing to skip phases if my engine and production artifacts already exist?

Yes, workflow routing adapts to your project state by skipping phases when engine and production artifacts exist. It collects your current state and routes you directly to the relevant setup or design phase.

How does guided onboarding handle decision points without auto-executing the next steps?

Guided onboarding handles decision points by using Phase-based prompts to determine and present the next steps without auto-execution. This ensures you retain manual control over the workflow progression.

Do I need a root SKILL.md file with YAML frontmatter to start the onboarding workflow?

Yes, the onboarding workflow requires a root SKILL.md file with name and description in YAML frontmatter. This file provides the necessary metadata for the skill to initiate the guided setup process.

Why does the onboarding workflow use predefined phases instead of a single setup script?

The onboarding workflow uses predefined phases to avoid assumptions and accurately map next steps based on your project state. This structured approach reduces setup friction compared to a single linear script.