vibe-blueprintlisted

# Vibe Blueprint ## Purpose Turn validated planning and research into a high-level system design that is coherent, scoped appropriately, and ready for deeper technical detail. This skill exists to define the system shape before implementation begins. It should clarify: - the major components of the system - what the system is responsible for - what is outside system responsibility - how the core flows are expected to work - how success and behavior can later be measured - whether the project needs explicit event architecture before detail design continues ## When to Use Use this skill when: - planning has been completed - research has been completed - the project has a trusted problem statement and scope - major assumptions and visible risks have been surfaced - the system is ready to move from intent into high-level design ## When Not to Use Do not use this skill when: - no trusted project state exists - planning is incomplete - research is incomplete - the request is only to inspect status or resume context - the system is still relying on invisible or unsupported assumptions - the project is already in detail design or QA and no blueprint revision was explicitly requested ## Required Context Minimum required context: - problem statement - scope - success definition - research summary - risk register - assumptions log Helpful optional context: - constraints - preferred stack - prior decisions - domain-specific requirements - delivery limits If required conte