yuxuanhui
91861565bb
- Introduced API guidelines for interface contracts and request handling. - Added design tokens usage guidelines for consistent styling across the project. - Established DTO guidelines for defining request parameters and response data types. - Created frontend structure guidelines to clarify directory organization and code placement rules. - Compiled a comprehensive frontend development guideline document covering various aspects of the development process. - Implemented quality guidelines to ensure code maintainability and adherence to best practices.
847 B
847 B
id, case_id, type, stage, owner_role, status, source_ids, derived_ids, created, updated
| id | case_id | type | stage | owner_role | status | source_ids | derived_ids | created | updated | ||
|---|---|---|---|---|---|---|---|---|---|---|---|
| RA-20260629-001 | REQ-20260629-001-example | requirement-analysis | user-requirement | PM | draft |
|
|
2026-06-29 | 2026-06-29 |
需求分析：AI 研发工作流研究区
问题拆解
- 需求链路容易断裂，需要统一 artifact 模型。
- skill 容易散落，需要独立源目录。
- 真实需求和规范资产容易混淆，需要分层目录。
约束
- 当前阶段以 vault 内 Markdown 为主。
- 不要求一次完成所有 skill。
- 需要支持后续反复调优。
风险
- 过早细化字段会导致维护成本高。
- skill 如果直接做成正式安装版，迭代成本会变高。
决策点
- 先用本目录维护 skill 草稿，稳定后再安装到 Codex skill 目录。