feat: add frontend development guidelines and structure documentation
- 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.
This commit is contained in:
@@ -0,0 +1,58 @@
|
||||
---
|
||||
id: TRACEABILITY-AI-RD-WORKFLOW
|
||||
type: standard
|
||||
status: draft
|
||||
created: 2026-06-29
|
||||
---
|
||||
|
||||
# 追踪规则
|
||||
|
||||
## 基本规则
|
||||
|
||||
1. 每个 artifact 必须有唯一 `id`。
|
||||
2. 每个真实需求必须有统一 `case_id`。
|
||||
3. 下游产物必须在 `source_ids` 中声明直接上游。
|
||||
4. 上游产物应在 `derived_ids` 中声明直接下游。
|
||||
5. 如果需求变更影响已通过评审的产物,必须新增变更记录或更新状态为 `rework`。
|
||||
|
||||
## 推荐链路
|
||||
|
||||
```text
|
||||
INTAKE
|
||||
-> UR
|
||||
-> RA
|
||||
-> SA
|
||||
-> OR
|
||||
-> DR
|
||||
-> DS
|
||||
-> TASK
|
||||
-> TP
|
||||
-> TC
|
||||
```
|
||||
|
||||
实际项目允许分支,例如一个 DR 产生多个 DS,一个 DS 产生多个 TASK。
|
||||
|
||||
## 追踪矩阵字段
|
||||
|
||||
在每个 case 的 `traceability.md` 中维护:
|
||||
|
||||
| 上游 ID | 下游 ID | 关系 | 覆盖状态 | 备注 |
|
||||
| --- | --- | --- | --- | --- |
|
||||
| UR-xxx | OR-xxx | derives | covered | - |
|
||||
|
||||
覆盖状态:
|
||||
|
||||
- `covered`:已覆盖。
|
||||
- `partial`:部分覆盖。
|
||||
- `missing`:缺失。
|
||||
- `changed`:上游变更后待更新。
|
||||
- `not-applicable`:明确不适用。
|
||||
|
||||
## AI 检查点
|
||||
|
||||
每次进入下一阶段前,让 AI agent 检查:
|
||||
|
||||
- 是否存在没有下游的关键上游产物。
|
||||
- 是否存在没有上游的下游产物。
|
||||
- 是否存在 status 不一致的产物。
|
||||
- 是否存在已变更但未重新评审的产物。
|
||||
Reference in New Issue
Block a user