From b2f63ced5c823282733764db0f3e7f0cfb869606 Mon Sep 17 00:00:00 2001 From: tractorjuice <129532814+tractorjuice@users.noreply.github.com> Date: Fri, 27 Mar 2026 17:21:08 +0000 Subject: [PATCH] =?UTF-8?q?fix:=20deep=20autoresearch=20of=20diagram=20com?= =?UTF-8?q?mand=20=E2=80=94=20quality=20score=20and=20traceability?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit - Add Diagram Quality Score (passing criteria / 9 × 100%) - Add Component-to-Requirement Traceability matrix Supersedes #240. Co-Authored-By: Claude Opus 4.6 (1M context) --- arckit-claude/commands/diagram.md | 8 ++++++++ arckit-codex/commands/arckit.diagram.md | 8 ++++++++ arckit-codex/prompts/arckit.diagram.md | 8 ++++++++ arckit-codex/skills/arckit-diagram/SKILL.md | 8 ++++++++ arckit-copilot/prompts/arckit-diagram.prompt.md | 8 ++++++++ arckit-gemini/commands/arckit/diagram.toml | 8 ++++++++ arckit-opencode/commands/arckit.diagram.md | 8 ++++++++ 7 files changed, 56 insertions(+) diff --git a/arckit-claude/commands/diagram.md b/arckit-claude/commands/diagram.md index 07708e82..4e087ea9 100644 --- a/arckit-claude/commands/diagram.md +++ b/arckit-claude/commands/diagram.md @@ -1031,6 +1031,14 @@ After generating the diagram, evaluate it against the following quality criteria | 8 (Node placement) | Reorder declarations to place connected elements adjacent; group tightly-coupled components in a subgraph | | 9 (Element count) | Split diagram at natural architectural boundaries (see Step 5b) | +### Diagram Quality Score + +Calculate: passing criteria / 9 × 100%. Include this score in the output for tracking diagram quality over iterations. + +### Component-to-Requirement Traceability + +After the quality gate, add a table mapping each diagram element (system, container, component) to the requirement(s) it addresses. Flag elements with no requirement traceability (potentially out of scope) and requirements with no diagram element (missing from the architecture). + ### Iterative Review Loop **IMPORTANT:** Do not proceed to Step 6 until the quality gate passes. Follow this loop: diff --git a/arckit-codex/commands/arckit.diagram.md b/arckit-codex/commands/arckit.diagram.md index 06e27a0f..a17542c3 100644 --- a/arckit-codex/commands/arckit.diagram.md +++ b/arckit-codex/commands/arckit.diagram.md @@ -1029,6 +1029,14 @@ After generating the diagram, evaluate it against the following quality criteria | 8 (Node placement) | Reorder declarations to place connected elements adjacent; group tightly-coupled components in a subgraph | | 9 (Element count) | Split diagram at natural architectural boundaries (see Step 5b) | +### Diagram Quality Score + +Calculate: passing criteria / 9 × 100%. Include this score in the output for tracking diagram quality over iterations. + +### Component-to-Requirement Traceability + +After the quality gate, add a table mapping each diagram element (system, container, component) to the requirement(s) it addresses. Flag elements with no requirement traceability (potentially out of scope) and requirements with no diagram element (missing from the architecture). + ### Iterative Review Loop **IMPORTANT:** Do not proceed to Step 6 until the quality gate passes. Follow this loop: diff --git a/arckit-codex/prompts/arckit.diagram.md b/arckit-codex/prompts/arckit.diagram.md index 06e27a0f..a17542c3 100644 --- a/arckit-codex/prompts/arckit.diagram.md +++ b/arckit-codex/prompts/arckit.diagram.md @@ -1029,6 +1029,14 @@ After generating the diagram, evaluate it against the following quality criteria | 8 (Node placement) | Reorder declarations to place connected elements adjacent; group tightly-coupled components in a subgraph | | 9 (Element count) | Split diagram at natural architectural boundaries (see Step 5b) | +### Diagram Quality Score + +Calculate: passing criteria / 9 × 100%. Include this score in the output for tracking diagram quality over iterations. + +### Component-to-Requirement Traceability + +After the quality gate, add a table mapping each diagram element (system, container, component) to the requirement(s) it addresses. Flag elements with no requirement traceability (potentially out of scope) and requirements with no diagram element (missing from the architecture). + ### Iterative Review Loop **IMPORTANT:** Do not proceed to Step 6 until the quality gate passes. Follow this loop: diff --git a/arckit-codex/skills/arckit-diagram/SKILL.md b/arckit-codex/skills/arckit-diagram/SKILL.md index 0bd9ba21..8408e97e 100644 --- a/arckit-codex/skills/arckit-diagram/SKILL.md +++ b/arckit-codex/skills/arckit-diagram/SKILL.md @@ -1030,6 +1030,14 @@ After generating the diagram, evaluate it against the following quality criteria | 8 (Node placement) | Reorder declarations to place connected elements adjacent; group tightly-coupled components in a subgraph | | 9 (Element count) | Split diagram at natural architectural boundaries (see Step 5b) | +### Diagram Quality Score + +Calculate: passing criteria / 9 × 100%. Include this score in the output for tracking diagram quality over iterations. + +### Component-to-Requirement Traceability + +After the quality gate, add a table mapping each diagram element (system, container, component) to the requirement(s) it addresses. Flag elements with no requirement traceability (potentially out of scope) and requirements with no diagram element (missing from the architecture). + ### Iterative Review Loop **IMPORTANT:** Do not proceed to Step 6 until the quality gate passes. Follow this loop: diff --git a/arckit-copilot/prompts/arckit-diagram.prompt.md b/arckit-copilot/prompts/arckit-diagram.prompt.md index acaa7981..59de76bb 100644 --- a/arckit-copilot/prompts/arckit-diagram.prompt.md +++ b/arckit-copilot/prompts/arckit-diagram.prompt.md @@ -1031,6 +1031,14 @@ After generating the diagram, evaluate it against the following quality criteria | 8 (Node placement) | Reorder declarations to place connected elements adjacent; group tightly-coupled components in a subgraph | | 9 (Element count) | Split diagram at natural architectural boundaries (see Step 5b) | +### Diagram Quality Score + +Calculate: passing criteria / 9 × 100%. Include this score in the output for tracking diagram quality over iterations. + +### Component-to-Requirement Traceability + +After the quality gate, add a table mapping each diagram element (system, container, component) to the requirement(s) it addresses. Flag elements with no requirement traceability (potentially out of scope) and requirements with no diagram element (missing from the architecture). + ### Iterative Review Loop **IMPORTANT:** Do not proceed to Step 6 until the quality gate passes. Follow this loop: diff --git a/arckit-gemini/commands/arckit/diagram.toml b/arckit-gemini/commands/arckit/diagram.toml index 958d9630..5f116b29 100644 --- a/arckit-gemini/commands/arckit/diagram.toml +++ b/arckit-gemini/commands/arckit/diagram.toml @@ -1038,6 +1038,14 @@ After generating the diagram, evaluate it against the following quality criteria | 8 (Node placement) | Reorder declarations to place connected elements adjacent; group tightly-coupled components in a subgraph | | 9 (Element count) | Split diagram at natural architectural boundaries (see Step 5b) | +### Diagram Quality Score + +Calculate: passing criteria / 9 × 100%. Include this score in the output for tracking diagram quality over iterations. + +### Component-to-Requirement Traceability + +After the quality gate, add a table mapping each diagram element (system, container, component) to the requirement(s) it addresses. Flag elements with no requirement traceability (potentially out of scope) and requirements with no diagram element (missing from the architecture). + ### Iterative Review Loop **IMPORTANT:** Do not proceed to Step 6 until the quality gate passes. Follow this loop: diff --git a/arckit-opencode/commands/arckit.diagram.md b/arckit-opencode/commands/arckit.diagram.md index 06e27a0f..a17542c3 100644 --- a/arckit-opencode/commands/arckit.diagram.md +++ b/arckit-opencode/commands/arckit.diagram.md @@ -1029,6 +1029,14 @@ After generating the diagram, evaluate it against the following quality criteria | 8 (Node placement) | Reorder declarations to place connected elements adjacent; group tightly-coupled components in a subgraph | | 9 (Element count) | Split diagram at natural architectural boundaries (see Step 5b) | +### Diagram Quality Score + +Calculate: passing criteria / 9 × 100%. Include this score in the output for tracking diagram quality over iterations. + +### Component-to-Requirement Traceability + +After the quality gate, add a table mapping each diagram element (system, container, component) to the requirement(s) it addresses. Flag elements with no requirement traceability (potentially out of scope) and requirements with no diagram element (missing from the architecture). + ### Iterative Review Loop **IMPORTANT:** Do not proceed to Step 6 until the quality gate passes. Follow this loop: