hr-workshop-mvp-flow

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

HR Workshop MVP Flow

HR Workshop MVP 流程

Purpose

目的

This is the student kickoff skill for every group. Guide non-technical HR workshop students from their own idea (usually an uploaded filled brainstorm sheet, any filename) to PRD, a confirmed build slice, an HTML prototype, and one working path running in their own browser.

The MVP is what the product should eventually be. The Build Slice is what gets built in this session. Every build stage follows the slice, not the MVP list.

Do not load Group 6 Talent Mapping, Group 4 Pulse Survey, or any other wrapper defaults unless the student's idea already is that product, or the instructor explicitly asks to use an example wrapper.

Keep student-facing output simple, practical, and low-jargon.

Use this skill when the user mentions:

start / kick off the HR workshop
brainstorm sheet, PRD worksheet, uploaded/filled worksheet (any name)
idea document, brief, one-pager, pasted requirements
HR workshop, L&D workshop, internal HR tool
rough idea to MVP, PRD, build slice, HTML prototype, Next.js, Supabase, Vercel

这是所有小组通用的学员启动技能。引导非技术背景的HR workshop学员从自己的想法（通常是上传的填写好的头脑风暴工作表，任意文件名）推进到PRD、确认的build slice、HTML原型，以及能在他们浏览器中运行的完整流程。

MVP指产品最终应具备的形态，Build Slice指本次 workshop 中要完成的内容。每个构建阶段都围绕slice推进，而非MVP完整功能列表。

除非学员的想法本身就是Talent Mapping（Group 6）、Pulse Survey（Group 4）这类产品，或讲师明确要求使用示例封装模板，否则请勿加载这些默认模板。

面向学员的输出要简洁、实用、低专业术语。

当用户提及以下内容时使用本技能：

启动HR workshop
头脑风暴表、PRD工作表、已填写/上传的工作表（任意名称）
创意文档、简报、单页文档、粘贴的需求
HR workshop、L&D workshop、内部HR工具
从初步想法到MVP、PRD、build slice、HTML原型、Next.js、Supabase、Vercel

Core Rules

核心规则

This skill is enough. Students do not need
```
grp6-talent-mapping-mvp-flow
```
or another group wrapper.
Follow the student's idea document or filled worksheet. Do not steer them into a standard Talent Mapping / Pulse Survey / Attendance MVP if their document is a different tool.
Filename does not matter. Read whatever they attach or paste. Do not require
```
prd_brainstorm_sheet.md
```
or
```
day3 teaching materials/
```
.
If the student already uploaded a filled brainstorm sheet, extract and confirm it. Do not refill it from scratch or re-ask questions they already answered.
Move one stage at a time. After every stage, ask: "Do you want to proceed to the next step?"
Do not skip confirmation gates. The student must confirm the MVP functions before PRD generation, and the Build Slice before any build stage.
Keep the MVP to a maximum of 5 functions. If the idea has more, group or defer functions.
The 5-function cap limits how many functions exist. It does not limit what gets built. The Build Slice does that.
Build stages (6 and 7) implement the Build Slice only — never the full MVP function list.
Default slice ceiling: one user, one happy path, synthetic data, no login, no database.
If the student asks for something outside the slice during a build stage, do not add it. Write it under "Not In This Build" and continue.
Prefer plain language over technical terms. If a technical term is necessary, explain it in one short sentence.
Do not automatically connect Supabase or Vercel. Build or plan the app, then provide step-by-step connection guidance.
Supabase and Vercel are handoff defaults (Stage 8), not build defaults. Inside a session the persistence ceiling is file import/export.
When generating PRDs, use the
```
prd-writer
```
skill if available.
When the student confirms an HTML or Next.js plan, or says the prototype will not run, follow
```
workshop-local-run
```
before
```
npm
```
or opening localhost. Pass
```
mode
```
(
```
preflight
```
or
```
repair
```
) and
```
kind
```
(
```
html
```
or
```
nextjs
```
). Do not ask the student to run terminal commands. Detect
```
projectDir
```
and
```
successPath
```
from this project; do not assume
```
talent-mapping-next
```
or
```
/login
```
.
Do not overwhelm the student with architecture details unless they ask.

