@agent-ix/quoin 0.1.3

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (215) hide show
  1. package/.agents/plugins/marketplace.json +14 -0
  2. package/.claude-plugin/marketplace.json +16 -0
  3. package/.claude-plugin/plugin.json +8 -0
  4. package/.codex-plugin/plugin.json +27 -0
  5. package/.github/plugin/marketplace.json +16 -0
  6. package/LICENSE +21 -0
  7. package/README.md +266 -0
  8. package/bin/quoin.js +14 -0
  9. package/default-modules.yaml +82 -0
  10. package/dist/base-DrUMkAh1.js +137 -0
  11. package/dist/base.d.ts +23 -0
  12. package/dist/base.d.ts.map +1 -0
  13. package/dist/catalog.d.ts +32 -0
  14. package/dist/catalog.d.ts.map +1 -0
  15. package/dist/cli.d.ts +18 -0
  16. package/dist/cli.d.ts.map +1 -0
  17. package/dist/cli.js +20 -0
  18. package/dist/commands/catalog/index.d.ts +2 -0
  19. package/dist/commands/catalog/index.d.ts.map +1 -0
  20. package/dist/commands/catalog/index.js +2 -0
  21. package/dist/commands/catalog/list.d.ts +11 -0
  22. package/dist/commands/catalog/list.d.ts.map +1 -0
  23. package/dist/commands/catalog/list.js +22 -0
  24. package/dist/commands/catalog/show.d.ts +13 -0
  25. package/dist/commands/catalog/show.d.ts.map +1 -0
  26. package/dist/commands/catalog/show.js +25 -0
  27. package/dist/commands/catalog/validate.d.ts +10 -0
  28. package/dist/commands/catalog/validate.d.ts.map +1 -0
  29. package/dist/commands/catalog/validate.js +27 -0
  30. package/dist/commands/config/doctor.d.ts +7 -0
  31. package/dist/commands/config/doctor.d.ts.map +1 -0
  32. package/dist/commands/config/doctor.js +15 -0
  33. package/dist/commands/config/edit.d.ts +7 -0
  34. package/dist/commands/config/edit.d.ts.map +1 -0
  35. package/dist/commands/config/edit.js +13 -0
  36. package/dist/commands/config/get.d.ts +11 -0
  37. package/dist/commands/config/get.d.ts.map +1 -0
  38. package/dist/commands/config/get.js +20 -0
  39. package/dist/commands/config/index.d.ts +2 -0
  40. package/dist/commands/config/index.d.ts.map +1 -0
  41. package/dist/commands/config/index.js +2 -0
  42. package/dist/commands/config/set.d.ts +12 -0
  43. package/dist/commands/config/set.d.ts.map +1 -0
  44. package/dist/commands/config/set.js +26 -0
  45. package/dist/commands/matrix.d.ts +14 -0
  46. package/dist/commands/matrix.d.ts.map +1 -0
  47. package/dist/commands/matrix.js +15 -0
  48. package/dist/commands/module/ensure-defaults.d.ts +8 -0
  49. package/dist/commands/module/ensure-defaults.d.ts.map +1 -0
  50. package/dist/commands/module/ensure-defaults.js +17 -0
  51. package/dist/commands/module/index.d.ts +2 -0
  52. package/dist/commands/module/index.d.ts.map +1 -0
  53. package/dist/commands/module/index.js +2 -0
  54. package/dist/commands/module/install.d.ts +11 -0
  55. package/dist/commands/module/install.d.ts.map +1 -0
  56. package/dist/commands/module/install.js +22 -0
  57. package/dist/commands/module/list.d.ts +8 -0
  58. package/dist/commands/module/list.d.ts.map +1 -0
  59. package/dist/commands/module/list.js +13 -0
  60. package/dist/commands/module/remove.d.ts +10 -0
  61. package/dist/commands/module/remove.d.ts.map +1 -0
  62. package/dist/commands/module/remove.js +16 -0
  63. package/dist/commands/plugin/deprecation.d.ts +10 -0
  64. package/dist/commands/plugin/deprecation.d.ts.map +1 -0
  65. package/dist/commands/plugin/ensure-defaults.d.ts +8 -0
  66. package/dist/commands/plugin/ensure-defaults.d.ts.map +1 -0
  67. package/dist/commands/plugin/ensure-defaults.js +12 -0
  68. package/dist/commands/plugin/index.d.ts +2 -0
  69. package/dist/commands/plugin/index.d.ts.map +1 -0
  70. package/dist/commands/plugin/index.js +2 -0
  71. package/dist/commands/plugin/install.d.ts +8 -0
  72. package/dist/commands/plugin/install.d.ts.map +1 -0
  73. package/dist/commands/plugin/install.js +12 -0
  74. package/dist/commands/plugin/list.d.ts +8 -0
  75. package/dist/commands/plugin/list.d.ts.map +1 -0
  76. package/dist/commands/plugin/list.js +12 -0
  77. package/dist/commands/plugin/remove.d.ts +8 -0
  78. package/dist/commands/plugin/remove.d.ts.map +1 -0
  79. package/dist/commands/plugin/remove.js +12 -0
  80. package/dist/commands/review.d.ts +14 -0
  81. package/dist/commands/review.d.ts.map +1 -0
  82. package/dist/commands/review.js +15 -0
  83. package/dist/commands/to-plan.d.ts +14 -0
  84. package/dist/commands/to-plan.d.ts.map +1 -0
  85. package/dist/commands/to-plan.js +15 -0
  86. package/dist/commands/update.d.ts +13 -0
  87. package/dist/commands/update.d.ts.map +1 -0
  88. package/dist/commands/update.js +34 -0
  89. package/dist/commands/write.d.ts +16 -0
  90. package/dist/commands/write.d.ts.map +1 -0
  91. package/dist/commands/write.js +33 -0
  92. package/dist/config-schema-Dp-vlxuR.js +13 -0
  93. package/dist/config-schema.d.ts +52 -0
  94. package/dist/config-schema.d.ts.map +1 -0
  95. package/dist/deprecation-fRxUHoxv.js +4 -0
  96. package/dist/flow-command-SMjCSOFg.js +88 -0
  97. package/dist/flow-command.d.ts +25 -0
  98. package/dist/flow-command.d.ts.map +1 -0
  99. package/dist/flows.d.ts +7 -0
  100. package/dist/flows.d.ts.map +1 -0
  101. package/dist/index.d.ts +11 -0
  102. package/dist/index.d.ts.map +1 -0
  103. package/dist/index.js +9 -0
  104. package/dist/modules-CW8pBK41.js +22 -0
  105. package/dist/modules.d.ts +10 -0
  106. package/dist/modules.d.ts.map +1 -0
  107. package/dist/org.d.ts +61 -0
  108. package/dist/org.d.ts.map +1 -0
  109. package/dist/plugins-GSxafyD3.js +77 -0
  110. package/dist/plugins.d.ts +13 -0
  111. package/dist/plugins.d.ts.map +1 -0
  112. package/dist/version-_1nY4KyJ.js +17 -0
  113. package/dist/version.d.ts +3 -0
  114. package/dist/version.d.ts.map +1 -0
  115. package/dist/write-CQAitcI5.js +156 -0
  116. package/dist/write.d.ts +28 -0
  117. package/dist/write.d.ts.map +1 -0
  118. package/package.json +119 -0
  119. package/skills/gap-analysis/SKILL.md +97 -0
  120. package/skills/gap-analysis/references/step-1-target-selection.md +53 -0
  121. package/skills/gap-analysis/references/step-2-plan-completion.md +49 -0
  122. package/skills/gap-analysis/references/step-3-matrix-verification.md +54 -0
  123. package/skills/gap-analysis/references/step-4-underspecified-code.md +63 -0
  124. package/skills/gap-analysis/references/step-5-semantic-review.md +51 -0
  125. package/skills/gap-analysis/references/step-6-specreview-artifact.md +95 -0
  126. package/skills/spec-app-review/SKILL.md +51 -0
  127. package/skills/spec-app-review/references/checklist.md +197 -0
  128. package/skills/spec-dependency-analysis/SKILL.md +75 -0
  129. package/skills/spec-ears-analysis/SKILL.md +89 -0
  130. package/skills/spec-evidence-analysis/SKILL.md +78 -0
  131. package/skills/spec-failure-domain-analysis/SKILL.md +44 -0
  132. package/skills/spec-ideation/SKILL.md +46 -0
  133. package/skills/spec-integrity-analysis/SKILL.md +47 -0
  134. package/skills/spec-matrix/SKILL.md +168 -0
  135. package/skills/spec-matrix/assets/test-cases/TC-001.md +35 -0
  136. package/skills/spec-matrix/assets/test-cases/TC-002.md +37 -0
  137. package/skills/spec-matrix/assets/test-cases/TC-006.md +50 -0
  138. package/skills/spec-matrix/assets/test-matrix-example.md +104 -0
  139. package/skills/spec-matrix/assets/test-matrix-template.md +123 -0
  140. package/skills/spec-matrix/workflow-assets/skills/matrix/SKILL.md +35 -0
  141. package/skills/spec-matrix/workflow-assets/skills/matrix/scripts/invariants.js +1 -0
  142. package/skills/spec-matrix/workflow-assets/skills/matrix/templates/report/default.md +30 -0
  143. package/skills/spec-matrix/workflow-assets/skills/matrix/workflows/matrix/def.yaml +82 -0
  144. package/skills/spec-object-review/SKILL.md +125 -0
  145. package/skills/spec-object-review/references/object-type-guide.md +118 -0
  146. package/skills/spec-review/SKILL.md +71 -0
  147. package/skills/spec-review/references/checklist.md +50 -0
  148. package/skills/spec-review/workflow-assets/skills/review/SKILL.md +96 -0
  149. package/skills/spec-review/workflow-assets/skills/review/scripts/invariants.js +60 -0
  150. package/skills/spec-review/workflow-assets/skills/review/workflows/review/def.yaml +68 -0
  151. package/skills/spec-risk-complexity-analysis/SKILL.md +77 -0
  152. package/skills/spec-scope-boundary-analysis/SKILL.md +86 -0
  153. package/skills/spec-security-analysis/SKILL.md +84 -0
  154. package/skills/spec-security-analysis/assets/security-analysis-example.md +89 -0
  155. package/skills/spec-security-analysis/assets/security-analysis-template.md +73 -0
  156. package/skills/spec-security-analysis/references/component-type-mapping.md +161 -0
  157. package/skills/spec-security-analysis/references/gdpr/ChII-Principles.md +58 -0
  158. package/skills/spec-security-analysis/references/gdpr/ChIII-DataSubjectRights.md +84 -0
  159. package/skills/spec-security-analysis/references/gdpr/ChIV-ControllerProcessor.md +83 -0
  160. package/skills/spec-security-analysis/references/gdpr/ChV-DataTransfers.md +62 -0
  161. package/skills/spec-security-analysis/references/gdpr/index.md +54 -0
  162. package/skills/spec-security-analysis/references/iso27001/A5-OrganizationalControls.md +64 -0
  163. package/skills/spec-security-analysis/references/iso27001/A6-PeopleControls.md +30 -0
  164. package/skills/spec-security-analysis/references/iso27001/A7-PhysicalControls.md +35 -0
  165. package/skills/spec-security-analysis/references/iso27001/A8-TechnologicalControls.md +66 -0
  166. package/skills/spec-security-analysis/references/iso27001/index.md +43 -0
  167. package/skills/spec-security-analysis/references/nist-800-53/AC-AccessControl.md +57 -0
  168. package/skills/spec-security-analysis/references/nist-800-53/AU-AuditAccountability.md +49 -0
  169. package/skills/spec-security-analysis/references/nist-800-53/CM-ConfigurationManagement.md +36 -0
  170. package/skills/spec-security-analysis/references/nist-800-53/IA-IdentificationAuthentication.md +44 -0
  171. package/skills/spec-security-analysis/references/nist-800-53/SA-SystemServicesAcquisition.md +50 -0
  172. package/skills/spec-security-analysis/references/nist-800-53/SC-SystemCommunications.md +53 -0
  173. package/skills/spec-security-analysis/references/nist-800-53/SI-SystemInformationIntegrity.md +52 -0
  174. package/skills/spec-security-analysis/references/nist-800-53/index.md +58 -0
  175. package/skills/spec-security-analysis/references/owasp-asvs/V1-Architecture.md +33 -0
  176. package/skills/spec-security-analysis/references/owasp-asvs/V10-MaliciousCode.md +33 -0
  177. package/skills/spec-security-analysis/references/owasp-asvs/V11-BusinessLogic.md +32 -0
  178. package/skills/spec-security-analysis/references/owasp-asvs/V12-Files.md +34 -0
  179. package/skills/spec-security-analysis/references/owasp-asvs/V13-API.md +34 -0
  180. package/skills/spec-security-analysis/references/owasp-asvs/V14-Configuration.md +35 -0
  181. package/skills/spec-security-analysis/references/owasp-asvs/V2-Authentication.md +36 -0
  182. package/skills/spec-security-analysis/references/owasp-asvs/V3-SessionManagement.md +35 -0
  183. package/skills/spec-security-analysis/references/owasp-asvs/V4-AccessControl.md +39 -0
  184. package/skills/spec-security-analysis/references/owasp-asvs/V5-Validation.md +37 -0
  185. package/skills/spec-security-analysis/references/owasp-asvs/V6-Cryptography.md +34 -0
  186. package/skills/spec-security-analysis/references/owasp-asvs/V7-ErrorLogging.md +37 -0
  187. package/skills/spec-security-analysis/references/owasp-asvs/V8-DataProtection.md +34 -0
  188. package/skills/spec-security-analysis/references/owasp-asvs/V9-Communication.md +32 -0
  189. package/skills/spec-security-analysis/references/owasp-asvs/index.md +59 -0
  190. package/skills/spec-security-analysis/references/soc2/CC1-ControlEnvironment.md +31 -0
  191. package/skills/spec-security-analysis/references/soc2/CC2-CommunicationInformation.md +27 -0
  192. package/skills/spec-security-analysis/references/soc2/CC3-RiskAssessment.md +29 -0
  193. package/skills/spec-security-analysis/references/soc2/CC4-MonitoringActivities.md +27 -0
  194. package/skills/spec-security-analysis/references/soc2/CC5-ControlActivities.md +28 -0
  195. package/skills/spec-security-analysis/references/soc2/CC6-LogicalPhysicalAccess.md +45 -0
  196. package/skills/spec-security-analysis/references/soc2/CC7-SystemOperations.md +42 -0
  197. package/skills/spec-security-analysis/references/soc2/CC8-ChangeManagement.md +32 -0
  198. package/skills/spec-security-analysis/references/soc2/CC9-RiskMitigation.md +34 -0
  199. package/skills/spec-security-analysis/references/soc2/index.md +46 -0
  200. package/skills/spec-security-analysis/references/standards-index.md +46 -0
  201. package/skills/spec-to-plan/SKILL.md +75 -0
  202. package/skills/spec-to-plan/references/step-0-plan-selection.md +121 -0
  203. package/skills/spec-to-plan/references/step-1-analysis.md +88 -0
  204. package/skills/spec-to-plan/references/step-2-test-plan.md +43 -0
  205. package/skills/spec-to-plan/references/step-3-execution-plan.md +218 -0
  206. package/skills/spec-to-plan/workflow-assets/skills/to-plan/SKILL.md +35 -0
  207. package/skills/spec-to-plan/workflow-assets/skills/to-plan/scripts/invariants.js +1 -0
  208. package/skills/spec-to-plan/workflow-assets/skills/to-plan/templates/implementation-plan/default.md +44 -0
  209. package/skills/spec-to-plan/workflow-assets/skills/to-plan/workflows/to-plan/def.yaml +85 -0
  210. package/skills/specify/SKILL.md +154 -0
  211. package/skills/specify/assets/app-spec-template.md +143 -0
  212. package/skills/specify/assets/spec-template.md +299 -0
  213. package/skills/specify/references/integration-tests.md +72 -0
  214. package/skills/specify/references/us-to-fr.md +40 -0
  215. package/skills/specify/references/writing-good-requirements.md +61 -0
