From dbc18429bbf06b14deb49c7b20c99fd48b9a2596 Mon Sep 17 00:00:00 2001 From: ganjihong Date: Wed, 16 Sep 2026 14:29:11 +0800 Subject: [PATCH] =?UTF-8?q?ties=5Fto=5Frequirement=20=E8=BF=99=E4=B8=AA?= =?UTF-8?q?=E6=8C=87=E6=A0=87=E5=BF=98=E8=AE=B0=E5=8A=A0=E5=88=B0intent?= =?UTF-8?q?=E9=87=8C=E9=9D=A2?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- backend/agent/skills/cad-authoring/SKILL.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/backend/agent/skills/cad-authoring/SKILL.md b/backend/agent/skills/cad-authoring/SKILL.md index 9cab443f..5e7e5eb4 100644 --- a/backend/agent/skills/cad-authoring/SKILL.md +++ b/backend/agent/skills/cad-authoring/SKILL.md @@ -157,6 +157,7 @@ Feature level — attach `intent` to every feature: "label": "shaft_passage", "summary": "Ø45 central through bore, concentric with the outer contour", "why": "The fitting face of the sleeve; diameter follows the mating shaft", + "ties_to_requirement": "R2", "provenance": "authored" } } @@ -178,6 +179,10 @@ Feature level — attach `intent` to every feature: Use parameterized wording (`M8`, `Ø75`, `R8`), never a restatement of the request prose. - `why` (optional, ≤400 characters): the functional reason this feature exists. +- `ties_to_requirement` (optional): the requirement id from the task's + requirements contract that this feature implements. Include it whenever the + task carries requirement ids and the feature plainly implements one of them; + omit it when the task has no requirement ids. Never invent an id. - `provenance`: always `"authored"` when the model writes it. - Do not invent fields inside `intent`, and never treat a mismatch between an annotation and geometry as acceptable — the label must match the feature