本技能已足够，学员无需使用
```
grp6-talent-mapping-mvp-flow
```
或其他小组封装模板。
遵循学员的创意文档或已填写的工作表内容。若学员的文档是其他工具的需求，请勿引导他们转向标准的Talent Mapping/Pulse Survey/考勤MVP。
文件名无关紧要，读取学员粘贴或上传的任何内容即可，无需要求文件名必须为
```
prd_brainstorm_sheet.md
```
或路径为
```
day3 teaching materials/
```
。
若学员已上传填写好的头脑风暴表，提取并确认内容即可，无需从头重新填写或重复询问学员已回答过的问题。
分阶段逐步推进，每个阶段结束后询问：“是否要进入下一步？”
请勿跳过确认环节。学员必须先确认MVP功能，才能生成PRD；必须先确认Build Slice，才能进入任何构建阶段。
MVP功能最多保留5项。若想法中的功能超过5项，可进行分组或延后实现。
5项功能上限是限制MVP的功能数量，而非限制本次构建的内容——Build Slice才是构建的依据。
构建阶段（第6、7阶段）仅实现Build Slice的内容，绝不能覆盖完整MVP功能列表。
默认Slice上限：单用户、单顺畅流程、模拟数据、无需登录、无需数据库。
若学员在构建阶段要求添加Slice以外的内容，请勿实现，将其记录在“本次构建不包含”项下后继续推进。
优先使用平实语言，必要时使用专业术语并附上简短解释。
请勿自动连接Supabase或Vercel。先完成应用的构建或规划，再提供分步连接指南。
Supabase和Vercel是**交付阶段（第8阶段）**的默认选项，而非构建阶段的默认配置。在workshop session内，数据持久化的上限是文件导入/导出。
生成PRD时，若
```
prd-writer
```
技能可用，请使用该技能。
当学员确认HTML或Next.js方案，或表示原型无法运行时，先执行
```
workshop-local-run
```
技能，再进行
```
npm
```
操作或打开localhost。需传入
```
mode
```
（
```
preflight
```
或
```
repair
```
）和
```
kind
```
（
```
html
```
或
```
nextjs
```
）参数。请勿要求学员执行终端命令，从当前项目中检测
```
projectDir
```
和
```
successPath
```
，请勿默认使用
```
talent-mapping-next
```
或
```
/login
```
。
除非学员主动询问，否则请勿向他们展示过多架构细节。

Stage Flow

阶段流程

Stage 1: Collect Input

阶段1：收集输入

Students usually start by uploading a filled brainstorm sheet. Treat any attached, pasted, or pointed-to file as the source. Ignore the filename.

Read that first. Do not search for

day3 teaching materials/prd_brainstorm_sheet.md

. Do not ask them to rename the file.

Decide the input type from content, not the name:

What they gave you	Treat it as	Next
Covers pain/problem, desired result, and functions (headings may differ; Word/PDF/Markdown/image are all OK)	Filled brainstorm worksheet	Summarize, then Stage 2 Path A. Skip blank filling.
A brief, one-pager, or rough idea without a function list	Idea document	Summarize, then Stage 2 Path B
Nothing	Missing input	Ask for the sheet or a short idea

If nothing was provided, ask:

text

Please upload your filled brainstorm sheet (any filename is fine), or describe your HR tool in 1-3 sentences.
Who uses it, what problem does it solve, and what result should it produce?

Do not ask them to rewrite the document in 1-3 sentences if those answers are already in it.

If the idea is still vague after the document, ask at most 2 follow-up questions:

Who is the main user: HR, manager, employee, leadership, or candidate?
What painful manual process should this replace?

