Prototype requirements workflow
Use this skill for may's requirement and prototype work.
Trigger conditions
Use this skill when the user mentions any of these topics:
- requirements, requirement modules, feature requirements, product design
- prototypes, SVG prototypes, Figma import, image handoff
- development handoff, six-dimension requirement specification
- operation manuals, user guides, feature usage instructions
- HR system modules such as performance, compensation, attendance, organization, social insurance, provident fund
Stable workspace
Use this stable workspace as the source of truth:
/Users/mayu/WorkBuddy/prototype-workspace
Before doing requirement-related work, read or follow:
/Users/mayu/WorkBuddy/prototype-workspace/AI入口.md
/Users/mayu/WorkBuddy/prototype-workspace/INDEX.md
If the task concerns a specific module or feature, locate it through:
/Users/mayu/WorkBuddy/prototype-workspace/02_模块需求/模块索引.md
Then read the module's 模块索引.md and the feature's README.md.
Default workflow
Follow this default workflow unless may says otherwise:
需求描述 -> SVG 原型源稿 -> 导入 Figma 手动调整 -> 导出 PNG/JPG -> 研发说明交付
Treat SVG as the default editable source artifact. Generate HTML only when one of these is needed:
- real interaction demo
- browser behavior such as tab switching, popups, scrolling, validation
- batch screenshots
- frontend implementation reference
Do not create a separate archive area by default. Store all artifacts under the corresponding module/function directory.
Requirement folder convention
Create and maintain requirements by module and feature:
02_模块需求/模块名/功能名/
├── README.md
├── 需求说明.md（含六维度：客户业务需求、业务现状与痛点、解决方案、旧数据影响、移动端、集团版）
├── svg/
├── figma/
├── images/
├── dev-spec/
└── notes/
Maintain indexes whenever adding or renaming modules/features:
- update
/Users/mayu/WorkBuddy/prototype-workspace/INDEX.md - update
/Users/mayu/WorkBuddy/prototype-workspace/02_模块需求/模块索引.md - update the module-level
模块索引.md - update the feature-level
README.md
Why requirement documents use six dimensions
Each feature has a single 需求说明.md with six dimensions instead of five separate files:
| Dimension | Purpose |
|---|---|
| 客户业务需求 | business goal, target users, scope, boundaries, customer original诉求 |
| 业务现状与痛点 | current problems, unmet scenarios, pain points |
| 解决方案 | pages, fields, interactions, states, business rules |
| 旧数据影响 | impact on existing data and in-progress flows after launch |
| 移动端 | mobile adaptation, interaction differences |
| 集团版 | multi-tenant/group scenarios, permission and data isolation |
For very small requirements, allow starting with only the feature README.md; add the six-dimension 需求说明.md once the feature grows.
Operation manual rules
When generating an operation manual, use exactly these four top-level dimensions:
应用场景功能入口使用说明对现有业务影响及处理方式
Apply the following rules:
- Supplement
应用场景from the requirement context when screenshots or source materials do not state it explicitly. - Leave
功能入口blank when the complete and reliable entry path is unknown. Do not guess menus or navigation paths. - Integrate business logic into the operation sequence in
使用说明. Avoid separating业务逻辑and操作流程into disconnected sections. - Describe each key step as one coherent unit containing the user action, the system behavior, and the resulting business outcome when applicable.
- Match detail to feature complexity:
- For simple features, use a concise continuous sequence and retain only configuration, core operation, necessary validation, and recovery or switching behavior.
- For complex features, expand by business scenario, role, state, exception, and validation as needed while keeping logic and actions integrated.
- Do not add unrelated sections such as applicable users, precautions, FAQs, terminology, or independent feature descriptions unless may explicitly requests them.
- Keep the manual user-facing and operational. Avoid turning it into a requirement specification or developer handoff document.
AI operating rules
When answering or executing requirement tasks:
- Prefer Chinese.
- Use the stable workspace path; do not create new dated workspaces for requirement management.
- Read indexes before searching broadly.
- Store new artifacts in the correct module/function folder.
- Keep feature
README.mdas the functional index, not as a huge all-in-one PRD. - Update indexes after creating modules, features, SVGs, Figma links, exported images, or developer specs.
- For prototypes, generate or modify SVG directly unless interactive HTML is explicitly useful.
- For developer handoff, ensure images are paired with the requirement specification (six dimensions).
Useful reference
Detailed current workspace rules live in:
/Users/mayu/WorkBuddy/prototype-workspace/00_工作流说明/需求文档组织规范.md
/Users/mayu/WorkBuddy/prototype-workspace/00_工作流说明/原型流程.md
/Users/mayu/WorkBuddy/prototype-workspace/00_工作流说明/交付规范.md
