vibe-graduate
Skill1 starsChanged 3 months agoMITView on GitHub
【Vibe→Studio】原型晋升 — 将 sandbox 原型迁入 src/ 并补齐 ADR/测试/规范 → 生产代码。当用户说「原型稳了/转正」时使用。
In this repository23 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- studio-arch-designSkill
- studio-discoverySkill
- studio-gate-checkSkill
- studio-project-scanSkill
- studio-reviewSkill
- studio-setup-stackSkill
- studio-sprint-kickoffSkill
- studio-summarize-archSkill
- usds-cost-reportSkill
- usds-debt-logSkill
- usds-micro-adrSkill
- usds-mode-switchSkill
- usds-onboardSkill
- usds-startSkill
- usds-updateSkill
- vibe-branchSkill
- vibe-checkSkill
- vibe-explain-backSkill
- vibe-prototypeSkill
- vibe-startSkill
- vibe-taste-reviewSkill
The file
Files
技能:原型晋升 (/vibe-graduate)
执行代理: delivery-manager (主导) + technical-architect + lead-developer + qa-lead
概述 (Summary)
将 sandbox/<name>/ 下经过验证的原型,正式迁移到 src/,同时补齐所有 Studio Mode 工程标准。
这是 Vibe Mode → Studio Mode 的唯一合法通道。
前置条件 (Preconditions)
sandbox/<name>/存在且可运行docs/specs/lite-spec.md存在docs/specs/intent-log.md中至少有 1 条continue判断(证明方向经过校准)- 用户明确请求晋升
工作流 (Workflow)
阶段 1:晋升评估 (Delivery Manager)
- 检查前置条件
- 用
ask_user确认晋升目标:- "这个原型将从探索性质变为可维护的正式模块"
- "所有 Vibe Mode 豁免的规则都将重新生效"
- "预计需要 X 轮迭代补齐工程标准"
- [继续晋升] [暂缓] [取消]
阶段 2:追认型 ADR (Technical Architect)
- 分析 sandbox 代码的实际技术选型
- 生成
docs/arch/ADR-<n>.md,追认设计决策 - 必须包含:背景、决策、权衡、替代方案 (参照
doc-standards.md) - 关联
docs/specs/lite-spec.md作为需求来源
阶段 3:迁移与补齐 (Lead Developer)
按顺序执行:
- 代码迁移:
sandbox/<name>/→src/<module>/ - 消除硬编码: 提取到 config / env
- 命名规范: 符合
global-standards.md - 拆分文件: 单文件 ≤ 300 行,单函数 ≤ 30 行
- 补齐文档: 所有导出 API 添加 JSDoc / Docstring
- 结构化错误处理: 符合
backend-api.md - 补齐测试: 在
tests/<module>/添加测试,符合test-conventions.md- 核心逻辑 100% 分支覆盖
- 每个函数至少 Happy Path + Error Path
阶段 4:质量门 (QA Lead)
- 执行
/studio-gate-check - 验证所有工程标准通过
- 若失败,回退到阶段 3
阶段 5:归档 (Delivery Manager)
- 移动
sandbox/<name>/→sandbox/archive/<name>-<date>/ - 更新
production/backlog.md:标记原始 vibe 任务已完成 - 关闭
docs/specs/intent-log.md的意图追踪
成功门控 (Success Gate)
src/<module>/存在且符合所有工程规则docs/arch/ADR-<n>.md已生成tests/<module>/覆盖率达标/studio-gate-check通过sandbox/archive/已归档production/backlog.md已更新
输出约束 (Output Budget)
[强制] 完成后返回主上下文只输出:
晋升完成: [name] 已从 sandbox 迁移到 src。
- 源码: src/[module]/
- 架构决策: docs/arch/ADR-[n].md
- 测试覆盖: [X]%
- 归档位置: sandbox/archive/[name]-[date]/
现已进入 Studio Mode 维护流程。失败处理
若晋升过程中发现原型根本不该晋升(架构不匹配、测试无法覆盖等):
- 回滚所有变更
- 追加"晋升失败分析"到
docs/specs/intent-log.md - 建议:继续保留 sandbox 状态 或 pivot 重做
协作路径
- 前置:
/vibe-check确认方向稳定 - 后续:进入常规 Studio Mode 流程(
/studio-sprint-kickoff//studio-review//studio-gate-check)
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