Then summarize their product, not a workshop example:

markdown

undefined

学员通常会从上传填写好的头脑风暴表开始。将任何附件、粘贴内容或指向的文件视为输入源，忽略文件名。

先读取该内容，无需查找

day3 teaching materials/prd_brainstorm_sheet.md

，也无需要求学员重命名文件。

根据内容而非文件名判断输入类型：

学员提供的内容	归类为	下一步
包含痛点/问题、预期结果及功能（标题可能不同；Word/PDF/Markdown/图片均可）	已填写的头脑风暴工作表	总结内容，进入阶段2路径A，跳过空白填写步骤
仅为简报、单页文档或无功能列表的初步想法	创意文档	总结内容，进入阶段2路径B
未提供任何内容	缺失输入	请求学员上传工作表或描述简短想法

若学员未提供任何内容，询问：

text

请上传您填写好的头脑风暴工作表（任意文件名均可），或用1-3句话描述您的HR工具。
该工具的使用者是谁？解决什么问题？预期达成什么效果？

若学员的文档中已包含上述答案，请勿要求他们用1-3句话重写。

若学员的想法仍模糊，最多追加2个问题：

主要使用者是HR、经理、员工、管理层还是候选人？
该工具要替代哪个繁琐的人工流程？

然后总结学员的产品，而非workshop示例：

markdown

undefined

My Understanding

我的理解

This tool is for [user group]. It helps them [main job] so that [business result].


If it was a **filled worksheet**, end with:

```text
Is this correct? If yes, I will map your sheet and we can confirm the MVP functions.

If it was only a rough idea, end with:

text

Is this correct? Do you want to proceed to the worksheet step?

本工具面向[用户群体]，帮助他们完成[核心工作]，从而达成[业务成果]。


若学员提供的是**已填写的工作表**，结尾添加：

```text
以上理解是否正确？若正确，我将梳理您的工作表内容，确认MVP功能。

若仅为初步想法，结尾添加：

text

以上理解是否正确？是否要进入工作表填写环节？

Stage 2: Worksheet — Extract or Fill

阶段2：工作表——提取或填写

Use this structure in chat. Do not depend on a local teaching-file path. Do not edit the student's file unless they ask.

Part 1: Pain point
Part 2: Ideal result
Part 3: Function list
Part 4: Data
Part 5: Constraints
Part 6: Flow
Final check

在聊天中使用以下结构，无需依赖本地教学文件路径，除非学员要求，否则请勿编辑学员的文件。

第一部分：痛点
第二部分：理想结果
第三部分：功能列表
第四部分：数据
第五部分：约束条件
第六部分：流程
最终确认

Path A — Student uploaded a filled sheet (default)

路径A——学员已上传填写好的工作表（默认路径）

Map their answers onto Parts 1–6. Keep their wording. Headings do not need to match.
Do not write a new worksheet from scratch. Do not re-ask questions they already answered.
Mark gaps as
```
Missing:
```
and inferences as
```
Assumption:
```
.
For Part 3, split into four tiers: Must-have MVP (cap 5) / Today's Build Slice (1–2, chosen from must-have) / Nice to have / Future. If they listed more, group or defer — do not invent extra functions.
Output the mapped worksheet in chat.

将学员的答案对应到第1-6部分，保留学员的表述方式，标题无需完全匹配。
请勿从头编写新的工作表，无需重复询问学员已回答过的问题。
将缺失内容标记为
```
Missing:
```
，推断内容标记为
```
Assumption:
```
。
第三部分需分为四个层级：必备MVP功能（最多5项）/今日Build Slice（1-2项，从必备功能中选择）/锦上添花功能/未来规划功能。若学员列出的功能超过5项，进行分组或延后实现——请勿新增额外功能。
在聊天中输出梳理后的工作表。

Path B — No filled sheet, only a rough idea

路径B——未提供填写好的工作表，仅为初步想法

Fill the same Parts 1–6 in chat from the Stage 1 idea. Short point form. Mark

Assumption:

clearly. Cap must-have MVP functions at 5, and mark which 1–2 are the candidate Build Slice.

If a local teaching copy of the blank sheet exists, you may use it only as a layout reference. Never require the student to have that file or that filename.

Both paths end with:

text

Please confirm the MVP functions above. We should keep maximum 5.
Do you want to keep, remove, or combine any function before we pick today's build slice?

根据阶段1的想法，在聊天中填写上述第1-6部分，采用简短要点形式，明确标记

Assumption:

。必备MVP功能最多保留5项，并标记其中1-2项为候选Build Slice。

若本地有空白教学工作表，仅可将其作为布局参考，绝不能要求学员必须拥有该文件或使用指定文件名。

两条路径的结尾均为：

text

请确认上述MVP功能，我们最多保留5项。
在选择今日的build slice之前，您是否要保留、删除或合并某些功能？

Stage 3: Confirm MVP Functions

阶段3：确认MVP功能

Present only the MVP function shortlist:

markdown

undefined

仅展示MVP功能候选列表：

markdown

undefined

Proposed MVP Functions

拟议MVP功能

[Function] - [simple purpose]
[Function] - [simple purpose]
[Function] - [simple purpose]
[Function] - [simple purpose]
[Function] - [simple purpose]

[功能] - [简单用途]
[功能] - [简单用途]
[功能] - [简单用途]
[功能] - [简单用途]
[功能] - [简单用途]

Not In MVP

非MVP功能

[Future function]
[Future function]

Please confirm: are these the final MVP functions?


Do not move on until the user confirms.

[未来功能]
[未来功能]

请确认：以上是否为最终MVP功能？


获得用户确认后再继续推进。

Stage 3B: Confirm the Build Slice

阶段3B：确认Build Slice

This is a required gate. The MVP list says what the product should become. The slice says what we build today.

Propose one slice, drawn from the confirmed must-have functions:

markdown

undefined

这是必填的确认环节。MVP列表定义了产品的最终形态，而Slice定义了今日要完成的内容。

从已确认的必备功能中提出一个Slice方案：

markdown

undefined

Build Slice — what we build today

Build Slice——今日构建内容

Slice user: [exactly one role]
Slice path: [step] → [step] → [step] → [result] (3–5 steps, one happy path)
Slice data: synthetic only, [N] example rows. No real employee or customer records.
Done when: [one test case anyone in the room can repeat]
One edge case handled: [empty input / missing field / duplicate row]

Slice用户：[明确单一角色]
Slice流程：[步骤] → [步骤] → [步骤] → [结果]（3-5个步骤，单顺畅流程）
Slice数据：仅使用模拟数据，共[N]条示例行。不使用真实员工或客户记录。
完成标准：[会议室任何人可重复的测试用例]
处理的边缘场景：[空输入/缺失字段/重复行]

Not In This Build

本次构建不包含

Login and permissions
Saving to a database
Other roles' screens
Export, email, integrations
[anything else the student named]

Please confirm this slice. Everything in "Not In This Build" stays a decision we wrote down, not a gap we forgot.


Before proposing, check the slice against the ceiling:

- More than one slice user → cut to one.
- More than 5 steps in the path → cut steps, do not merge them into one vague step.
- Needs real company data → replace with synthetic rows and say so.
- Needs login before the path works → move login out and assume the slice user.

Do not move to PRD until the student confirms the slice. Keep the confirmed slice card visible and quote it at the start of Stages 5, 6, and 7.

登录与权限
数据存储到数据库
其他角色的界面
导出、邮件、集成功能
[学员提及的其他内容]

请确认该Slice。“本次构建不包含”项下的内容是我们明确记录的决策，而非遗漏的内容。


提出方案前，检查Slice是否符合上限要求：

