You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docgraph-plugin/skills/align/SKILL.md
+35-16Lines changed: 35 additions & 16 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,25 +5,29 @@ description: Deep Consistency Gate - Verify Vertical and Horizontal relationship
5
5
6
6
# Deep Consistency Gate (Architecture & Meaning)
7
7
8
-
This skill serves as the **gate for depth and relationship integrity** within the documentation graph. It focuses on ensuring that nodes are not only correct in isolation (as verified by `validate`) but also perfectly aligned with their context (Vertical) and their peers (Horizontal).
8
+
This skill serves as the **gate for depth and relationship integrity** within the documentation graph. It focuses on
9
+
ensuring that nodes are not only correct in isolation (as verified by `validate`) but also perfectly aligned with their
10
+
context (Vertical) and their peers (Horizontal).
9
11
10
-
> [!IMPORTANT]
11
-
> This is an **Architecture & Meaning Gate**. Flag any semantic "fog" (unclear boundaries, implicit assumptions, or overloaded terms). Every node must be fully justified by its context.
12
+
> [!IMPORTANT] This is an **Architecture & Meaning Gate**. Flag any semantic "fog" (unclear boundaries, implicit
13
+
> assumptions, or overloaded terms). Every node must be fully justified by its context.
12
14
13
15
## Workflow Steps
14
16
15
17
### 0. Validation Pre-requisite
18
+
16
19
-**Level**: STRICT
17
-
-**Policy**:
20
+
-**Policy**:
18
21
- If `validate` status is unknown or FAIL -> **STOP** and return FAIL.
19
22
- Do not re-evaluate surface items (naming, templates) already covered by `validate`.
1.**Cohesion**: Are all elements within this node tightly related to the "What" definition?
48
55
2.**Abstraction**: Is the node at the correct level relative to its parents and peers?
49
56
50
57
### 4. Proposals & Impact Analysis
58
+
51
59
-**Level**: MANDATORY
52
60
53
61
When proposing changes (Clarify Context, Split, Merge, or Move):
62
+
54
63
1.**Affected Nodes**: List all nodes (parents, peers, children) that will be affected.
55
64
2.**Re-validation**: Indicate whether `validate` must be re-run for any affected nodes.
56
65
3.**Safety**: Ensure no existing references are broken without a remediation plan.
57
66
58
67
## Workflow Cases
59
68
60
69
### Case 1: TYPE_ID (e.g., FR, MOD)
70
+
61
71
- Perform a full graph consistency review for the given type.
62
72
63
73
### Case 2: NODE_ID (e.g., FR_LOGIN)
74
+
64
75
-**Status**: Focused Refinement.
65
-
- Perform a deep analysis specifically for the node and its immediate relations. Do not scan the entire graph unless necessary for baseline identification.
76
+
- Perform a deep analysis specifically for the node and its immediate relations. Do not scan the entire graph unless
77
+
necessary for baseline identification.
66
78
67
79
## Alignment Analysis Report
80
+
68
81
You **must** provide the analysis in the following format:
69
82
70
83
### Target
84
+
71
85
-**Node/Scope**: [ID or Type]
72
86
-**Baseline Peer Pattern**: [Description of dominant convention]
0 commit comments