菜单
Phase-boundary checkpoint and ratchet review for VibeOS in Codex. Use when the user says phase is done, milestone check, checkpoint this phase, or wants a boundary audit before starting the next phase.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Full audit cycle that dispatches audit agents (security, architecture, correctness, test quality, evidence, product drift, flow, system invariants, dependency intelligence, delivery infrastructure, red team, contract validator), applies consensus logic, and produces a composite report with actionable findings. Use when the user says "audit the code", "review everything", "check for security issues", "do a full review", or wants a comprehensive multi-perspective code review.
Autonomous build orchestrator that executes work orders end-to-end. Use when the user says "continue", "keep going", "build the next thing", "resume", "start building", or wants to make progress on the development plan. Dispatches investigator, tester, prompt-engineering, implementation, and documentation agents in sequence with two-layer quality enforcement (Layer 1 gates + Layer 2 audit agents) and error recovery, while checking for product drift and stale high-impact decisions.
VibeOS audit flow for Codex. Use when the user asks for a code audit, quality review, governance review, architecture review, security review, or wants a full audit cycle before or after implementation work.
Full autonomous-session override for VibeOS in Codex. Use when the user says go autonomous, stop checking in, run on your own, stay in autonomous mode, or wants VibeOS to keep building until a real blocker or decision appears.
Autonomous VibeOS work-order execution for Codex. Use when the user says continue, resume, keep going, build the next thing, start implementing, or wants progress against the current VibeOS plan.
Compact enterprise MVP mission intake for VibOS Comp. Use for competition-grade builds, enterprise design-partner MVPs, rapid production-quality prototypes, battle harness runs, or explicit VibOS Comp/VibeOS Comp requests.
| name | vibeos-checkpoint |
| description | Phase-boundary checkpoint and ratchet review for VibeOS in Codex. Use when the user says phase is done, milestone check, checkpoint this phase, or wants a boundary audit before starting the next phase. |
Use this skill at phase boundaries.
docs/planning/DEVELOPMENT-PLAN.md and determine the target phase.if grep -q '"long_run"' ".vibeos/config.json" 2>/dev/null; then
python3 ".vibeos/scripts/autonomy-heartbeat.py" --status checkpoint --summary "phase checkpoint started" --next-action "run full checkpoint gates and audits"
fi
bash ".vibeos/scripts/gate-runner.sh" pre_commit --continue-on-failure
bash ".vibeos/scripts/gate-runner.sh" full_audit --continue-on-failure
.codex/agent-contracts/*auditor*.md as role contracts and execute the checkpoint review yourself. Include dependency intelligence review for any phase that changed manifests, lockfiles, package managers, runtimes, SDKs, frameworks, or high-impact packages. Include delivery infrastructure review for any phase that changed CI/CD, deployment, environment/secrets, observability, health/smoke checks, rollback, runbooks, or operational scripts..vibeos/baselines/ exists.