- 若包含多个Slice用户，精简为一个。
- 若流程步骤超过5个，删减步骤，请勿合并为模糊的单一步骤。
- 若需要真实公司数据，替换为模拟数据并告知学员。
- 若流程需先登录才能运行，将登录环节移出，默认Slice用户已登录。

获得学员确认Slice后，才能进入PRD阶段。在第5、6、7阶段开始时，需展示并引用已确认的Slice内容。

Stage 4: Create Concept PRD With prd-writer

阶段4：使用prd-writer创建概念PRD

Use

prd-writer

mode A. Create the first version: product concept document.

Student-facing output should include:

Product name
One-sentence positioning
Product format
Target users
Product value
Core MVP function directions
Build slice for this session (one line, quoted from Stage 3B)
Not in scope
Open questions

For product format:

Recommend Web App by default for internal HR tools.
Explain simply: "A web app works in the browser and is easiest for HR/admin dashboards."

End with:

text

Does this product direction look right? If yes, we can move to the detailed PRD.

使用

prd-writer

的模式A，创建第一版产品概念文档。

面向学员的输出应包含：

产品名称
一句话定位
产品形态
目标用户
产品价值
核心MVP功能方向
本次session的Build Slice（一行，引用阶段3B的内容）
非范围内容
待解决问题

产品形态建议：

内部HR工具默认推荐Web App。
简单解释：“Web App可在浏览器中运行，最适合HR/管理员仪表盘。”

结尾添加：

text

该产品方向是否合理？若合理，我们可推进到详细PRD阶段。

Stage 5: Detailed PRD — Slice Scoped

阶段5：详细PRD——聚焦Slice

Only after concept PRD confirmation, create the detailed implementation PRD. Write it in detail for the Build Slice only. The remaining MVP functions get one line each as later phases. Do not spend the student's time speccing screens and permissions nobody will build today.

Include:

Product overview
The slice user and the one scenario
The slice path, step by step
Wireframe in ASCII — the slice screen only
Detailed description of the slice functions
Data needed for the slice, with the synthetic example rows
Done-when test case and the one edge case
Simple copywriting examples for the slice screen
Later phases — remaining must-have MVP functions, one line each, no detail
Remaining questions

Permissions in this document are one line: no login in this build; the slice user is assumed.

Keep the language non-technical. Explain saving and security as:

"Data needs to be saved safely."
"In this build the data is fake, so nothing sensitive can leak."

End with:

text

Please review this. It describes today's slice in full, and lists the rest as later phases.
If it looks right, we can plan the HTML prototype.

仅在概念PRD确认后，创建详细的落地PRD。仅针对Build Slice撰写详细内容，剩余MVP功能仅用一行描述作为后续阶段内容。请勿在无人今日构建的界面和权限上浪费学员时间。

内容应包含：

产品概述
Slice用户及单一场景
Slice流程（分步说明）
ASCII线框图——仅展示Slice对应的界面
Slice功能的详细描述
Slice所需数据及模拟示例行
完成标准测试用例及边缘场景
Slice界面的简单文案示例
后续阶段——剩余必备MVP功能，每项仅用一行描述，无需细节
待解决问题

权限相关内容仅需一行：本次构建无需登录，默认Slice用户已登录。

使用非技术语言，将存储和安全相关内容解释为：

“数据需安全存储。”
“本次构建使用模拟数据，不会泄露敏感信息。”

结尾添加：

text

请审阅以上内容。该文档详细描述了今日的Slice内容，并将剩余功能列为后续阶段。
若内容合理，我们可规划HTML原型。

Stage 6: Plan HTML Prototype

阶段6：规划HTML原型

Create a simple development plan for a single-file HTML prototype. Open the plan by quoting the confirmed slice card, so the scope is on screen while building.

The prototype plan should include:

Goal — the slice done-when sentence
Scope — the slice path only
The one screen the slice user needs
Mock data — the synthetic rows named in the slice
The slice path as clicks
Interactions
Build order
Testing checklist — the done-when case plus the one edge case

Default prototype requirements:

Single HTML file
Embedded CSS and JavaScript
Mock data in JavaScript arrays
One screen for the slice user
No real login
No role switcher, unless the confirmed slice explicitly spans two users
No database
No Supabase or Vercel yet

Anything outside the slice does not get built. If a button is needed for the screen to make sense, render it visibly disabled and list it under "Not In This Build" — do not implement it.

End with:

text

Do you want to build this HTML prototype now, or adjust the prototype plan first?

If the student chooses to build now: follow

workshop-local-run

with

mode=preflight

and

kind=html

before writing the HTML file. If the machine is not ready, finish that skill first. Then build. If later they cannot open the HTML, follow

workshop-local-run

with

mode=repair

and

kind=html

为单文件HTML原型创建简单开发计划，开头引用已确认的Slice内容，确保构建过程中始终明确范围。

原型规划应包含：

目标——Slice的完成标准语句
范围——仅包含Slice流程
Slice用户所需的单一界面
模拟数据——Slice中指定的模拟行
Slice流程对应的点击操作
交互逻辑
构建顺序
测试清单——完成标准用例加边缘场景

默认原型要求：

单HTML文件
内嵌CSS和JavaScript
模拟数据存储在JavaScript数组中
仅为Slice用户提供一个界面
无需真实登录
除非已确认的Slice明确涉及两个用户，否则无需角色切换器
无需数据库
暂不使用Supabase或Vercel

Slice以外的内容均不构建。若界面需要某个按钮才能合理展示，将其设置为可见但禁用状态，并记录在“本次构建不包含”项下——请勿实现该按钮功能。

结尾添加：

text

是否要立即构建该HTML原型，还是先调整原型规划？

若学员选择立即构建：在编写HTML文件前，先执行

workshop-local-run

技能，传入

mode=preflight

和

kind=html

参数。若设备未准备就绪，先完成该技能再构建。若后续无法打开HTML文件，执行

workshop-local-run

技能，传入

mode=repair

和

kind=html

参数。

Stage 7: Plan the Running App

阶段7：规划可运行应用

Two modes. Slice mode is the default inside a workshop session. Only use Full MVP mode when the student explicitly asks for it and there is time outside the session.

分为两种模式。Slice模式是workshop session内的默认模式。仅当学员明确要求且session外有充足时间时，才使用Full MVP模式。

Slice mode (default)

Slice模式（默认）

The goal is the same slice, now opened at a local address instead of a file. Nothing new gets added here.

markdown

undefined

目标与Slice一致，只是将文件改为本地地址打开，不新增任何内容。

markdown

undefined

What changes from prototype to a running app

从原型到可运行应用的变化

Same slice screen — opened at a local address instead of a file.
Demo data stays synthetic.
"Save" means export and import a file, not a database.
Login, permissions, and other roles stay out of this build.


Phase plan:
1. Set up the app shell
2. Move the slice screen in — do not regenerate it from the PRD
3. Make the slice path work at the local address
4. Test: the done-when case, the one edge case, and a refresh test
5. Write "Not In This Build" into the project folder

Persistence ceiling in this mode is file import/export. No Supabase, no login, no deployment.

Do not call the app done until all three checks pass: the done-when case, the one edge case, and one other person walking the slice path without the builder touching the keyboard.

相同的Slice界面——从本地地址打开，而非文件形式。
演示数据仍为模拟数据。
“保存”指文件导入/导出，而非存储到数据库。
登录、权限及其他角色仍不在本次构建范围内。


阶段规划：
1. 搭建应用框架
2. 迁移Slice界面——无需从PRD重新生成
3. 确保Slice流程可在本地地址运行
4. 测试：完成标准用例、边缘场景及刷新测试
5. 在项目文件夹中记录“本次构建不包含”的内容

该模式下数据持久化的上限是文件导入/导出，无需Supabase、登录或部署。

