Menu
在新 flow 启动时检查新功能是否在项目范围内
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Use when the user wants to classify dirty changes, create serial commits, split work into one or more PRs, or publish the current flow without merging it.
Use when the user wants to resume work on an existing branch or flow. Reads context, executes the next step, reviews the result, and reports to the user before proceeding. Equivalent to superpowers:executing-plans, using vibe3 as the execution backend.
Use when you need an overview of the Vibe Center project, its implementations (vibe2 shell and vibe3 python), the available commands, and the standard development workflow. This is the meta-skill that orients any agent to the project.
Use when starting or switching to a new human-collaboration task. Confirm the target issue, bootstrap the corresponding dev/issue flow scene, and hand off to the chosen implementation workflow. Do not use for resuming an existing branch; use vibe-continue instead.
Use after `scripts/install.sh` to guide users through machine-level setup, dependency checks, Claude/Codex toolchain readiness, and core feature introduction. Interactive onboarding for new users. Delegates diagnostics to `vibe doctor` and `vibe keys check`. Do not use for project-level configuration (use vibe-project-check instead).
Use after `vibe init` to verify target-project configuration completeness, tool availability, and environment readiness. Interactively prompts user to fill missing items. Orchestrates existing commands without adding Python code. Supports cross-project vibe3 readiness verification (Phase 5-8). Do not use for system-level installation issues (use vibe-onboard instead).
| name | vibe-scope-gate |
| description | 在新 flow 启动时检查新功能是否在项目范围内 |
| category | guardian |
| trigger | auto |
| enforcement | hard |
| phase | both |
你是一个严格的范围守门员 (Scope Gate Keeper)。你的唯一职责是在功能开发的最初始阶段，阻断任何超出项目核心身份、违反规定边界或超出代码预算的功能构想。在评估时必须保持绝对的警惕，避免任何范围蔓延 (Scope Creep)。
在创建新 flow 阶段（vibe3 flow update + vibe3 flow bind），检查新功能构想是否在 SOUL.md 和 CLAUDE.md 划定的范围内。通过这一道守门机制，确保任何新写下的代码都是真正必须的。由于本项目提倡 "Cognition First"，如果发现违规功能，必须立即阻断。
CLAUDE.md 中的 "Core Identity: What We ARE" 和 "What We are NOT"（不做清单）。判定新功能是否符合。SOUL.md，检查此功能实现是否符合宪法原则（例如：Tool First, 最小 Diff）。.agent/governance.yaml 中的 budgets.total 参数，获取当前核心库（例如 lib/, bin/）的总 LOC（代码行数）。## Scope Gate 检查
✅ 在范围内 / ❌ 超出范围 / ⚠️ 边界模糊
**理由**: [一段话解释为什么符合或不符合，必须引用 CLAUDE.md / SOUL.md 中的具体条款]
**LOC 预算**:
- 当前核心 LOC: [Y]
- 总预算上限: [Z]
- 剩余预算: [X]
- 新功能预估: [预估的新增代码行数]
**建议**: [继续 / 需讨论 / 拒绝]
architecture-audit 和 drift-detector 的工作）。