weichenandCursor
45b8a38710
Why: Layout rules alone do not produce conclusion-first documents, extra views, or infographics, and nothing scored a deliverable before it was returned. Evidence: go test ./internal/prompts/ ./internal/quality/ ./internal/tools/ ./internal/squadadapter/ ./eval/ -count=1 and the house-style unittest passed in the previous session. Impact: Every task inherits content rules. Meetings, reports, and comparisons can name a view family. Long documents without a visual summary warn. quality_review and the squad checker share one scorecard. Refs: deliverable-quality-system A1-A5 Co-authored-by: Cursor <cursoragent@cursor.com>
17 lines
697 B
Markdown
17 lines
697 B
Markdown
# 上传文档应先判断相关性，再打标签入库
|
|
|
|
## 先校验，再生成
|
|
说话人1指出，上传后的第一步是判断文档与项目是否相关。确认后再拆开打标签。
|
|
一句话：没有这层记忆，后面的摘要和追溯都没有依据。
|
|
|
|
## 不要在上传时提示缺什么
|
|
依据会议原话，缺项提示放到体系成型之后。
|
|
一句话：上传节点是收集，不是验收。
|
|
|
|
## 基线要能迭代
|
|
新内容和已有基线比对，冲突时先问人。
|
|
一句话：一份基线反复补，而不是每次上传都新开一篇。
|
|
|
|
## 下一步
|
|
事项是写出第一版需求。负责人是陈威。期限是周五前。说不清的一律写未指明。
|