OpenOps-Studio/vibe-driven-dev
Skill Claude CodeCodex
Ground the project in evidence, visible risks, and explicit assumptions before blueprinting begins.
Agent-first framework for safe vibe coding. Turn messy product ideas into structured plans, bootstrap files, stack decisions, AI model choices, and handoff-ready workflows for coding agents.
OpenOps-Studio/vibe-driven-dev
Skill Claude CodeCodex
Ground the project in evidence, visible risks, and explicit assumptions before blueprinting begins.
OpenOps-Studio/vibe-driven-dev
Skill Claude CodeCodex
Resume a VDD journey from the latest trusted project state, prior handoff, and visible decisions without re-deriving context from scratch.
OpenOps-Studio/vibe-driven-dev
Skill Claude CodeCodex
Convert validated planning, architecture, and technical detail into repository bootstrap artifacts that downstream execution agents can build from without hallucinating.
OpenOps-Studio/vibe-driven-dev
Skill Claude CodeCodex
Summarize the current journey stage, active gates, handoff readiness, and next recommended command without mutating project state.
OpenOps-Studio/vibe-driven-dev
Skill Claude CodeCodex
Validates all raw external inputs (commands, configuration overrides) provided to the VDD runtime to prevent path traversal, prototype pollution, or injection.
OpenOps-Studio/vibe-driven-dev
Skill Claude CodeCodex
Evaluates product assumptions and plans for PII handling, user tracking, and data retention risks. Triggered during 'research' and 'blueprint' stages to enforce privacy-by-design.
OpenOps-Studio/vibe-driven-dev
Skill Claude CodeCodex
Verifies the structure, safety, and guardrails of system prompts generated within the project to prevent unintended behavior, hallucination, and prompt injection.
OpenOps-Studio/vibe-driven-dev
Skill Claude CodeCodex
Evaluates project artifacts and state for security risks. Triggered explicitly before the 'scaffold' and 'qa' stages to ensure no hardcoded secrets, unsafe dependency assumptions, or major architectural security flaws pass into execution.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: