vibeflow

启动 VibeFlow 本地看板，实时查看阶段、功能、产物和最近事件。

查看 VibeFlow 项目当前状态（阶段、进度、待处理项）。

VibeFlow框架入口。运行 /vibeflow 开始新项目或继续现有工作流。

测试阶段的真实浏览器验证底座。用于页面交互、表单、路由、前端 API、视觉状态和运行时问题验证。优先使用 Playwright MCP 做真实交互验证，使用 Chrome DevTools MCP 做运行时诊断；MCP 不可用时回退到本地 Playwright CLI 脚本。

在此仓库中用于在会话开始时路由整个VibeFlow生命周期的工作。

系统测试通过后且工作流要求 UI QA 时使用 — 运行浏览器导向的 QA 验证并生成报告

所有活跃功能通过且全局审查完成后使用 — 发布前运行全面系统测试，对齐 IEEE 829 和 ISTQB

以审批通过的 brief 为输入产出架构/设计文档，回答 HOW。内置问题探索（absorbed from brainstorming）— 当问题不清晰时在设计前先厘清。

独立学习流。用于陌生领域学习、研究文章写作、把资料变成输出。提供 Deep Research / Quick Reference / Write to Learn 三种模式，按 Collect -> Digest -> Outline -> Fill In -> Refine -> Publish 六阶段推进。

SRS 文档不存在且无设计文档时使用 — 通过结构化追问产出高质量需求规格说明书，对齐 ISO/IEC/IEEE 29148

Refreshes docs/overview architecture context for an existing codebase (Python + TypeScript)

维护 `docs/overview/` 轻量 RepoWiki 层，负责中文标准格式、生成区块保护、局部刷新和 freshness 检查。

YC Office Hours — two modes. Startup mode: six forcing questions that expose demand reality, status quo, desperate specificity, narrowest wedge, observation, and future-fit. Builder mode: design thinking brainstorming for side projects, hackathons, learning, and open source. Saves a design doc. Use when asked to "brainstorm this", "I have an idea", "help me think through this", "office hours", "is this worth building". Proactively suggest when the user describes a new product idea or is exploring whether something is worth building — before any code is written. Use before /vibeflow-plan-value-review or /vibeflow-plan-eng-review.

Spark 阶段 — 灵感迸发。默认先用 office-hours 做问题框定，把方向、边界、验收标准和约束想清楚；完成总结并经用户确认后再进入 Design。

在 tasks 审批通过后使用，基于设计契约生成 feature-list.json 并准备进入 Build

feature-list.json 存在且部分功能仍失败时使用 — 驱动功能通过完整 TDD 管线、质量门禁和代码审查

Think 阶段的深度调研引擎。系统性地分析 GitHub 同领域高星项目的 能力分布、技术栈、产品护城河，输出结构化竞品分析报告，为差异化创新提供情报支持。 使用场景：用户启动新项目前的竞品调研、需要了解同类项目技术选型、 寻找差异化机会点、识别竞品护城河。

Designer's eye plan review for VibeFlow — interactive review. Rates each design dimension 0-10, explains what would make it a 10, then fixes the plan to get there. Works in plan mode. Use when asked to "review the design plan", "design critique", or when a plan with UI/UX components is ready for design scrutiny. Proactively suggest when the user has a plan with UI/UX components that should be reviewed before implementation.

Engineering manager-mode plan review for VibeFlow. Lock in the execution plan — architecture, data flow, diagrams, edge cases, test coverage, performance. Walks through issues interactively with opinionated recommendations. Use when asked to "review the architecture", "engineering review", "lock in the plan", or when a plan is ready for technical scrutiny. Proactively suggest when the user has a plan or design doc and is about to start coding — to catch architecture issues before implementation.

Plan 阶段第一步 — CEO/Founder 视角的商业价值评估

TDD 循环后使用 — 强制覆盖率门禁、变异测试门禁和新鲜验证证据，方可标记功能为通过

Quick Mode for VibeFlow. Use when the work is small, bounded, low-risk, and easy to verify or roll back.

发布后使用 — 创建回顾、总结经验教训、生成下一迭代输入

所有活跃功能通过后使用 — 在最终测试和发布前运行全变更审查

Spark 阶段可选的圆桌会议 — 通过多角色独立观点对齐形成共识。 在深度洞察后使用，帮助用户在设计前充分考量各方视角。 使用场景：用户希望从多个角色视角审视方向、需要在团队内部形成设计共识。

Tasks 阶段 — 基于 spark brief 与 design 产出 execution-grade tasks.md，作为 Build 的正式交接输入。

独立生成 UCD 风格指南（视觉风格、Token、组件/页面提示词）。已并入 vibeflow-design 的步骤 1；此 skill 作为可选独立入口保留。

质量门禁通过后使用 — 独立管理测试环境生命周期，执行黑盒验收测试，生成 ISO/IEC/IEEE 29119 合规测试用例文档

VibeFlow 构建阶段的 Red-Green-Refactor 步骤 — 强制测试先行开发

Brainstorming Ideas Into Designs for VibeFlow. Must use before any creative work — creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation. Use when asked to "brainstorm this", "help me design this", "think through this", or when a design needs exploration before technical specification.

VibeFlow safety guardrails for destructive commands. Warns before rm -rf, DROP TABLE, force-push, git reset --hard, kubectl delete, and similar destructive operations. User can override each warning. Use when touching prod, debugging live systems, or working in a shared environment. Use when asked to "be careful", "safety mode", "prod mode", "careful mode", or "/vibeflow-careful". **This skill is optional and defaults to OFF.** Activate it explicitly when needed.

VibeFlow file edit boundary. Restricts Edit and Write operations to a specific directory for the session. Blocks edits outside the allowed path. Use when debugging to prevent accidentally "fixing" unrelated code, or when you want to scope changes to one module. Use when asked to "freeze", "restrict edits", "only edit this folder", "lock down edits", or "/vibeflow-freeze". **This skill is optional and defaults to OFF.** Activate it explicitly when needed.

VibeFlow full safety mode: destructive command warnings + directory-scoped edits. Combines /vibeflow-careful (warns before rm -rf, DROP TABLE, force-push, etc.) with /vibeflow-freeze (blocks edits outside a specified directory). Use for maximum safety when touching prod or debugging live systems. Use when asked to "guard mode", "full safety", "lock it down", "maximum safety", or "/vibeflow-guard". **This skill is optional and defaults to OFF.** Activate it explicitly when needed.

清除 freeze-dir.txt 边界文件，解除 Edit/Write 操作限制。解除后可恢复全局编辑权限。

测试通过后使用 — 准备发布工件、版本管理和发布输出

每个功能质量门禁通过后使用 — 运行规格与设计合规审查，确保实现匹配审批通过的规格、设计、计划和 UCD