vibe-detaillisted

# Vibe Detail ## Purpose Turn a trusted high-level blueprint into execution-ready technical detail. This skill exists to bridge the gap between system shape and actual build preparation. It should define: - important technical constraints - core flows and logic details - what must be validated - what implementation caveats still matter - what remains risky before QA - and, when relevant, the concrete event catalog and event contracts that downstream execution must honor ## When to Use Use this skill when: - blueprinting has been completed - the project has trusted architecture artifacts - the system is ready to move from high-level design into actionable implementation detail - the next step depends on concrete technical and validation-oriented outputs ## When Not to Use Do not use this skill when: - no trusted project state exists - blueprinting is incomplete - the request is only to inspect status or resume context - the project is still missing planning or research truth - the system is attempting to jump directly from planning into technical detail - the workflow is already inside QA or handoff with no explicit detail revision request ## Required Context Minimum required context: - architecture baseline - system boundaries - analytics outline - problem statement - scope - assumptions log Helpful optional context: - preferred stack - prior decisions - technical constraints - delivery limits - runtime environment constraints If required context is missing, t