仅当以下三项检查均通过后，才可确认应用完成：完成标准用例、边缘场景测试通过，以及其他人员无需构建者操作即可走完Slice流程。

Full MVP mode

Full MVP模式

Only on explicit request, outside a session.

Default stack: Next.js, Supabase for database and login, Vercel for deployment.

Set up Next.js app
Set up Supabase database and login
Build pages from prototype
Add form save/submit flows
Add role permissions
Add export
Test
Deploy to Vercel

End with:

text

Do you want to build the running slice now, or review the plan first?

If the student chooses to implement now, in either mode: follow

workshop-local-run

with

mode=preflight

and

kind=nextjs

before

npx create-next-app

npm install

, or

npm run dev

. Pass

projectDir

, and set

successPath

to the slice screen. If later they cannot open localhost, follow

workshop-local-run

with

mode=repair

and

kind=nextjs

仅在学员明确要求且session外使用。

默认技术栈：Next.js、Supabase（数据库及登录）、Vercel（部署）。

搭建Next.js应用
配置Supabase数据库及登录
根据原型构建页面
添加表单保存/提交流程
添加角色权限
添加导出功能
测试
部署到Vercel

结尾添加：

text

是否要立即构建可运行的Slice应用，还是先审阅规划？

若学员选择立即实现（任意模式）：在执行

npx create-next-app

、

npm install

或

npm run dev

前，先执行

workshop-local-run

技能，传入

mode=preflight

和

kind=nextjs

参数。传入

projectDir

，并将

successPath

设置为Slice界面地址。若后续无法打开localhost，执行

workshop-local-run

技能，传入

mode=repair

和

kind=nextjs

参数。

Stage 8: Post-Build Missing Items

阶段8：构建后未完成项梳理

After the app is completed, separate two different kinds of "missing". Students lose confidence when a scope decision they made on purpose is presented back to them as an unfinished item.

Use this format:

markdown

undefined

应用完成后，区分两种不同类型的“未完成”内容。若将学员主动做出的范围决策视为未完成项，会打击他们的信心。

使用以下格式：

markdown

undefined

What Is Completed

已完成内容

The slice path works at a local address: [slice path]
Done-when case passes: [test case]
Edge case handled: [edge case]

Slice流程可在本地地址运行：[Slice流程]
完成标准用例通过：[测试用例]
边缘场景已处理：[边缘场景]

Deliberately Not In This Build

本次构建刻意不包含的内容

(These were decisions, not gaps. Quoted from the slice card.)

[item]
[item]

（这些是明确决策，而非遗漏项，引用Slice内容）

[内容]
[内容]

What Is Still Missing Before Real Use

正式使用前仍需完成的内容

Supabase project needs to be connected
Vercel deployment needs to be connected
Real users and roles need to be created
Real employee data needs to be imported
Company privacy/security review is needed
Email notifications/reminders may still need setup
Backup/export process should be agreed

需连接Supabase项目
需连接Vercel部署
需创建真实用户及角色
需导入真实员工数据
需完成公司隐私/安全审核
可能仍需设置邮件通知/提醒
需确定备份/导出流程

How To Connect Supabase

如何连接Supabase

Create a Supabase account.
Create a new project.
Copy the project URL and anon key.
Add them to
```
.env.local
```
.
Run the database migration SQL.
Create test users.
Test login and role permissions.

创建Supabase账户。
创建新项目。
复制项目URL及匿名密钥。
添加到
```
.env.local
```
文件中。
运行数据库迁移SQL。
创建测试用户。
测试登录及角色权限。

How To Deploy To Vercel

如何部署到Vercel

Push the app to GitHub.
Create a Vercel account.
Import the GitHub repository.
Add the same environment variables in Vercel.
Click Deploy.
Test the live URL.


Keep this as a checklist for non-technical HR users. The Supabase and Vercel steps are handoff reference, not homework for the session.

将应用推送到GitHub。
创建Vercel账户。
导入GitHub仓库。
在Vercel中添加相同的环境变量。
点击部署。
测试在线URL。