@@ -0,0 +1,123 @@
1
+ # Test Matrix
2
+
3
+ ## Overview
4
+ This matrix ensures comprehensive test coverage by transforming requirements into test cases.
5
+
6
+ ## Test Matrix Rules
7
+ 1. **Coverage Rule**: Every acceptance criterion (AC) must have at least one test case
8
+ 2. **Option Permutation Rule**: Test all valid combinations of options
9
+ 3. **Constraint Boundary Rule**: Test at boundaries of each constraint
10
+ 4. **Error Path Rule**: Test all documented error conditions
11
+ 5. **State Transition Rule**: Test all valid state transitions (if applicable)
12
+ 6. **Edge Case Rule**: Identify and test edge cases for each requirement
13
+
14
+ ## Requirements Traceability
15
+
16
+ ### Stakeholder Requirement Coverage
17
+ | Stakeholder Req | Trace to US/FR | Test/Validation | Coverage Status |
18
+ |-----------------|----------------|-----------------|-----------------|
19
+ | StR-XXX | US-XXX, FR-XXX | Review | ✅ Complete |
20
+
21
+ ### User Story Coverage
22
+ | User Story | Acceptance Criteria | Test Cases | Coverage Status |
23
+ |------------|---------------------|------------|-----------------|
24
+ | US-XXX | US-XXX-AC-1 | TC-001, TC-002 | ✅ Complete |
25
+ | US-XXX | US-XXX-AC-2 | TC-003 | ✅ Complete |
26
+
27
+ ### Functional Requirement Coverage
28
+ | Functional Req | Acceptance Criteria | Test Cases | Coverage Status |
29
+ |----------------|---------------------|------------|-----------------|
30
+ | FR-XXX | FR-XXX-AC-1 | TC-004, TC-005 | ✅ Complete |
31
+
32
+ ### Non-Functional Requirement Coverage
33
+ | Non-Functional Req | Verification Method | Evidence/Test Cases | Status |
34
+ |--------------------|---------------------|---------------------|--------|
35
+ | NFR-XXX | Test / Review | TC-006, Audit Log | ✅ Complete |
36
+
37
+ ## Test Case Summary
38
+
39
+ | Test ID | Title | Type | Priority | Traces To | Status |
40
+ |---------|-------|------|----------|-----------|--------|
41
+ | TC-001 | [Test Title] | [Unit/Integration/E2E/Property] | [P0/P1/P2/P3/P4] | [US-XXX-AC-X] | [✅/⚠️/❌/🚧/⛔] |
42
+ | TC-002 | [Test Title] | [Unit/Integration/E2E/Property] | [P0/P1/P2/P3/P4] | [FR-XXX-AC-X] | [✅/⚠️/❌/🚧/⛔] |
43
+
44
+ **Note**: Detailed test case definitions should be in separate files in `test-cases/` directory.
45
+
46
+ **`Type`** shows the four most common values inline. The full enforced set is
47
+ `Unit`, `Integration`, `E2E`, `Property`, `Fuzz`, `Benchmark`, `Static`,
48
+ `Compile`, `Snapshot`, `Manual` — see the `Test Case Summary` section of
49
+ `SKILL.md` for when each applies. Use exactly one value per row; the vocabulary
50
+ is validated, so `Unit / pg_test` and other compounds are rejected.
51
+
52
+ ## Option Permutation Matrix
53
+ | Test Case | OPT-A | OPT-B | OPT-C | Expected Behavior |
54
+ |-----------|-------|-------|-------|-------------------|
55
+ | TC-XXX | Value1 | Value1 | Value1 | [behavior] |
56
+ | TC-XXX | Value1 | Value2 | Value1 | [behavior] |
57
+
58
+ ## Constraint Boundary Tests
59
+ | Constraint | Boundary Type | Test Value | Test Case | Expected |
60
+ |------------|---------------|------------|-----------|----------|
61
+ | CON-1 | Min | [value] | TC-XXX | [pass/fail] |
62
+ | CON-1 | Max | [value] | TC-XXX | [pass/fail] |
63
+ | CON-1 | Below Min | [value] | TC-XXX | Error |
64
+ | CON-1 | Above Max | [value] | TC-XXX | Error |
65
+
66
+ ## Edge Cases
67
+ | ID | Description | Related Req | Test Case | Risk if Untested |
68
+ |----|-------------|-------------|-----------|------------------|
69
+ | EC-001 | [edge case] | FR-XXX | TC-XXX | [risk] |
70
+
71
+ ## Integration Test Matrix
72
+
73
+ > Include this section when requirements specify integration testing is required.
74
+
75
+ ### Cross-Project Integrations
76
+ | Integration ID | Purpose | Target Project | Type | Test Cases | Status |
77
+ |----------------|---------|----------------|------|------------|--------|
78
+ | INT-001 | Event consumption | event-monitor | service | TC-INT-001, TC-INT-002 | 🚧 |
79
+ | INT-002 | API orchestration | orchestrator-service | service | TC-INT-003, TC-INT-004, TC-INT-005 | ❌ |
80
+
81
+ ### Local Service Integrations
82
+ | Integration ID | Purpose | Service | Type | Test Cases | Status |
83
+ |----------------|---------|---------|------|------------|--------|
84
+ | INT-010 | Data persistence | postgres.ix | database | TC-INT-010a, TC-INT-010b, TC-INT-010c | ✅ |
85
+ | INT-011 | Cache operations | redis.ix | service | TC-INT-011, TC-INT-012 | ⚠️ |
86
+ | INT-012 | Message publishing | event-bus | event | TC-INT-013, TC-INT-014, TC-INT-015 | ❌ |
87
+
88
+ ### Browser/UI Integrations
89
+ | Integration ID | Purpose | Target | Type | Test Cases | Status |
90
+ |----------------|---------|--------|------|------------|--------|
91
+ | INT-020 | Component rendering | Storybook | browser | TC-INT-020a thru TC-INT-020f | ✅ |
92
+ | INT-021 | User interaction flows | Storybook | browser | TC-INT-021, TC-INT-022, TC-INT-023 | 🚧 |
93
+ | INT-022 | Visual regression | Storybook | browser | TC-INT-024, TC-INT-025 | ❌ |
94
+
95
+ ### Integration Test Details
96
+
97
+ For each integration, define extensive test coverage:
98
+
99
+ | Test Case | Integration | Scenario | Input | Expected | Priority |
100
+ |-----------|-------------|----------|-------|----------|----------|
101
+ | TC-INT-001 | INT-001 | Happy path event processing | Valid event payload | Event processed, state updated | P0 |
102
+ | TC-INT-002 | INT-001 | Malformed event rejection | Invalid JSON schema | Event DLQ'd, error logged | P1 |
103
+ | TC-INT-010a | INT-010 | CRUD operations | Standard model data | Data persisted correctly | P0 |
104
+ | TC-INT-010b | INT-010 | Concurrent writes | Simultaneous updates | Proper lock handling | P1 |
105
+ | TC-INT-010c | INT-010 | Connection recovery | DB restart mid-operation | Graceful reconnection | P1 |
106
+ | TC-INT-020a | INT-020 | Default state render | No props | Component renders correctly | P0 |
107
+ | TC-INT-020b | INT-020 | Loading state | isLoading=true | Spinner displayed | P0 |
108
+ | TC-INT-020c | INT-020 | Error state | error prop set | Error message visible | P0 |
109
+ | TC-INT-020d | INT-020 | Interactive actions | User clicks button | Handler invoked | P1 |
110
+ | TC-INT-020e | INT-020 | Accessibility | Keyboard navigation | All controls reachable | P1 |
111
+ | TC-INT-020f | INT-020 | Mobile responsive | Viewport 375px | Layout adapts correctly | P2 |
112
+
113
+ ## Coverage Gaps
114
+ | Gap ID | Description | Risk Level | Mitigation |
115
+ |--------|-------------|------------|------------|
116
+ | GAP-001 | [description] | [High/Med/Low] | [plan to address] |
117
+
118
+ ## Test Execution Summary
119
+ | Category | Total | Passed | Failed | Blocked | Coverage |
120
+ |----------|-------|--------|--------|---------|----------|
121
+ | Unit | X | X | X | X | XX% |
122
+ | Integration | X | X | X | X | XX% |
123
+ | E2E | X | X | X | X | XX% |
@@ -0,0 +1,35 @@
1
+ ---
2
+ name: spec-matrix
3
+ description: Build and update requirements test matrices.
4
+ contributes:
5
+ workflows: ./workflows
6
+ ---
7
+
8
+ # /spec-matrix
9
+
10
+ ## When To Use
11
+
12
+ Use this skill when generating or reviewing bidirectional mappings between requirements, acceptance criteria, tests, and evidence.
13
+
14
+ ## What It Does
15
+
16
+ Build and update requirements test matrices. The workflow definition is the source of truth for phases, gates, item schemas, recipes, and validation points.
17
+
18
+ ## Workflow Behavior
19
+
20
+ - Start from the workflow status and follow reported next actions.
21
+ - Record evidence items before advancing analysis, review, or validation phases.
22
+ - Use recipes for deterministic command chains, but preserve human gates for acceptance.
23
+ - Prefer templates for stable artifact creation and generic file editing for broad semantic rewrites.
24
+
25
+ ## Acceptance Criteria
26
+
27
+ - AC-1: Creates or updates matrix rows for requirement-to-test and test-to-requirement coverage.
28
+ - AC-2: Flags orphan requirements, orphan tests, duplicate mappings, and stale evidence references.
29
+ - AC-3: Validates matrix output before acceptance and avoids changing requirement text unless another workflow is requested.
30
+
31
+ ## Boundaries
32
+
33
+ - Do not silently overwrite existing human-authored requirements artifacts.
34
+ - Do not invent missing facts, links, or evidence; record assumptions and gaps.
35
+ - Do not expand to adjacent spec operations unless the user request requires it or the workflow directs it.
@@ -0,0 +1 @@
1
+ export { specInvariants as invariants } from "../../../dist/index.js";
@@ -0,0 +1,30 @@
1
+ ---
2
+ type: requirements-matrix
3
+ id: "{{items.operation_request.request.artifact_id}}"
4
+ title: "{{items.operation_request.request.title}}"
5
+ scope: "{{items.operation_request.request.scope}}"
6
+ ---
7
+
8
+ # {{items.operation_request.request.artifact_id}}: {{items.operation_request.request.title}}
9
+
10
+ ## Operation
11
+
12
+ Build and update requirements test matrices.
13
+
14
+ ## Scope
15
+
16
+ {{items.operation_request.request.scope}}
17
+
18
+ ## Evidence
19
+
20
+ {{items.operation_request.request.evidence}}
21
+
22
+ ## Findings
23
+
24
+ {{items.operation_request.request.findings}}
25
+
26
+ ## Acceptance Criteria
27
+
28
+ - Evidence is recorded before conclusions.
29
+ - Findings reference concrete spec paths, requirement ids, or graph objects where available.
30
+ - Follow-up work is expressed as recommended next workflows rather than hidden edits.
@@ -0,0 +1,82 @@
1
+ name: matrix
2
+ version: 0.1.0
3
+ description: Build and update requirements test matrices.
4
+ initialPhase: intake
5
+ phases:
6
+ - { name: intake }
7
+ - { name: evidence_recorded }
8
+ - { name: report_rendered }
9
+ - { name: validated }
10
+ - { name: accepted, terminal: true }
11
+ transitions:
12
+ - from: intake
13
+ to: evidence_recorded
14
+ invariants:
15
+ - "interview.complete:request"
16
+ defaultGate: auto
17
+ - from: evidence_recorded
18
+ to: report_rendered
19
+ invariants: []
20
+ defaultGate: auto
21
+ - from: report_rendered
22
+ to: validated
23
+ invariants:
24
+ - "artifact.frontmatter_valid:report"
25
+ defaultGate: auto
26
+ - from: validated
27
+ to: accepted
28
+ invariants: []
29
+ defaultGate: hitl
30
+ itemSchemas:
31
+ operation_request: {}
32
+ OperationReportSchema:
33
+ required: [type, id, title, scope]
34
+ properties:
35
+ type: { type: string }
36
+ id: { type: string }
37
+ title: { type: string }
38
+ scope: { type: string }
39
+ linkSchemas: {}
40
+ interviews:
41
+ request:
42
+ itemType: operation_request
43
+ completenessRule: all_required
44
+ questions:
45
+ - key: artifact_id
46
+ prompt: "Report id, for example REPORT-001."
47
+ type: text
48
+ required: true
49
+ - key: title
50
+ prompt: "Report title."
51
+ type: text
52
+ required: true
53
+ - key: scope
54
+ prompt: "Spec paths, requirement ids, or graph scope to inspect."
55
+ type: text
56
+ required: true
57
+ - key: evidence
58
+ prompt: "Evidence sources used for this operation."
59
+ type: text
60
+ required: true
61
+ - key: findings
62
+ prompt: "Findings, gaps, or result summary."
63
+ type: text
64
+ required: true
65
+ artifactTemplates:
66
+ report:
67
+ source: templates/report/default.md
68
+ target: spec/reports/matrix/${items.operation_request.request.artifact_id}.md
69
+ phase: report_rendered
70
+ frontmatterSchema: OperationReportSchema
71
+ recipes:
72
+ run-to-review:
73
+ description: Record inputs, render the operation report, validate it, then stop at acceptance.
74
+ steps:
75
+ - command: advance
76
+ to: evidence_recorded
77
+ - command: advance
78
+ to: report_rendered
79
+ - command: advance
80
+ to: validated
81
+ - command: advance
82
+ to: accepted
@@ -0,0 +1,125 @@
1
+ ---
2
+ name: spec-object-review
3
+ description: Audit spec domain objects, cross-references, and entity completeness across single or multi-repo ecosystems.
4
+ ---
5
+
6
+ # Spec Object Review
7
+
8
+ Audit a codebase's spec domain objects for completeness, cross-reference integrity, and alignment with the object-type-guide format.
9
+
10
+ ## When to Use
11
+
12
+ - After initial spec creation to verify domain coverage.
13
+ - When integrating a new service into an existing ecosystem.
14
+ - When fixing spec-code misalignments or tracing integration bugs.
15
+ - As a periodic health check on spec quality.
16
+
17
+ ## Process
18
+
19
+ ### 1. Inventory
20
+
21
+ Scan all `spec/` directories in scope (single repo or ecosystem-wide):
22
+
23
+ ```bash
24
+ find spec/ -name "*.md" -path "*/functional/*"
25
+ ```
26
+
27
+ For each FR, extract frontmatter fields: `id`, `title`, `type`, `object`.
28
+
29
+ ### 2. Cross-Reference Audit
30
+
31
+ For every FR with a Traceability / Dependencies section:
32
+
33
+ - **Verify upstream refs exist**: If FR-A says it depends on `repo-B FR-003`, confirm `repo-B/spec/functional/FR-003-*.md` exists.
34
+ - **Verify bidirectional tracing**: If FR-A references FR-B as upstream, FR-B should reference FR-A as downstream (or vice versa).
35
+ - **Check endpoint paths match code**: For any API endpoint documented in a spec, grep the source code to confirm the path is correct. Pay attention to router prefixes that may not appear in the FR but are applied at app mount time.
36
+
37
+ **Common Pitfalls:**
38
+ - Router prefixes (e.g., `/auth` prefix) silently changing the actual path vs what the FR documents.
39
+ - References using vague service names ("identity") instead of specific FR IDs ("identity FR-006").
40
+ - `depends_on` in master spec frontmatter being empty when runtime dependencies exist.
41
+
42
+ ### 3. Domain Object Completeness
43
+
44
+ Check whether domain objects defined inline in specs have proper dedicated FRs with `object:` frontmatter.
45
+
46
+ **Scan for inline objects:**
47
+
48
+ | Pattern in spec | Missing Domain FR Type |
49
+ |----------------|----------------------|
50
+ | `### Data Models` table with field/type columns | `entity` or `value_object` |
51
+ | API Request/Response JSON bodies in `## API Contract` | `value_object` |
52
+ | `class X(SQLModel)` or Pydantic model in code without FR | `entity` |
53
+ | `class X(str, Enum)` or status fields | `value_object` or `state_machine` |
54
+ | Multi-step behavior spanning services | `process` |
55
+ | Env var / configuration table in spec.md | `configuration` |
56
+ | `stateDiagram-v2` in spec.md | `state_machine` |
57
+
58
+ **The Semantic Payload Trap:** Inline JSON bodies inside of an endpoint's API Contract section are the #1 cause of cross-repo semantic drift. Even if the syntax matches (e.g. `{ "username": "string" }`), the *semantics* drift (`email` vs `account_name`). Any structured payload passed across a bounded context MUST have a dedicated `value_object` FR to anchor its field semantics.
59
+
60
+ **Reference**: See [object-type-guide.md](references/object-type-guide.md) for the full type taxonomy.
61
+
62
+ ### 4. Frontmatter Validation
63
+
64
+ All FRs must use standard frontmatter:
65
+
66
+ ```yaml
67
+ ---
68
+ id: FR-XXX
69
+ title: "Descriptive Title"
70
+ type: FR
71
+ object: entity # Only if FR defines a domain object
72
+ relationships: # Structured array of cross-references
73
+ - target: "ix://org/repo/TargetFR"
74
+ type: "depends_on"
75
+ cardinality: "1:1"
76
+ ---
77
+ ```
78
+
79
+ **Check for:**
80
+ - `type: functional` instead of `type: FR` (non-standard value).
81
+ - Missing `object:` on FRs that clearly define domain objects.
82
+ - `domain:` or `status:` fields that aren't part of the standard schema.
83
+ - Missing `relationships:` array in the frontmatter when the body references upstream/downstream dependencies (such as an API, an event, a data entity, or a required permission).
84
+ - Dependencies defined as generic Markdown text lists or raw Mermaid diagrams instead of structured YAML relational objects.
85
+ - Relationships using generic `type: "depends_on"` when a more specific semantic linkage applies (e.g. `calls`, `publishes`, `consumes`, `triggers`, `reads`, `writes`, `requires`).
86
+
87
+ ### 5. Rebuild Test
88
+
89
+ Ask yourself these questions. If the answer is "no" to any, there's a gap:
90
+
91
+ 1. **Can I rebuild this system from spec alone?** Every entity, its fields, invariants, and relationships should be in a dedicated FR — not just inline markdown tables.
92
+ 2. **Can I find how to perform operation X?** End-to-end flows (login, deploy, sync) should have `object: process` FRs that show the full sequence across services.
93
+ 3. **Can I find how to integrate?** Each service should document what it consumes and what it exposes, with FR-level traceability.
94
+ 4. **Can I troubleshoot?** Error handling sections should exist in every API endpoint and process FR.
95
+
96
+ ### 6. Application-Level Check
97
+
98
+ For multi-service domains (e.g., Auth = auth-service + identity + auth-py + auth-fastapi + ts-auth-sdk):
99
+
100
+ - Is there a catalog fixture defining the Application entity?
101
+ - Does an application-level repo exist to own:
102
+ - The bounded context / domain FR.
103
+ - Cross-service process FRs.
104
+ - The catalog fixture itself.
105
+ - Do individual service repos avoid duplicating domain-level concerns?
106
+
107
+ ## Output
108
+
109
+ Produce a review report with:
110
+
111
+ | Priority | Finding | Repo | Impact |
112
+ |----------|---------|------|--------|
113
+ | P0 | Spec-code mismatch | repo | Incorrect documentation |
114
+ | P1 | Missing cross-reference | repo | Traceability gap |
115
+ | P2 | Missing `object:` frontmatter | repo | Parser incompatibility |
116
+ | P3 | Missing domain-typed FR | repo | Incomplete domain model |
117
+
118
+ ## Tips from Real Reviews
119
+
120
+ - **Router prefix trap**: FastAPI router prefixes (e.g., `router = APIRouter(prefix="/auth")`) silently change paths. Always verify spec paths against the *mounted* path, not just the route decorator.
121
+ - **Vague traceability**: `| identity | Fetches user |` is weaker than `| identity FR-006 | Fetches user via internal lookup |`. Always use FR-level IDs.
122
+ - **Empty `depends_on`**: Client libraries almost always depend on the service they consume. An empty `depends_on: []` in a client SDK spec is a red flag.
123
+ - **Section number gaps**: Master specs jumping from §8 to §19 suggest template sections were deleted. Check if §8 (Domain Model) and §9 (Events and Signals) should be populated.
124
+ - **Shared entities**: If two FRs reference the same model (e.g., `AuthToken` used by both API Keys FR-004 and OAuth Clients FR-008), the model needs its own entity FR to avoid ambiguity.
125
+ - **Semantic mismatch trap**: Even when endpoint signatures align, field semantics can drift across bounded contexts (e.g., UI sends `email` mapped to SDK's `username` field, but Backend strictly expects an account name). Always cross-check the *meaning* and *format* of data passed across boundaries, especially in multi-repo systems like Auth.
@@ -0,0 +1,118 @@
1
+ # Domain Type Decision Guide
2
+
3
+ When an FR defines a domain object, set the `object:` frontmatter field and use the matching template.
4
+
5
+ > The `assets/...-template.md` names below identify each object type's template
6
+ > **within its catalog module** — they are not files shipped in this skill.
7
+ > Obtain the actual skeleton + schema with `quoin write --types <type>` (or
8
+ > inspect a type with `quoin catalog show <type>`).
9
+
10
+ ## Business Objects (spec-objects-business)
11
+
12
+ - `entity` / `aggregate_root` / `nested_entity`: Data entity, model, or aggregate → `assets/business/entity-template.md`
13
+ - `value_object`: Immutable value type or enum → `assets/business/value-object-template.md`
14
+ - `event`: Domain events emitted by a service → `assets/business/event-template.md`
15
+ - `process`: End-to-end process spanning multiple FRs → `assets/business/process-template.md`
16
+ - `state_machine`: Lifecycle with states/transitions → `assets/business/state-machine-template.md`
17
+ - `repository`: Data access layer for an entity → `assets/business/repository-template.md`
18
+ - `domain`: Bounded context definition (`## Bounded Context` is the required kernel; entities are SEPARATE `entity` FRs linked via `contains` edges — the `## Entities` list is an optional summary) → `assets/business/domain-template.md`
19
+ - `enumeration`: Controlled label vocabulary other artifacts reference by exact string (state names, codec kinds, metric labels) → `assets/business/enumeration-template.md`
20
+
21
+ ## Architecture Objects (spec-objects-architecture)
22
+
23
+ - `api_endpoint`: REST/HTTP endpoint (routes live INSIDE `## Endpoint` — there is no separate Routes section) → `assets/architecture/api-endpoint-template.md`
24
+ - `queue`: Message queue or topic → `assets/architecture/queue-template.md`
25
+ - `data_schema`: Database table / JSON-shaped schema → `assets/architecture/data-schema-template.md`
26
+ - `binary_format`: Persisted BINARY layout (offsets/sizes/endianness as a `## Layout` YAML block — JSON Schema can't express these) → `assets/architecture/binary-format-template.md`
27
+ - `interface`: Operations contract WITHIN the system (trait / TS interface / ABC / port; the whole plugin/codec/driver space). `## Contract` YAML block; implementations link via `implements` edges, never enumerated inline → `assets/architecture/interface-template.md`
28
+ - `external_contract`: Contract with an EXTERNAL system (vendor, peer service whose contract this repo does not own) → `assets/architecture/external-contract-template.md`
29
+ - `extension_point`: Pluggability as a first-class node (registration + stability guarantees around a published interface) → `assets/architecture/extension-point-template.md`
30
+ - `action`: Command/action (CLI, job, task) → `assets/architecture/action-template.md`
31
+ - `ui_component`: UI component with props → `assets/architecture/ui-component-template.md`
32
+ - `page`: Full page, route, or view → `assets/architecture/page-template.md`
33
+ - `dto`: API request/response schema (Pydantic/Zod model) → `assets/architecture/dto-template.md`
34
+ - `middleware`: Cross-cutting concern (auth, logging, validation) → `assets/architecture/middleware-template.md`
35
+
36
+ ## Operational Objects (spec-objects-operational)
37
+
38
+ - `configuration`: Configuration parameters / env vars → `assets/operational/configuration-template.md`
39
+ - `migration`: Database migration → `assets/operational/migration-template.md`
40
+ - `hook`: Lifecycle event (startup, shutdown, pre/post) → `assets/operational/hook-template.md`
41
+ - `job`: Scheduled or recurring task → `assets/operational/job-template.md`
42
+
43
+ ## Standard Behavioral FR
44
+
45
+ If the FR does not define a domain object, omit the `object:` field and use `assets/functional-requirement-template.md`.
46
+
47
+ ## Tags (Discovery Dimensions)
48
+
49
+ Tags are cross-cutting concerns — they define how an FR is **used** or **discovered**, not what it structurally IS. Set tags in the `tags:` frontmatter field.
50
+
51
+ > **Important**: `integration` is a **tag**, not an object type. Never use `object: integration`. (The legacy `integration` object type was removed from spec-objects-architecture v0.2.0 — internal contracts are `interface`, external-system contracts are `external_contract`, and service-client FRs use `calls`/`consumes` relationship edges.)
52
+
53
+ Common tags:
54
+ - `integration`: Consumer-facing integration contracts, SDKs, connection guides → appears in Integration tab
55
+ - `consumer-facing`: Endpoints or APIs intended for external consumers
56
+ - `internal`: Internal service-to-service contracts
57
+ - `security`: Security-critical functionality → appears in Security tab
58
+
59
+ Example: An FR for an integration guide with no structural object:
60
+ ```yaml
61
+ ---
62
+ id: FR-007
63
+ title: "Consumer Integration Contract"
64
+ type: FR
65
+ tags: [integration]
66
+ ---
67
+ ```
68
+
69
+ Example: An endpoint that is both structural and consumer-facing:
70
+ ```yaml
71
+ ---
72
+ id: FR-001
73
+ title: "Login Endpoint"
74
+ type: FR
75
+ object: api_endpoint
76
+ tags: [consumer-facing]
77
+ ---
78
+ ```
79
+
80
+ ## Semantic Graph Linkages (Verbs vs Nouns)
81
+
82
+ The spec ecosystem uses a strictly typed relationship graph to link specifications.
83
+
84
+ The domain objects defined above act as the **Nouns** (Nodes) in the graph. The connections between them must be pure **Verbs** (Edges), defined in the `relationships:` array of the YAML frontmatter.
85
+
86
+ > **CRITICAL**: Do NOT bake the noun into the verb! (e.g., do not use `publishes_event` or `uses_api`). The database already knows the target is an `event` or an `api_endpoint` based on its domain type.
87
+
88
+ ### Valid Relationship Verbs
89
+ When linking specs, you must use one of the following strict semantic primitives:
90
+
91
+ **1. Operational & Flow:**
92
+ - `calls`: Synchronous invocation (e.g., an endpoint `calls` an external API).
93
+ - `publishes`: Asynchronous emission (e.g., a process `publishes` a domain event).
94
+ - `consumes`: Asynchronous reception (e.g., a worker process `consumes` a domain event).
95
+ - `triggers`: Process initiation (e.g., a scheduler `triggers` a job or macro-flow).
96
+
97
+ **2. Data & State:**
98
+ - `reads`: Safe, read-only data consumption (e.g., a component `reads` an entity).
99
+ - `writes`: Mutating data access (e.g., an endpoint `writes` an entity).
100
+
101
+ **3. Contracts & Constraints:**
102
+ - `requires`: Security and configuration bounds (e.g., an endpoint `requires` a specific permission scope or configuration).
103
+ - `implements`: Interface/contract fulfillment.
104
+ - `specifies`: An object FR providing the normative definition of structure/contract a behavioral FR relies on (e.g., a `binary_format` FR `specifies` the storage FR that writes it). Use this — not `references` — for the object-FR → behavioral-FR edge.
105
+
106
+ **4. Generic Structure:**
107
+ - `depends_on`: Library/package dependencies. NOTE: as a frontmatter FIELD, `depends_on:` is reserved for `spec.md` (master-requirements), where it is the repo-level dependency manifest. At artifact level always author the explicit `relationships:` array — bare-ID sugar fields are read-side ingestion tolerance only.
108
+ - `contains`: Composition (e.g., UI component `contains` sub-components, Aggregate Root `contains` Entities, a `domain` `contains` its entity FRs).
109
+ - `transitions_to`: State machine flows.
110
+ - `references` / `related_to`: Loose general linkages (use only if no specific verb applies).
111
+
112
+ ## Acceptance-Criteria Verification Vocabulary
113
+
114
+ AC table `Verification` cells use the ISO 29148 methods — `Inspection`,
115
+ `Analysis`, `Demonstration`, `Test` — optionally annotated with test-case
116
+ references, e.g. `Test (TC-035)`. Checked by the `ac-verification-method`
117
+ lint rule (`quire lint`); spec-only artifacts legitimately carry
118
+ `Inspection`/`Analysis` until implementation upgrades them to `Test (TC-xxx)`.
@@ -0,0 +1,71 @@
1
+ ---
2
+ name: spec-review
3
+ description: Review requirements for quality, consistency, and completeness.
4
+ ---
5
+
6
+ # Review Requirements
7
+
8
+ Use this skill to validate requirements artefacts before implementation.
9
+
10
+ ## Checklist
11
+
12
+ See **[references/checklist.md](references/checklist.md)** for the detailed quality gates.
13
+
14
+ ## Choose the review set
15
+
16
+ Before reviewing, present these options to the user and let them choose:
17
+
18
+ - **base** — the **Checklist** only: ID formats, US/FR/TC quality, and the six coverage
19
+ rules. No analysis skills.
20
+ - **all** — `base` plus all seven analyses below.
21
+ - **subset** — `base` plus the analyses the user picks from the seven below.
22
+
23
+ The seven analyses:
24
+
25
+ | Analysis | Skill |
26
+ | --- | --- |
27
+ | failure-domain | `spec-failure-domain-analysis` |
28
+ | integrity | `spec-integrity-analysis` |
29
+ | dependency | `spec-dependency-analysis` |
30
+ | evidence | `spec-evidence-analysis` |
31
+ | risk-complexity | `spec-risk-complexity-analysis` |
32
+ | scope-boundary | `spec-scope-boundary-analysis` |
33
+ | ears-conformance | `spec-ears-analysis` |
34
+
35
+ ## Process
36
+
37
+ 1. Automated Checks (always — part of `base`):
38
+ - Validate ID formats (US/FR/TC/AC/CON).
39
+ - Detect duplicates or gaps.
40
+ - Validation link integrity.
41
+ 2. Base Review (always):
42
+ - Read each artifact.
43
+ - Verify against the **Checklist**.
44
+ - Verify Test Coverage (6 Rules).
45
+ 3. Selected Analyses:
46
+ - Run each analysis the user chose. Prefer running them **in parallel**.
47
+ - **Fetch the template from quoin** once with `quoin write --types SpecReview` — use its
48
+ skeleton + schema as the contract (do not invent the format).
49
+ - Write **one `SpecReview` document per analysis** to `spec/reviews/<analysis>.md`
50
+ (plus `spec/reviews/base.md` for the base checklist). Findings go in a validated
51
+ `## Findings` table (`| ID | Severity | Summary | Refs |`, `FND-NNN` ids, Severity ∈
52
+ `low`/`medium`/`high`).
53
+ 4. Validate + record:
54
+ - Run `quire validate --scope <repo> "spec/**/*.md"` and fix any errors.
55
+ - The docs sync into filament-core as `SpecReview` artifacts; do not proceed to
56
+ implementation until reviewed.
57
+
58
+ ## Enforced runs (workflow mode)
59
+
60
+ `quoin review` drives this through `ix-flow`, which **records the chosen set and hard-blocks
61
+ acceptance until every selected analysis has produced a validated `SpecReview` doc** (the
62
+ `selected_analyses_covered` gate). Use it when you want the choice enforced rather than
63
+ trusted to discipline. The per-analysis `SpecReview` structure + the findings table are
64
+ defined in the workflow skill (`workflow-assets/skills/review/SKILL.md`).
65
+
66
+ ## Common Issues
67
+
68
+ - Vague Criteria: "Fast", "User-friendly". -> Make measurable.
69
+ - Missing Errors: Only happy path. -> Add error modes.
70
+ - No Coverage: AC without TC. -> Add tests.
71
+ - Inconsistent IDs: `US-1` instead of `US-001`. -> Fix formatting.
@@ -0,0 +1,50 @@
1
+ # Requirements Review Checklist
2
+
3
+ ## ID Format and Uniqueness
4
+ - [ ] All user stories use `US-XXX` format (3-digit).
5
+ - [ ] All functional requirements use `FR-XXX` format.
6
+ - [ ] All test cases use `TC-XXX` format.
7
+ - [ ] Acceptance criteria use `{PARENT}-AC-N`.
8
+ - [ ] Options use `{PARENT}-OPT-{LETTER}`.
9
+ - [ ] Constraints use `{PARENT}-CON-N`.
10
+ - [ ] No duplicate IDs. IDs are sequential.
11
+
12
+ ## User Story Quality
13
+ - [ ] Uses "As a/I want/So that" format.
14
+ - [ ] >= 2 acceptance criteria (Given/When/Then).
15
+ - [ ] Criteria are testable.
16
+ - [ ] Options document trade-offs.
17
+ - [ ] Constraints include rationale.
18
+ - [ ] Dependencies linked.
19
+ - [ ] Priority specified.
20
+ - [ ] User value focus (not implementation).
21
+
22
+ ## Functional Requirement Quality
23
+ - [ ] Description clear/specific.
24
+ - [ ] Related US linked.
25
+ - [ ] Inputs defined (type, validation).
26
+ - [ ] Outputs defined (type).
27
+ - [ ] Behavior detailed.
28
+ - [ ] Options document impact.
29
+ - [ ] Constraints document rationale/validation.
30
+ - [ ] Error conditions documented (codes).
31
+ - [ ] Performance targets specific.
32
+ - [ ] Security addressed.
33
+ - [ ] Criteria verifiable.
34
+ - [ ] Dependencies documented.
35
+
36
+ ## Test Coverage Quality (Six Rules)
37
+ - [ ] Coverage: Every AC has >= 1 TC.
38
+ - [ ] Option Permutation: All valid combinations tested.
39
+ - [ ] Constraint Boundary: All boundaries tested (min, max, over, under).
40
+ - [ ] Error Path: All error conditions tested.
41
+ - [ ] State Transition: All transitions tested (if applicable).
42
+ - [ ] Edge Case: Edge cases identified/tested.
43
+ - [ ] TC fields complete (Type, Priority, Trace).
44
+
45
+ ## Cross-Referencing
46
+ - [ ] FR links to US.
47
+ - [ ] TC links to AC.
48
+ - [ ] Full IDs used.
49
+ - [ ] Links valid.
50
+ - [ ] Terminology consistent.