vibe-researchlisted

# Vibe Research ## Purpose Ground the project in visible evidence, alternatives, assumptions, and risks before high-level system design begins. This skill exists to reduce blind confidence. It should help the system understand: - what is already known - what is still uncertain - what risks are already visible - what assumptions require caution - what alternative directions may exist ## When to Use Use this skill when: - initialization and planning have already been completed - the project has a trusted problem statement and scope - the system is about to move toward blueprinting - assumptions and risks need to be surfaced before architecture choices begin ## When Not to Use Do not use this skill when: - no trusted project state exists - planning has not been completed - the request is only to inspect status or resume context - the project is already deep in implementation and the task is unrelated to research grounding - the workflow is attempting to skip problem framing entirely ## Required Context Minimum required context: - problem statement - scope - success definition Helpful optional context: - user constraints - prior assumptions - known alternatives - domain context - prior decisions - timeline pressure If the required context is incomplete, the skill should halt or surface assumptions explicitly instead of pretending confidence. ## Assumptions Rules This skill may use light assumptions only when they do not fabricate evidence or hide meaningful risk