vibe-planlisted

# Vibe Plan ## Purpose Turn vague intent into a clear project framing that the rest of the Vibe Driven Dev journey can build on. This skill defines: - the actual problem worth solving - who the project is for - what is in scope - what is out of scope - what success means - what would make the effort not worth continuing ## When to Use Use this skill when: - the project has been initialized successfully - the user has an idea, direction, or product ambition but it is still fuzzy - the system needs to turn freeform intent into structured planning truth - the next step depends on a reliable problem statement and scope boundary ## When Not to Use Do not use this skill when: - no valid project state exists yet - the workflow is still in an uninitialized state - the task is only to inspect status or resume context - the project already has a trusted planning artifact and the user is not intentionally revisiting planning - the request is purely implementation-focused with no problem framing at all ## Required Context Minimum required context: - target user - problem context - success definition Helpful optional context: - constraints - early non-goals - preferred stack - business context - timeline sensitivity If the required context is weak, the skill should either surface assumptions explicitly or halt through the orchestration layer. ## Assumptions Rules This skill may make limited assumptions only when they do not distort core scope or project truth. Allowed as