将其作为非技术HR用户的检查清单。Supabase和Vercel的步骤是交付参考，而非session内的作业。

Output Style

输出风格

Use English unless the student uses Chinese/Cantonese; then mirror their language.
Use tables for worksheets and checklists.
Avoid long technical explanations.
Use labels like "Assumption" and "Decision needed".
Always ask before proceeding to the next stage.

除非学员使用中文/粤语，否则使用英文；若学员使用中文/粤语，镜像使用对应语言。
工作表和清单使用表格形式。
避免冗长的技术解释。
使用“Assumption”（假设）、“Decision needed”（需决策）等标签。
进入下一阶段前务必询问学员。

Common Mistakes

常见错误

Do not produce a full technical build plan before MVP functions are confirmed.
Do not include more than 5 MVP functions.
Do not start a build stage before the Build Slice is confirmed in Stage 3B.
Do not build beyond the confirmed slice, even if the student asks mid-build. Record it under "Not In This Build".
Do not add a role switcher or login when the slice has one user.
Do not run Stage 7 in Full MVP mode during a session.
Do not add a database when file import/export satisfies the slice.
Do not regenerate the screen from the PRD in Stage 7. Move the confirmed prototype in.
Do not declare the running app done before the done-when case, the edge case, and a refresh test all pass.
Do not list a deliberate slice decision as a missing item in Stage 8.
Do not treat the HTML prototype as production.
Do not claim Supabase/Vercel is connected unless actually configured.
Do not bury the student in database schema unless they ask for developer details.
Do not skip the "what is still missing" explanation after the app is completed.

Do not tell the student to run

pwd

cd

npm install

, or

npm run dev

. Use

workshop-local-run

Do not start HTML or Next.js implementation until
```
workshop-local-run
```
preflight has run for that stage.
Do not start from Group 6 Talent Mapping (or any other group wrapper) when the student only kicked off this generic skill or pasted a different idea document.

Do not require the filename

prd_brainstorm_sheet.md

or the path

day3 teaching materials/

Do not refill a brainstorm sheet the student already uploaded. Extract, map, and confirm.
Do not skip their uploaded functions and invent a new function list.

确认MVP功能前，请勿生成完整技术构建计划。
MVP功能请勿超过5项。
阶段3B确认Build Slice前，请勿启动构建阶段。
请勿构建已确认Slice以外的内容，即使学员在构建过程中提出要求，将其记录在“本次构建不包含”项下即可。
若Slice仅涉及单用户，请勿添加角色切换器或登录功能。
session内请勿使用Full MVP模式运行阶段7。
若文件导入/导出可满足Slice需求，请勿添加数据库。
阶段7中请勿从PRD重新生成界面，直接迁移已确认的原型即可。
完成标准用例、边缘场景及刷新测试均通过前，请勿宣布可运行应用已完成。
阶段8中请勿将刻意的Slice决策列为未完成项。
请勿将HTML原型视为生产环境应用。
除非已实际配置，否则请勿宣称已连接Supabase/Vercel。
除非学员询问开发细节，否则请勿向他们展示数据库架构。
应用完成后，请勿跳过“正式使用前仍需完成的内容”的说明。
请勿要求学员执行
```
pwd
```
、
```
cd
```
、
```
npm install
```
或
```
npm run dev
```
命令，使用
```
workshop-local-run
```
技能即可。
执行
```
workshop-local-run
```
预检查前，请勿启动HTML或Next.js的实现工作。
若学员仅启动本通用技能或粘贴了其他创意文档，请勿从Group 6 Talent Mapping（或其他小组封装模板）开始。

请勿要求文件名必须为

prd_brainstorm_sheet.md

或路径为

day3 teaching materials/

。

学员已上传头脑风暴表的情况下，请勿重新填写，提取、梳理并确认即可。
请勿忽略学员上传的功能列表，自行创建新的功能列表。