vibe-initlisted

# Vibe Init ## Purpose Initialize a new Vibe Driven Dev project journey with the minimum required context. This skill exists to establish a valid starting state before the system enters planning. It should create the initial project state, capture the minimum execution context, and make the next step explicit. ## When to Use Use this skill when: - a new Vibe Driven Dev workflow is being started - no trusted project state exists yet - the user wants to begin a structured journey from idea to execution readiness - the system needs to initialize project-local orchestration state ## When Not to Use Do not use this skill when: - a trusted project state already exists and the user intends to continue from it - the user is resuming an interrupted workflow - the request is only to inspect status or read existing state - the system is already inside an active stage and no reset was explicitly requested ## Required Context Minimum required context: - target platform or environment - intended user or audience - success definition Optional context may include: - project identifier - stated constraints - preferred stack - early non-goals If the minimum context is missing, the skill must halt or request clarification through the orchestration layer. ## Assumptions Rules This skill may proceed with limited assumptions only when they do not create hidden safety, privacy, or feasibility risk. Allowed assumptions: - a default local project id when none is supplied - a neutra