@agent-ix/quoin 0.22.5 → 0.24.1

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 (398) hide show
  1. package/README.md +8 -258
  2. package/bin/launcher.js +138 -0
  3. package/package.json +22 -119
  4. package/.agents/plugins/marketplace.json +0 -14
  5. package/.claude-plugin/marketplace.json +0 -16
  6. package/.claude-plugin/plugin.json +0 -8
  7. package/.codex-plugin/plugin.json +0 -27
  8. package/.github/plugin/marketplace.json +0 -16
  9. package/bin/quoin.js +0 -21
  10. package/default-modules.yaml +0 -107
  11. package/dist/advisor/advise.d.ts +0 -199
  12. package/dist/advisor/advise.d.ts.map +0 -1
  13. package/dist/advisor/index.d.ts +0 -10
  14. package/dist/advisor/index.d.ts.map +0 -1
  15. package/dist/advisor/methods.d.ts +0 -60
  16. package/dist/advisor/methods.d.ts.map +0 -1
  17. package/dist/advisor-BkgwDKvQ.js +0 -63
  18. package/dist/assurance/graph.d.ts +0 -87
  19. package/dist/assurance/graph.d.ts.map +0 -1
  20. package/dist/assurance/index.d.ts +0 -9
  21. package/dist/assurance/index.d.ts.map +0 -1
  22. package/dist/assurance/render.d.ts +0 -3
  23. package/dist/assurance/render.d.ts.map +0 -1
  24. package/dist/auditor/audit.d.ts +0 -146
  25. package/dist/auditor/audit.d.ts.map +0 -1
  26. package/dist/auditor/combinatorial.d.ts +0 -53
  27. package/dist/auditor/combinatorial.d.ts.map +0 -1
  28. package/dist/auditor/index.d.ts +0 -9
  29. package/dist/auditor/index.d.ts.map +0 -1
  30. package/dist/auditor-C3bSmPD_.js +0 -340
  31. package/dist/base-CqKNs2Kd.js +0 -137
  32. package/dist/base.d.ts +0 -23
  33. package/dist/base.d.ts.map +0 -1
  34. package/dist/catalog.d.ts +0 -33
  35. package/dist/catalog.d.ts.map +0 -1
  36. package/dist/cli.d.ts +0 -61
  37. package/dist/cli.d.ts.map +0 -1
  38. package/dist/cli.js +0 -34
  39. package/dist/commands/advise.d.ts +0 -16
  40. package/dist/commands/advise.d.ts.map +0 -1
  41. package/dist/commands/advise.js +0 -234
  42. package/dist/commands/assurance.d.ts +0 -14
  43. package/dist/commands/assurance.d.ts.map +0 -1
  44. package/dist/commands/assurance.js +0 -204
  45. package/dist/commands/catalog/index.d.ts +0 -2
  46. package/dist/commands/catalog/index.d.ts.map +0 -1
  47. package/dist/commands/catalog/index.js +0 -2
  48. package/dist/commands/catalog/list.d.ts +0 -11
  49. package/dist/commands/catalog/list.d.ts.map +0 -1
  50. package/dist/commands/catalog/list.js +0 -22
  51. package/dist/commands/catalog/methods.d.ts +0 -12
  52. package/dist/commands/catalog/methods.d.ts.map +0 -1
  53. package/dist/commands/catalog/methods.js +0 -43
  54. package/dist/commands/catalog/show.d.ts +0 -13
  55. package/dist/commands/catalog/show.d.ts.map +0 -1
  56. package/dist/commands/catalog/show.js +0 -25
  57. package/dist/commands/catalog/validate.d.ts +0 -10
  58. package/dist/commands/catalog/validate.d.ts.map +0 -1
  59. package/dist/commands/catalog/validate.js +0 -27
  60. package/dist/commands/completeness.d.ts +0 -16
  61. package/dist/commands/completeness.d.ts.map +0 -1
  62. package/dist/commands/completeness.js +0 -49
  63. package/dist/commands/config/doctor.d.ts +0 -7
  64. package/dist/commands/config/doctor.d.ts.map +0 -1
  65. package/dist/commands/config/doctor.js +0 -15
  66. package/dist/commands/config/edit.d.ts +0 -7
  67. package/dist/commands/config/edit.d.ts.map +0 -1
  68. package/dist/commands/config/edit.js +0 -13
  69. package/dist/commands/config/get.d.ts +0 -11
  70. package/dist/commands/config/get.d.ts.map +0 -1
  71. package/dist/commands/config/get.js +0 -20
  72. package/dist/commands/config/index.d.ts +0 -2
  73. package/dist/commands/config/index.d.ts.map +0 -1
  74. package/dist/commands/config/index.js +0 -2
  75. package/dist/commands/config/set.d.ts +0 -12
  76. package/dist/commands/config/set.d.ts.map +0 -1
  77. package/dist/commands/config/set.js +0 -26
  78. package/dist/commands/evidence/affirm.d.ts +0 -17
  79. package/dist/commands/evidence/affirm.d.ts.map +0 -1
  80. package/dist/commands/evidence/affirm.js +0 -65
  81. package/dist/commands/evidence/audit.d.ts +0 -34
  82. package/dist/commands/evidence/audit.d.ts.map +0 -1
  83. package/dist/commands/evidence/audit.js +0 -107
  84. package/dist/commands/evidence/baseline.d.ts +0 -14
  85. package/dist/commands/evidence/baseline.d.ts.map +0 -1
  86. package/dist/commands/evidence/baseline.js +0 -89
  87. package/dist/commands/evidence/gc.d.ts +0 -13
  88. package/dist/commands/evidence/gc.d.ts.map +0 -1
  89. package/dist/commands/evidence/gc.js +0 -35
  90. package/dist/commands/evidence/index.d.ts +0 -8
  91. package/dist/commands/evidence/index.d.ts.map +0 -1
  92. package/dist/commands/evidence/index.js +0 -18
  93. package/dist/commands/evidence/inspect-mocks.d.ts +0 -16
  94. package/dist/commands/evidence/inspect-mocks.d.ts.map +0 -1
  95. package/dist/commands/evidence/inspect-mocks.js +0 -49
  96. package/dist/commands/evidence/record.d.ts +0 -22
  97. package/dist/commands/evidence/record.d.ts.map +0 -1
  98. package/dist/commands/evidence/record.js +0 -140
  99. package/dist/commands/matrix.d.ts +0 -14
  100. package/dist/commands/matrix.d.ts.map +0 -1
  101. package/dist/commands/matrix.js +0 -15
  102. package/dist/commands/measurement/index.d.ts +0 -7
  103. package/dist/commands/measurement/index.d.ts.map +0 -1
  104. package/dist/commands/measurement/index.js +0 -11
  105. package/dist/commands/measurement/record.d.ts +0 -10
  106. package/dist/commands/measurement/record.d.ts.map +0 -1
  107. package/dist/commands/measurement/record.js +0 -35
  108. package/dist/commands/module/ensure-defaults.d.ts +0 -8
  109. package/dist/commands/module/ensure-defaults.d.ts.map +0 -1
  110. package/dist/commands/module/ensure-defaults.js +0 -17
  111. package/dist/commands/module/index.d.ts +0 -2
  112. package/dist/commands/module/index.d.ts.map +0 -1
  113. package/dist/commands/module/index.js +0 -2
  114. package/dist/commands/module/install.d.ts +0 -11
  115. package/dist/commands/module/install.d.ts.map +0 -1
  116. package/dist/commands/module/install.js +0 -22
  117. package/dist/commands/module/list.d.ts +0 -8
  118. package/dist/commands/module/list.d.ts.map +0 -1
  119. package/dist/commands/module/list.js +0 -13
  120. package/dist/commands/module/remove.d.ts +0 -10
  121. package/dist/commands/module/remove.d.ts.map +0 -1
  122. package/dist/commands/module/remove.js +0 -16
  123. package/dist/commands/plugin/deprecation.d.ts +0 -10
  124. package/dist/commands/plugin/deprecation.d.ts.map +0 -1
  125. package/dist/commands/plugin/ensure-defaults.d.ts +0 -8
  126. package/dist/commands/plugin/ensure-defaults.d.ts.map +0 -1
  127. package/dist/commands/plugin/ensure-defaults.js +0 -12
  128. package/dist/commands/plugin/index.d.ts +0 -2
  129. package/dist/commands/plugin/index.d.ts.map +0 -1
  130. package/dist/commands/plugin/index.js +0 -2
  131. package/dist/commands/plugin/install.d.ts +0 -8
  132. package/dist/commands/plugin/install.d.ts.map +0 -1
  133. package/dist/commands/plugin/install.js +0 -12
  134. package/dist/commands/plugin/list.d.ts +0 -8
  135. package/dist/commands/plugin/list.d.ts.map +0 -1
  136. package/dist/commands/plugin/list.js +0 -12
  137. package/dist/commands/plugin/remove.d.ts +0 -8
  138. package/dist/commands/plugin/remove.d.ts.map +0 -1
  139. package/dist/commands/plugin/remove.js +0 -12
  140. package/dist/commands/report.d.ts +0 -15
  141. package/dist/commands/report.d.ts.map +0 -1
  142. package/dist/commands/report.js +0 -70
  143. package/dist/commands/review.d.ts +0 -14
  144. package/dist/commands/review.d.ts.map +0 -1
  145. package/dist/commands/review.js +0 -15
  146. package/dist/commands/to-plan.d.ts +0 -14
  147. package/dist/commands/to-plan.d.ts.map +0 -1
  148. package/dist/commands/to-plan.js +0 -15
  149. package/dist/commands/update.d.ts +0 -13
  150. package/dist/commands/update.d.ts.map +0 -1
  151. package/dist/commands/update.js +0 -34
  152. package/dist/commands/validate.d.ts +0 -13
  153. package/dist/commands/validate.d.ts.map +0 -1
  154. package/dist/commands/validate.js +0 -123
  155. package/dist/commands/write.d.ts +0 -16
  156. package/dist/commands/write.d.ts.map +0 -1
  157. package/dist/commands/write.js +0 -33
  158. package/dist/completeness/assess.d.ts +0 -82
  159. package/dist/completeness/assess.d.ts.map +0 -1
  160. package/dist/completeness/bundle.d.ts +0 -52
  161. package/dist/completeness/bundle.d.ts.map +0 -1
  162. package/dist/completeness/declarations.d.ts +0 -46
  163. package/dist/completeness/declarations.d.ts.map +0 -1
  164. package/dist/completeness/index.d.ts +0 -11
  165. package/dist/completeness/index.d.ts.map +0 -1
  166. package/dist/completeness/run.d.ts +0 -35
  167. package/dist/completeness/run.d.ts.map +0 -1
  168. package/dist/completeness-DamWradt.js +0 -228
  169. package/dist/config-schema-Dp-vlxuR.js +0 -13
  170. package/dist/config-schema.d.ts +0 -52
  171. package/dist/config-schema.d.ts.map +0 -1
  172. package/dist/deprecation-fRxUHoxv.js +0 -4
  173. package/dist/evidence/adapters/agent-eval.d.ts +0 -26
  174. package/dist/evidence/adapters/agent-eval.d.ts.map +0 -1
  175. package/dist/evidence/adapters/audit-script.d.ts +0 -25
  176. package/dist/evidence/adapters/audit-script.d.ts.map +0 -1
  177. package/dist/evidence/adapters/cargo-mutants.d.ts +0 -3
  178. package/dist/evidence/adapters/cargo-mutants.d.ts.map +0 -1
  179. package/dist/evidence/adapters/junit.d.ts +0 -17
  180. package/dist/evidence/adapters/junit.d.ts.map +0 -1
  181. package/dist/evidence/adapters/registry.d.ts +0 -63
  182. package/dist/evidence/adapters/registry.d.ts.map +0 -1
  183. package/dist/evidence/adapters/sarif.d.ts +0 -35
  184. package/dist/evidence/adapters/sarif.d.ts.map +0 -1
  185. package/dist/evidence/adapters/sbom.d.ts +0 -35
  186. package/dist/evidence/adapters/sbom.d.ts.map +0 -1
  187. package/dist/evidence/adapters/types.d.ts +0 -55
  188. package/dist/evidence/adapters/types.d.ts.map +0 -1
  189. package/dist/evidence/index.d.ts +0 -24
  190. package/dist/evidence/index.d.ts.map +0 -1
  191. package/dist/evidence/mock-inspection.d.ts +0 -16
  192. package/dist/evidence/mock-inspection.d.ts.map +0 -1
  193. package/dist/evidence/record.d.ts +0 -58
  194. package/dist/evidence/record.d.ts.map +0 -1
  195. package/dist/evidence/store.d.ts +0 -215
  196. package/dist/evidence/store.d.ts.map +0 -1
  197. package/dist/evidence/types.d.ts +0 -281
  198. package/dist/evidence/types.d.ts.map +0 -1
  199. package/dist/evidence-DD0CHzJ0.js +0 -533
  200. package/dist/flow-command-BfFNY0Rv.js +0 -88
  201. package/dist/flow-command.d.ts +0 -25
  202. package/dist/flow-command.d.ts.map +0 -1
  203. package/dist/flows.d.ts +0 -7
  204. package/dist/flows.d.ts.map +0 -1
  205. package/dist/hooks/command-not-found.d.ts +0 -23
  206. package/dist/hooks/command-not-found.d.ts.map +0 -1
  207. package/dist/hooks/command-not-found.js +0 -8
  208. package/dist/index.d.ts +0 -12
  209. package/dist/index.d.ts.map +0 -1
  210. package/dist/index.js +0 -10
  211. package/dist/measurement/compare.d.ts +0 -4
  212. package/dist/measurement/compare.d.ts.map +0 -1
  213. package/dist/measurement/index.d.ts +0 -9
  214. package/dist/measurement/index.d.ts.map +0 -1
  215. package/dist/measurement/plans.d.ts +0 -4
  216. package/dist/measurement/plans.d.ts.map +0 -1
  217. package/dist/measurement/portfolio.d.ts +0 -48
  218. package/dist/measurement/portfolio.d.ts.map +0 -1
  219. package/dist/measurement/profiles.d.ts +0 -9
  220. package/dist/measurement/profiles.d.ts.map +0 -1
  221. package/dist/measurement/report.d.ts +0 -44
  222. package/dist/measurement/report.d.ts.map +0 -1
  223. package/dist/measurement/store.d.ts +0 -7
  224. package/dist/measurement/store.d.ts.map +0 -1
  225. package/dist/measurement/types.d.ts +0 -83
  226. package/dist/measurement/types.d.ts.map +0 -1
  227. package/dist/measurement/validate.d.ts +0 -9
  228. package/dist/measurement/validate.d.ts.map +0 -1
  229. package/dist/measurement-CzB74Q07.js +0 -595
  230. package/dist/modules-ez9httBA.js +0 -23
  231. package/dist/modules.d.ts +0 -10
  232. package/dist/modules.d.ts.map +0 -1
  233. package/dist/org.d.ts +0 -61
  234. package/dist/org.d.ts.map +0 -1
  235. package/dist/plugins-C-ta0llj.js +0 -77
  236. package/dist/plugins.d.ts +0 -13
  237. package/dist/plugins.d.ts.map +0 -1
  238. package/dist/quire/contract.d.ts +0 -87
  239. package/dist/quire/contract.d.ts.map +0 -1
  240. package/dist/quire/exec.d.ts +0 -66
  241. package/dist/quire/exec.d.ts.map +0 -1
  242. package/dist/quire/index.d.ts +0 -12
  243. package/dist/quire/index.d.ts.map +0 -1
  244. package/dist/quire/types.d.ts +0 -415
  245. package/dist/quire/types.d.ts.map +0 -1
  246. package/dist/quire/validate.d.ts +0 -34
  247. package/dist/quire/validate.d.ts.map +0 -1
  248. package/dist/quire-D8tCpgyA.js +0 -4961
  249. package/dist/schemas/coverage-v1.schema.json +0 -1111
  250. package/dist/schemas/properties-v1.schema.json +0 -159
  251. package/dist/store--2sAv12X.js +0 -219
  252. package/dist/validators/gates.d.ts +0 -18
  253. package/dist/validators/gates.d.ts.map +0 -1
  254. package/dist/validators/index.d.ts +0 -2
  255. package/dist/validators/index.d.ts.map +0 -1
  256. package/dist/version-Dg0e6CZU.js +0 -17
  257. package/dist/version.d.ts +0 -3
  258. package/dist/version.d.ts.map +0 -1
  259. package/dist/write-DElwS9xc.js +0 -157
  260. package/dist/write.d.ts +0 -28
  261. package/dist/write.d.ts.map +0 -1
  262. package/skills/assurance-status-report/SKILL.md +0 -135
  263. package/skills/assurance-status-report/references/report-contract.md +0 -110
  264. package/skills/gap-analysis/SKILL.md +0 -111
  265. package/skills/gap-analysis/references/step-1-target-selection.md +0 -53
  266. package/skills/gap-analysis/references/step-2-plan-completion.md +0 -49
  267. package/skills/gap-analysis/references/step-3-matrix-verification.md +0 -147
  268. package/skills/gap-analysis/references/step-4-underspecified-code.md +0 -63
  269. package/skills/gap-analysis/references/step-5-semantic-review.md +0 -51
  270. package/skills/gap-analysis/references/step-6-specreview-artifact.md +0 -107
  271. package/skills/spec-app-review/SKILL.md +0 -51
  272. package/skills/spec-app-review/references/checklist.md +0 -197
  273. package/skills/spec-architecture-evaluation/SKILL.md +0 -30
  274. package/skills/spec-correctness/SKILL.md +0 -96
  275. package/skills/spec-correctness/assets/strategy-table.md +0 -101
  276. package/skills/spec-correctness/assets/templates/fast-check.ts.md +0 -169
  277. package/skills/spec-correctness/assets/templates/hypothesis.py.md +0 -156
  278. package/skills/spec-correctness/assets/templates/proptest.rs.md +0 -147
  279. package/skills/spec-correctness/references/step-0-scope-and-harness.md +0 -94
  280. package/skills/spec-correctness/references/step-1-census.md +0 -53
  281. package/skills/spec-correctness/references/step-2-clause-grounding.md +0 -159
  282. package/skills/spec-correctness/references/step-3-strategy-selection.md +0 -85
  283. package/skills/spec-correctness/references/step-4-generate-tests.md +0 -117
  284. package/skills/spec-correctness/references/step-5-second-pass.md +0 -81
  285. package/skills/spec-correctness/references/step-6-review-artifact.md +0 -134
  286. package/skills/spec-correctness/references/step-7-report-and-handoff.md +0 -102
  287. package/skills/spec-dependency-analysis/SKILL.md +0 -90
  288. package/skills/spec-ears-analysis/SKILL.md +0 -102
  289. package/skills/spec-evidence-analysis/SKILL.md +0 -156
  290. package/skills/spec-failure-domain-analysis/SKILL.md +0 -59
  291. package/skills/spec-fuzz/SKILL.md +0 -132
  292. package/skills/spec-fuzz/assets/templates/atheris.py.md +0 -74
  293. package/skills/spec-fuzz/assets/templates/cargo-fuzz.rs.md +0 -83
  294. package/skills/spec-fuzz/assets/templates/fast-check.ts.md +0 -76
  295. package/skills/spec-fuzz/references/step-0-scope-and-harness.md +0 -51
  296. package/skills/spec-fuzz/references/step-1-select-obligations.md +0 -47
  297. package/skills/spec-fuzz/references/step-2-ground-entry-point.md +0 -55
  298. package/skills/spec-fuzz/references/step-3-emit-targets.md +0 -65
  299. package/skills/spec-fuzz/references/step-4-report.md +0 -56
  300. package/skills/spec-ideation/SKILL.md +0 -46
  301. package/skills/spec-integrity-analysis/SKILL.md +0 -62
  302. package/skills/spec-matrix/SKILL.md +0 -186
  303. package/skills/spec-matrix/assets/test-cases/TC-001.md +0 -35
  304. package/skills/spec-matrix/assets/test-cases/TC-002.md +0 -37
  305. package/skills/spec-matrix/assets/test-cases/TC-006.md +0 -50
  306. package/skills/spec-matrix/assets/test-matrix-example.md +0 -104
  307. package/skills/spec-matrix/assets/test-matrix-template.md +0 -123
  308. package/skills/spec-matrix/workflow-assets/dist/index.d.ts +0 -146
  309. package/skills/spec-matrix/workflow-assets/dist/index.d.ts.map +0 -1
  310. package/skills/spec-matrix/workflow-assets/dist/index.js +0 -7525
  311. package/skills/spec-matrix/workflow-assets/dist/invariants.d.ts +0 -6
  312. package/skills/spec-matrix/workflow-assets/dist/invariants.d.ts.map +0 -1
  313. package/skills/spec-matrix/workflow-assets/skills/matrix/SKILL.md +0 -35
  314. package/skills/spec-matrix/workflow-assets/skills/matrix/scripts/invariants.js +0 -1
  315. package/skills/spec-matrix/workflow-assets/skills/matrix/templates/report/default.md +0 -30
  316. package/skills/spec-matrix/workflow-assets/skills/matrix/workflows/matrix/def.yaml +0 -82
  317. package/skills/spec-object-review/SKILL.md +0 -125
  318. package/skills/spec-object-review/references/object-type-guide.md +0 -118
  319. package/skills/spec-review/SKILL.md +0 -92
  320. package/skills/spec-review/references/checklist.md +0 -50
  321. package/skills/spec-review/workflow-assets/dist/index.d.ts +0 -146
  322. package/skills/spec-review/workflow-assets/dist/index.d.ts.map +0 -1
  323. package/skills/spec-review/workflow-assets/dist/index.js +0 -7525
  324. package/skills/spec-review/workflow-assets/dist/invariants.d.ts +0 -6
  325. package/skills/spec-review/workflow-assets/dist/invariants.d.ts.map +0 -1
  326. package/skills/spec-review/workflow-assets/skills/review/SKILL.md +0 -96
  327. package/skills/spec-review/workflow-assets/skills/review/scripts/invariants.js +0 -61
  328. package/skills/spec-review/workflow-assets/skills/review/workflows/review/def.yaml +0 -68
  329. package/skills/spec-risk-complexity-analysis/SKILL.md +0 -92
  330. package/skills/spec-scope-boundary-analysis/SKILL.md +0 -101
  331. package/skills/spec-security-analysis/SKILL.md +0 -84
  332. package/skills/spec-security-analysis/assets/security-analysis-example.md +0 -89
  333. package/skills/spec-security-analysis/assets/security-analysis-template.md +0 -73
  334. package/skills/spec-security-analysis/references/component-type-mapping.md +0 -161
  335. package/skills/spec-security-analysis/references/gdpr/ChII-Principles.md +0 -58
  336. package/skills/spec-security-analysis/references/gdpr/ChIII-DataSubjectRights.md +0 -84
  337. package/skills/spec-security-analysis/references/gdpr/ChIV-ControllerProcessor.md +0 -83
  338. package/skills/spec-security-analysis/references/gdpr/ChV-DataTransfers.md +0 -62
  339. package/skills/spec-security-analysis/references/gdpr/index.md +0 -54
  340. package/skills/spec-security-analysis/references/iso27001/A5-OrganizationalControls.md +0 -64
  341. package/skills/spec-security-analysis/references/iso27001/A6-PeopleControls.md +0 -30
  342. package/skills/spec-security-analysis/references/iso27001/A7-PhysicalControls.md +0 -35
  343. package/skills/spec-security-analysis/references/iso27001/A8-TechnologicalControls.md +0 -66
  344. package/skills/spec-security-analysis/references/iso27001/index.md +0 -43
  345. package/skills/spec-security-analysis/references/nist-800-53/AC-AccessControl.md +0 -57
  346. package/skills/spec-security-analysis/references/nist-800-53/AU-AuditAccountability.md +0 -49
  347. package/skills/spec-security-analysis/references/nist-800-53/CM-ConfigurationManagement.md +0 -36
  348. package/skills/spec-security-analysis/references/nist-800-53/IA-IdentificationAuthentication.md +0 -44
  349. package/skills/spec-security-analysis/references/nist-800-53/SA-SystemServicesAcquisition.md +0 -50
  350. package/skills/spec-security-analysis/references/nist-800-53/SC-SystemCommunications.md +0 -53
  351. package/skills/spec-security-analysis/references/nist-800-53/SI-SystemInformationIntegrity.md +0 -52
  352. package/skills/spec-security-analysis/references/nist-800-53/index.md +0 -58
  353. package/skills/spec-security-analysis/references/owasp-asvs/V1-Architecture.md +0 -33
  354. package/skills/spec-security-analysis/references/owasp-asvs/V10-MaliciousCode.md +0 -33
  355. package/skills/spec-security-analysis/references/owasp-asvs/V11-BusinessLogic.md +0 -32
  356. package/skills/spec-security-analysis/references/owasp-asvs/V12-Files.md +0 -34
  357. package/skills/spec-security-analysis/references/owasp-asvs/V13-API.md +0 -34
  358. package/skills/spec-security-analysis/references/owasp-asvs/V14-Configuration.md +0 -35
  359. package/skills/spec-security-analysis/references/owasp-asvs/V2-Authentication.md +0 -36
  360. package/skills/spec-security-analysis/references/owasp-asvs/V3-SessionManagement.md +0 -35
  361. package/skills/spec-security-analysis/references/owasp-asvs/V4-AccessControl.md +0 -39
  362. package/skills/spec-security-analysis/references/owasp-asvs/V5-Validation.md +0 -37
  363. package/skills/spec-security-analysis/references/owasp-asvs/V6-Cryptography.md +0 -34
  364. package/skills/spec-security-analysis/references/owasp-asvs/V7-ErrorLogging.md +0 -37
  365. package/skills/spec-security-analysis/references/owasp-asvs/V8-DataProtection.md +0 -34
  366. package/skills/spec-security-analysis/references/owasp-asvs/V9-Communication.md +0 -32
  367. package/skills/spec-security-analysis/references/owasp-asvs/index.md +0 -59
  368. package/skills/spec-security-analysis/references/soc2/CC1-ControlEnvironment.md +0 -31
  369. package/skills/spec-security-analysis/references/soc2/CC2-CommunicationInformation.md +0 -27
  370. package/skills/spec-security-analysis/references/soc2/CC3-RiskAssessment.md +0 -29
  371. package/skills/spec-security-analysis/references/soc2/CC4-MonitoringActivities.md +0 -27
  372. package/skills/spec-security-analysis/references/soc2/CC5-ControlActivities.md +0 -28
  373. package/skills/spec-security-analysis/references/soc2/CC6-LogicalPhysicalAccess.md +0 -45
  374. package/skills/spec-security-analysis/references/soc2/CC7-SystemOperations.md +0 -42
  375. package/skills/spec-security-analysis/references/soc2/CC8-ChangeManagement.md +0 -32
  376. package/skills/spec-security-analysis/references/soc2/CC9-RiskMitigation.md +0 -34
  377. package/skills/spec-security-analysis/references/soc2/index.md +0 -46
  378. package/skills/spec-security-analysis/references/standards-index.md +0 -46
  379. package/skills/spec-to-plan/SKILL.md +0 -88
  380. package/skills/spec-to-plan/references/step-0-plan-selection.md +0 -121
  381. package/skills/spec-to-plan/references/step-1-analysis.md +0 -88
  382. package/skills/spec-to-plan/references/step-2-test-plan.md +0 -43
  383. package/skills/spec-to-plan/references/step-3-execution-plan.md +0 -218
  384. package/skills/spec-to-plan/workflow-assets/dist/index.d.ts +0 -146
  385. package/skills/spec-to-plan/workflow-assets/dist/index.d.ts.map +0 -1
  386. package/skills/spec-to-plan/workflow-assets/dist/index.js +0 -7525
  387. package/skills/spec-to-plan/workflow-assets/dist/invariants.d.ts +0 -6
  388. package/skills/spec-to-plan/workflow-assets/dist/invariants.d.ts.map +0 -1
  389. package/skills/spec-to-plan/workflow-assets/skills/to-plan/SKILL.md +0 -35
  390. package/skills/spec-to-plan/workflow-assets/skills/to-plan/scripts/invariants.js +0 -1
  391. package/skills/spec-to-plan/workflow-assets/skills/to-plan/templates/implementation-plan/default.md +0 -44
  392. package/skills/spec-to-plan/workflow-assets/skills/to-plan/workflows/to-plan/def.yaml +0 -85
  393. package/skills/specify/SKILL.md +0 -154
  394. package/skills/specify/assets/app-spec-template.md +0 -143
  395. package/skills/specify/assets/spec-template.md +0 -299
  396. package/skills/specify/references/integration-tests.md +0 -72
  397. package/skills/specify/references/us-to-fr.md +0 -40
  398. package/skills/specify/references/writing-good-requirements.md +0 -61
@@ -1,135 +0,0 @@
1
- ---
2
- name: assurance-status-report
3
- description: Produce an evidence-backed status report for a Quoin/Quire epic, phase, or assurance campaign. Use when asked for progress, percent complete, before/after metrics, completed-ticket inventory, open-work classification, or readiness for the next phase. The workflow is read-only and does not comment on, close, or modify tickets or repositories.
4
- ---
5
-
6
- # Assurance Status Report
7
-
8
- Report what the retained evidence proves about a named goal. Use Quoin for
9
- measurement meaning and history, Quire for producer provenance, git for local
10
- state, and GitHub for current ticket and promotion state. Do not recreate their
11
- analysis in the skill.
12
-
13
- Read [references/report-contract.md](references/report-contract.md) before
14
- assembling the report.
15
-
16
- ## Boundary
17
-
18
- This workflow is read-only. It may inspect repositories, retained evidence, and
19
- remote ticket state. It must not run measurement producers, update baselines,
20
- modify evidence, push branches, or create/comment/close/reopen issues or pull
21
- requests unless the user separately authorizes that mutation.
22
-
23
- A closed ticket is workflow state, not proof of completion. Match each claimed
24
- result to its acceptance evidence, promoted commit, and relevant current-state
25
- check.
26
-
27
- ## Inputs
28
-
29
- Establish these before collecting evidence:
30
-
31
- - the goal, epic, phase, or campaign being reported;
32
- - repositories and tickets in scope;
33
- - work the user explicitly excluded;
34
- - the baseline and current endpoint; and
35
- - whether the user also wants an intermediate phase boundary.
36
-
37
- If no baseline is named, use the earliest retained collection explicitly linked
38
- by the target epic. Use the latest compatible retained collection as current.
39
- State that selection instead of silently choosing favorable snapshots.
40
-
41
- ## Collect exact evidence
42
-
43
- ### Repository state
44
-
45
- For every participating repository, record:
46
-
47
- ```bash
48
- git rev-parse HEAD
49
- git status --porcelain
50
- git remote get-url origin
51
- ```
52
-
53
- Resolve revisions to full 40-character SHAs. Use the canonical remote and a
54
- versioned, read-only GitHub query to confirm current default-branch and commit
55
- reachability, for example:
56
-
57
- ```bash
58
- gh api --header 'X-GitHub-Api-Version: 2022-11-28' \
59
- repos/OWNER/REPO/commits/FULL_SHA
60
- ```
61
-
62
- Validate required response fields rather than assuming a successful command
63
- returned the requested object. Record dirty, unreachable, ambiguous, or
64
- wrong-origin state as a limitation; never normalize it to clean.
65
-
66
- ### Tool and measurement state
67
-
68
- Use existing machine-readable interfaces:
69
-
70
- ```bash
71
- quoin report --format json
72
- quoin report --series METRIC --format json
73
- quoin report --since FULL_BASELINE_REVISION --format json
74
- quire provenance --json
75
- ```
76
-
77
- Use `quoin report` to discover active MeasurementPlans and retained values. Use
78
- the series or comparison view for historical values; do not scrape rendered
79
- human output when JSON exists. Confirm Quire's provenance schema, full CLI and
80
- engine revisions, clean state, and required capabilities before attributing a
81
- measurement to it.
82
-
83
- Record the exact collection id, timestamp, source revision, corpus revision,
84
- tool identity/version, configuration digest, definition version, and population
85
- identity supporting each reported value. If the repository has a verification
86
- stack attestation, report its lock and executable digests.
87
-
88
- Do not regenerate evidence merely to answer a status question. A new run changes
89
- the evidence state and requires separate authorization.
90
-
91
- ### Ticket and promotion state
92
-
93
- Use versioned read-only GitHub REST or GraphQL queries. For each issue capture at
94
- least number, title, state, URL, and closed time. For each delivery pull request
95
- capture state, base/head branches, merge time, merge commit, and URL. Confirm the
96
- current default-branch SHA separately.
97
-
98
- Follow relationships from the target epic and its retained implementation
99
- comments. Do not equate “mentioned nearby” with “child.” Classify every remaining
100
- item as blocking, non-blocking, downstream, excluded, or unknown and state the
101
- evidence for that disposition.
102
-
103
- ## Interpret without hiding drift
104
-
105
- Define every project-specific term before its first use in the metrics section.
106
- Derive definitions from the active MeasurementPlan or other versioned contract.
107
- At minimum define any use of finding, controlled case, differential pair,
108
- localization, L1/L2/L3, actionability, span grounding, safe refusal, Tier 1,
109
- Tier 2, ratchet, drift mutation, comparability, or fail closed.
110
-
111
- For every percentage, report its numerator and denominator. Express rate changes
112
- as percentage points. Compare baseline and current numerically only when their
113
- definition versions and population identities are compatible. If either moved,
114
- show both values and explain the change, but mark the delta incomparable.
115
-
116
- Keep historical metrics visible when a stronger successor exists. Explain why
117
- the successor is more decision-relevant; do not relabel old evidence under the
118
- new definition.
119
-
120
- If the user asks for percent complete, use authored task weights when present.
121
- Otherwise report the unweighted count of proven-complete in-scope tasks and say
122
- that this is the method. Present verification and promotion gates separately so
123
- a high task percentage cannot conceal an unverified result.
124
-
125
- ## Report and stop
126
-
127
- Follow the ordering in the report contract: status, definitions, metrics,
128
- completed work, open work, drift controls, limitations, and progress judgment.
129
- Lead with whether the named goal is complete, progressing, at risk, blocked, or
130
- not started, but put the glossary before the first detailed metric use.
131
-
132
- Link to the exact retained collections, issues, pull requests, and promoted
133
- commits. Distinguish evidence observed now from historical evidence retained by
134
- the campaign. If required evidence is missing or incompatible, say
135
- `unknown` or `not_computed` and identify what would resolve it.
@@ -1,110 +0,0 @@
1
- # Assurance status report contract
2
-
3
- Use this contract for a detailed report. Short status requests may compress
4
- sections, but they retain the same evidence and comparison rules.
5
-
6
- ## Evidence states
7
-
8
- - **Proven:** Direct current or retained evidence satisfies the requirement.
9
- - **Contradicted:** Direct evidence shows the requirement is not satisfied.
10
- - **Incomplete:** Some required evidence exists, but the full requirement is not
11
- demonstrated.
12
- - **Missing:** No authoritative evidence was found.
13
- - **Incomparable:** Values exist, but their definitions or populations do not
14
- permit a numeric delta.
15
-
16
- Never turn incomplete, missing, or incomparable evidence into zero, green, or
17
- complete.
18
-
19
- ## Required order
20
-
21
- ### 1. Executive status
22
-
23
- Name the goal, current disposition, as-of time and timezone, current promoted
24
- revision, scope boundary, and progress method. Distinguish completion of the
25
- named phase from progress of the larger program.
26
-
27
- ### 2. Definitions
28
-
29
- Define each project-specific term before the metrics table. Definitions cite the
30
- active versioned contract. Prefer plain language, then state the exact counting
31
- rule where it matters.
32
-
33
- Examples of distinctions that must remain visible:
34
-
35
- - localization identifies the correct place; it does not prove the explanation
36
- or remedy is correct;
37
- - actionability-field presence does not prove guidance correctness;
38
- - safe refusal preserves uncertainty and does not count as an exact span;
39
- - a controlled-corpus result does not estimate ecosystem-wide precision; and
40
- - a closed ticket does not by itself prove its acceptance criteria.
41
-
42
- ### 3. Metric progression
43
-
44
- Use a table with these conceptual columns:
45
-
46
- | Metric | Baseline | Intermediate | Current | Delta | Comparability | Evidence |
47
- | --- | --- | --- | --- | --- | --- | --- |
48
-
49
- Every ratio displays `matched/examined` beside the percentage. Each row retains
50
- the metric definition version and population identity, either inline or in its
51
- evidence link. Use `—` for a deliberately absent intermediate snapshot and
52
- `not_computed: REASON` for an unavailable value.
53
-
54
- Do not calculate a delta when:
55
-
56
- - the definition version changed;
57
- - the applicable population was redefined;
58
- - the source or corpus identity cannot be proved;
59
- - either value is not computed; or
60
- - a producer or required capability changed without an accepted comparison.
61
-
62
- When the population merely grows under the same contract, report both the count
63
- change and the rate change. A rate decline with a larger numerator can be scope
64
- growth rather than a product regression; explain which occurred.
65
-
66
- ### 4. Completed work
67
-
68
- Enumerate every in-scope ticket/task with title, repository, final state, delivery
69
- PR or commit, and the evidence that proves acceptance. Group by workstream when
70
- the list is long. Separately enumerate promotion PRs and exact merge commits.
71
-
72
- ### 5. Open work
73
-
74
- Enumerate unresolved items and assign exactly one disposition:
75
-
76
- - **blocking:** prevents the named goal;
77
- - **non-blocking:** retained limitation that does not prevent this goal;
78
- - **downstream:** belongs to a later goal or phase;
79
- - **excluded:** explicitly outside the user's scope; or
80
- - **unknown:** relationship or impact is not proven.
81
-
82
- Do not omit open work merely because the named phase is complete.
83
-
84
- ### 6. Drift controls
85
-
86
- Report the guard and its proof for each relevant drift class: repository,
87
- submodule, tool/engine, executable bytes, package resolution, toolchain, workflow
88
- action, container, schema, configuration, corpus, metric definition, evidence
89
- overlay, and promotion topology. Distinguish a guard observed in code from a
90
- mutation test proving it fails before governed execution.
91
-
92
- ### 7. Limitations and judgment
93
-
94
- State remaining evidence limitations, then answer whether the effort is moving
95
- toward the goal and why. Use one of:
96
-
97
- - **complete** — every requirement is proven and no in-scope work remains;
98
- - **on track** — incomplete, with no current blocking contradiction;
99
- - **at risk** — progress exists, but a named unresolved risk threatens the goal;
100
- - **blocked** — a named blocker prevents meaningful progress; or
101
- - **not started** — no implementation evidence exists.
102
-
103
- Close with the next decision or evidence-gathering point. Do not suggest starting
104
- explicitly excluded work.
105
-
106
- ## Read-only rule
107
-
108
- Producing the report does not authorize ticket comments, issue state changes,
109
- branch updates, evidence regeneration, baseline updates, or new external
110
- messages. Ask separately before any such mutation.
@@ -1,111 +0,0 @@
1
- ---
2
- name: gap-analysis
3
- description: Verify a targeted plan is complete and validated — every task done, the Test
4
- Matrix backed by real tracking tags in tests, and code fully traced to spec (flagging
5
- underspecified code with no owning requirement). Optional semantic review checks that
6
- intent↔test↔code actually agree. Emits a quire-validated SpecReview artifact to
7
- reviews/YY-MM-DD-<slug>.md.
8
- ---
9
-
10
- # Gap Analysis
11
-
12
- Use this skill as a **post-implementation verification gate** for one targeted plan.
13
- It answers three questions and, on request, a fourth:
14
-
15
- 1. **Is the plan done?** Every `Task` in the targeted plan bundle is `status: done`.
16
- 2. **Is the Test Matrix real?** Every Test Case in the matrix is backed by an actual test
17
- carrying a matching **tracking tag** (`TC-xxx`, `FR-xxx-AC-x`) in the test code.
18
- 3. **Is anything unspecified?** Code/behavior exists with **no owning** StR/US/FR/NFR
19
- (the reverse, code→spec gap).
20
- 4. **(optional) Does intent match reality?** For each requirement↔test↔code triple — does
21
- the test validate the requirement's *intent*, does the test actually exercise the code,
22
- and does the code match the requirement's intent.
23
-
24
- The result is a single **quire-validated `SpecReview`** document (`analysis: gap-analysis`)
25
- written to `reviews/YY-MM-DD-<slug>.md`, with a **Verdict** (PASS / CONDITIONAL / FAIL)
26
- and a validated **Findings** table.
27
-
28
- ## When to use
29
-
30
- - After `implement-plan` (or any implementation effort) to confirm a plan is genuinely
31
- complete and verified before closing it.
32
- - To audit drift between spec, tests, and code for an existing component.
33
- - As a release/merge gate that produces a durable, traceable review artifact.
34
-
35
- This skill is **read-only over the codebase** — it inspects and reports; it does not fix
36
- code, edit the plan, or change the matrix. Its only write is the SpecReview artifact.
37
-
38
- ## Inputs
39
-
40
- - A target **plan bundle** `plan/<Plan-id>-<slug>/` (the user may name it; otherwise pick).
41
- - The component **spec** (`spec/spec.md` for `org`/`name`) and **Test Matrix**
42
- (`spec/matrix.md` or `spec/tests.md`).
43
- - The **source** and **test** trees of the component.
44
-
45
- ## Steps
46
-
47
- 0. **[Target selection](references/step-1-target-selection.md)**: Resolve the plan bundle,
48
- spec root, Test Matrix, and `org`/`component` for `ix://` URIs.
49
- 1. **[Plan completion](references/step-2-plan-completion.md)**: Assert every `Task` is
50
- `done`; report incomplete/blocked tasks and stale `plan.md` checkboxes.
51
- 2. **[Matrix verification](references/step-3-matrix-verification.md)**: Run
52
- `quire coverage --scope <root> --json` and interpret the report — unbacked rows, status
53
- lies, untracked tests, and the backed/total rollup. The reconciliation is the engine's;
54
- the severity and the verdict stay here. A repo whose module set declares no
55
- `traceability:` model falls back to a grep index, declared as such.
56
- 3. **[Underspecified code](references/step-4-underspecified-code.md)**: Find code/behavior
57
- with no owning requirement (reverse gap), plus stubs masquerading as complete.
58
- 4. **[Semantic review](references/step-5-semantic-review.md)** *(OPTIONAL — ask first)*:
59
- Judge intent↔test↔code agreement per requirement. Skip unless the user opts in.
60
- 5. **[SpecReview artifact](references/step-6-specreview-artifact.md)**: Write and validate
61
- the `SpecReview` to `reviews/YY-MM-DD-<slug>.md`.
62
-
63
- All steps required except Step 4, which is gated on user choice.
64
-
65
- > **`--scope` is the repository root, and must be passed explicitly.** Since quire-cli
66
- > v0.16.0 (quire-rs CR-045) the command derives **two roots** from it and never
67
- > interchanges them: spec documents are read from `<repo>/spec` only, trace tags from
68
- > the source tree at `<repo>` excluding `spec/`. A repo with no `spec/` exits with a
69
- > diagnostic naming the missing document root rather than scanning the whole tree, and a
70
- > matrix outside `spec/` (a fixture, a `plan/` copy) mints nothing. A relative glob
71
- > resolves under `--scope` only in scoped mode (no `--module`); with `--module` it
72
- > resolves against the process working directory, and an omitted `--scope` defaults to
73
- > `.` — so a run launched from a parent directory validates the **wrong tree** and exits
74
- > 0 for whatever it matched. Check `quire --version` ≥ 0.16.0 before relying on any of
75
- > this; ≤ 0.15.0 has the pre-split traversal semantics.
76
-
77
- ## The optional semantic review
78
-
79
- Steps 1–3 are mechanical and cheap. Step 4 is an expensive, judgment-heavy LLM pass.
80
- **Before running it**, ask the user explicitly (e.g. with a yes/no choice):
81
-
82
- > Run the optional semantic review (intent↔test↔code)? It's slower but verifies that tests
83
- > actually validate requirement intent and exercise real code.
84
-
85
- If yes, fan the work out (one subagent per FR or per area) for thoroughness. If no, note in
86
- the SpecReview's Coverage section that semantic review was skipped.
87
-
88
- ## Output
89
-
90
- A `SpecReview` (`spec-artifacts-process` archetype) at `<project_root>/reviews/YY-MM-DD-<slug>.md`:
91
-
92
- - Frontmatter `type: SpecReview`, `analysis: gap-analysis`, `id: SR-NNN`, `scope`,
93
- `review_set: subset`, and `relationships:` (`reviews` → the plan, `references` → the matrix).
94
- - Body: `## Summary`, `## Verdict` (PASS/CONDITIONAL/FAIL), `## Findings`
95
- (validated table `ID | Severity | Summary | Refs`), `## Coverage` (rollup).
96
-
97
- > **Note:** `reviews/` is at the **repo root** by deliberate choice for this skill, not
98
- > `spec/reviews/`. quire validation is path-agnostic, so this is fine.
99
-
100
- Validate before finishing:
101
-
102
- ```
103
- quire validate --scope <project_root> "reviews/**/*.md"
104
- ```
105
-
106
- ## Verdict rule
107
-
108
- - **FAIL** — any incomplete/blocked task, any matrix Test Case with no backing tagged test,
109
- or any `high`-severity finding.
110
- - **CONDITIONAL** — only `medium`/`low` findings (e.g. untracked tests, minor drift).
111
- - **PASS** — no gaps; record the single `FND-001 | low | No gaps found | -` row.
@@ -1,53 +0,0 @@
1
- # Step 1: Target Selection
2
-
3
- **Goal**: Resolve exactly what this run audits — one plan bundle, its spec, its Test
4
- Matrix — and the `ix://` identity used in the output artifact.
5
-
6
- ## Process
7
-
8
- ### 1. Resolve the target plan
9
-
10
- Mirror `spec-to-plan/references/step-0-plan-selection.md`:
11
-
12
- 1. **Named in context?** If the user passed a plan id (`Plan-002`) or one was established
13
- earlier this session, use it.
14
- 2. **Otherwise discover.** Glob `plan/*/plan.md`, read each frontmatter `id`/`title`/`status`,
15
- and present the list:
16
-
17
- ```
18
- Plans available to gap-analyze:
19
- - Plan-001 electron-hello core app (active)
20
- - Plan-002 packaging & distribution (active)
21
- ```
22
-
23
- Ask which one. One run targets **one** bundle.
24
-
25
- ### 2. Locate the spec and Test Matrix
26
-
27
- - **Spec root.** Single-repo: `spec/`. Multi-repo: `specs/<category>/<component>/spec/`.
28
- - **`org` / `component`.** Read from `spec/spec.md` frontmatter (`org`, `name`). These build
29
- the `ix://<org>/<component>/<id>` URIs used in the SpecReview `relationships:`.
30
- - **Test Matrix.** Look for `spec/matrix.md` first, then `spec/tests.md` (both names are in
31
- use across the ecosystem). Note its frontmatter `id` (e.g. `TestMatrix-001` / `TM-001`)
32
- for the `references` edge.
33
- - **Requirements.** Note the requirement files under `spec/functional/`,
34
- `spec/non-functional/`, `spec/usecase/`, `spec/stakeholder/` — Steps 3 and 4 trace against
35
- these ids.
36
- - **Source / test trees.** Identify where implementation and tests live (e.g. `src/` +
37
- `tests/`, or language-specific layout). Used in Steps 2–4.
38
-
39
- ### 3. Hand off
40
-
41
- State explicitly, so later steps and the artifact agree:
42
-
43
- - target bundle path (e.g. `plan/Plan-002-packaging-distribution/`)
44
- - spec root, matrix path + id
45
- - `ix://<org>/<component>` prefix
46
- - where source and tests live
47
-
48
- ## Notes
49
-
50
- - If there is **no** plan bundle, stop and tell the user — gap-analysis audits a plan; it
51
- does not invent one (use `spec-to-plan` first).
52
- - If there is **no** Test Matrix, Step 2 a/Plan checks still run, but record a `high`
53
- finding that the matrix is missing and Step 3 cannot verify coverage.
@@ -1,49 +0,0 @@
1
- # Step 2: Plan Completion
2
-
3
- **Goal**: Confirm every unit of work in the targeted plan is actually finished.
4
-
5
- ## The Task contract
6
-
7
- Tasks in the bundle are frontmatter-typed (`type: Task`). The machine contract
8
- (see `quoin/skills/spec-to-plan/SKILL.md`):
9
-
10
- ```yaml
11
- ---
12
- id: Task-001
13
- type: Task
14
- status: not_started | in_progress | blocked | done
15
- track: A | B | C | S | J | <gate-name>
16
- priority: P0 | P1 | P2 | P3
17
- relationships:
18
- - { target: "ix://org/component/Task-000", type: depends_on }
19
- - { target: "ix://org/component/FR-002", type: references } # requirement ownership
20
- - { target: "ix://org/component/TC-004", type: verifies } # test-case trace
21
- ---
22
- ```
23
-
24
- ## Process
25
-
26
- 1. **Enumerate tasks.** Read every `plan/<Plan-id>-<slug>/tasks/Task-*.md`.
27
- 2. **Assert completion.** For each task, check `status`:
28
- - `done` → OK.
29
- - `not_started` / `in_progress` / `blocked` → **finding**. Severity:
30
- - `high` if `priority: P0`/`P1` or it is on the critical path (`track: A`/`S`).
31
- - `medium` otherwise. `blocked` → note the blocker (its unmet `depends_on`).
32
- 3. **Check dependency sanity.** Flag a `done` task whose `depends_on` target is **not**
33
- `done` (out-of-order completion) as a `medium` finding.
34
- 4. **Cross-check `plan.md` checkboxes.** `plan.md` mirrors requirements/tests as
35
- `- [ ]` / `- [x]`. Flag (`low`) any checkbox state that contradicts task status
36
- (e.g. an unchecked requirement whose owning task is `done`, or vice-versa) — the plan
37
- doc is drifting from its tasks.
38
- 5. **Record the rollup.** Count tasks `done` / total — feeds the SpecReview `## Coverage`.
39
-
40
- ## Output of this step
41
-
42
- A list of findings (incomplete tasks, out-of-order completion, checkbox drift) with their
43
- `Refs` (the Task id, and the requirement/TC it owns) for the SpecReview Findings table, plus
44
- the tasks-done/total count.
45
-
46
- ## Notes
47
-
48
- - Do not edit task files or `plan.md` — gap-analysis only reports. If the user wants the
49
- plan reconciled, that's `spec-to-plan` (update flow) or `implement-plan`.
@@ -1,147 +0,0 @@
1
- # Step 3: Test-Matrix Verification
2
-
3
- **Goal**: Prove the Test Matrix is *real* — every Test Case it claims is backed by an actual
4
- test in the suite, identified by a matching **tracking tag** in the test code. This is the
5
- heart of gap-analysis: a matrix row marked ✅ means nothing unless a tagged test exists.
6
-
7
- **This step no longer greps.** `quire coverage` computes the reconciliation deterministically
8
- and reports it; this skill interprets the report and owns the judgement. Severity and verdict
9
- stay here — the command reports and does not judge (quire-rs FR-050-CON-1).
10
-
11
- ## The matrix shape
12
-
13
- Built by `spec-matrix` (`quoin/skills/spec-matrix/SKILL.md`). Key tables:
14
-
15
- - **Test Case Summary** — `Test ID | Title | Type | Priority | Traces To | Status`, where
16
- `Test ID` = `TC-xxx`, `Traces To` = `FR-XXX-AC-X` etc., `Status` ∈ `✅ ❌ 🚧 ⛔` (`⚠️` retired — partial work is `🚧`).
17
- - **Per-requirement coverage** — StR/US/FR/NFR → AC → TC → Status tables.
18
-
19
- What each column *means* is not this skill's knowledge either: the active module declares it
20
- under `traceability:`, and `quire coverage` reads the same declaration the matrix contract is
21
- validated against, so the two cannot drift.
22
-
23
- ## Run the rollup
24
-
25
- ```
26
- quire coverage --scope <project_root> --json
27
- ```
28
-
29
- `--scope` is the repository root, and stays so. Since quire-cli v0.16.0 (quire-rs CR-045)
30
- the command derives **two roots** from it and never interchanges them: spec documents are
31
- read from `<project_root>/spec` only, and trace tags from the source tree at
32
- `<project_root>` excluding `spec/`. This invocation needs no second flag — but a project
33
- whose `spec/` directory is missing now exits with a diagnostic naming the missing document
34
- root instead of silently scanning the whole repository, and a matrix outside `spec/` (a
35
- fixture, a `plan/` copy) mints nothing.
36
-
37
- **Check the version before relying on any of that.** The "since v0.16.0" premise is not
38
- enforced anywhere — nothing probes it, and a user on ≤ 0.15.0 silently gets the pre-split
39
- traversal semantics, where the walk covers the whole repository and a matrix outside
40
- `spec/` mints. One line, before the first invocation:
41
-
42
- ```bash
43
- quire --version # expect >= 0.16.0; on an older build the roots are not split
44
- ```
45
-
46
- If it is older, say so in `## Coverage` rather than reading the report as if the split
47
- applied.
48
-
49
- Do **not** pass `--strict`. Whether a gap blocks is this skill's verdict rule (Step 6), not
50
- the command's exit code.
51
-
52
- The report carries exactly the findings this step produces:
53
-
54
- | Report field | What it is |
55
- | --- | --- |
56
- | `unbacked_rows` | A declared reference row whose trace targets have no backing `verifies` relation. Each carries `reference`, `document`, `row_id`, `target_ids`. |
57
- | `status_lies` | A row whose status classes as `complete` while nothing backs it. Adds the authored `status` string. |
58
- | `untracked_symbols` | A test carrying a trace tag that resolves to no declared row. Carries `path`, `symbol`, `trace_id`. |
59
- | `no_symbol_rows` | An unbacked row whose **declared verification method mints no source symbol** — an eval, an inspection, a demonstration (quire-rs FR-050-AC-16 / CR-041). Carries `reference`, `document`, `row_id`, `test_type`, `target_ids`. **Read this before triaging `unbacked_rows`**: a row listed here is exempt from `status_lies` by its own method, and reporting it as an unbacked-row finding asserts something impossible. Absent from the JSON entirely when the module declares no `no_source_symbol` vocabulary. |
60
- | `criteria` | Per-document acceptance-criteria property counts (quire-rs FR-050-AC-13 / CR-028): `document`, `archetype`, `criteria`, `property_shaped`, `by_property`. Data for the `spec-correctness` handoff, never a verdict — a low property-shaped share describes a corpus, it does not fail one. Absent when the corpus binds no criteria. |
61
- | `groups` | Per minting document: `document`, `target`, `backed`, `total`. |
62
- | `diagnostics` | Declarations that selected nothing and why (quire-rs FR-050-AC-19 / CR-054): an unreadable declared `document:`, an archetype no document has when the model minted nothing, or a model with no trace targets. Absent when every declaration selected. A non-empty list means the numbers below it are measuring less than you think. |
63
- | `totals` | `backed` / `total` across the bundle, plus `criteria` / `property_shaped` when the corpus binds criteria. |
64
-
65
- ## Reconcile, producing findings
66
-
67
- | Report field | Finding | Severity |
68
- | --- | --- | --- |
69
- | `unbacked_rows` | Matrix overclaims coverage — the row names a criterion or test id nothing backs | `high` |
70
- | `status_lies` | The row asserts `✅` over nothing. A subset of the above, and the worse half | `high` |
71
- | `untracked_symbols` | A tagged test pointing at a row that does not exist — a stale tag, or a matrix that dropped a row | `medium` |
72
- | Marker drift | Matrix `Status` inconsistent with a real run (`🚧` on a passing tagged test) | `low` |
73
-
74
- `Refs` for each finding is the `row_id` and `document` the report gives, or `path::symbol`
75
- for an untracked symbol. Do not re-derive them.
76
-
77
- Marker drift is the one judgement the report cannot make — it needs the suite to have
78
- actually run (step 4 below).
79
-
80
- ## Two ways the report can mislead, and how to read it
81
-
82
- - **`totals.total == 0` is not full coverage.** It means the declared model matched nothing
83
- in this scope — no minting document was found. Recent `quire` prints `no rows matched`
84
- rather than a percentage and fails `--strict` (quire-rs FR-050-AC-14); an older build
85
- printed `0/0 rows backed (100%)` and exited 0. Treat a zero denominator as **no data**,
86
- say so in `## Coverage`, and fall back (below). It is not a `PASS`.
87
- - **An empty `unbacked_rows` proves nothing on its own.** It lists *reference rows* — cells
88
- that point at trace ids. A repo whose module declares no such references has an empty list
89
- regardless of how many tests are tagged. Read `groups` / `totals` alongside it.
90
-
91
- ## Fallback: a repo on an older module set
92
-
93
- `quire coverage` exits non-zero with a distinct diagnostic when no active module declares a
94
- `traceability:` model (FR-050-AC-9). That is a real repo state, not an error to swallow —
95
- `spec-artifacts-process` only began declaring the model at the release carrying FR-004.
96
-
97
- When the command refuses, or reports a zero denominator, fall back to the grep index below
98
- and **say which path ran** in the SpecReview's `## Coverage` section:
99
-
100
- ```
101
- Reconciliation: quire coverage (module spec-artifacts-process 0.11.0)
102
- Reconciliation: grep fallback — no active module declares a traceability model
103
- ```
104
-
105
- A finding derived from the fallback is weaker and should be read as such: grep matches a tag
106
- wherever it sits in a file, including places the engine will not bind it. In quoin, ~15 tags
107
- sat above a `describe(` block, which registers no symbol — greppable, and invisible to the
108
- engine (agent-ix/quoin#61). **Never present a grep count as a coverage figure** without
109
- naming it as a fallback.
110
-
111
- ### The fallback index
112
-
113
- Grep the test tree across `.py` / `.ts` / `.rs` for every form:
114
-
115
- | Form | Example |
116
- | --- | --- |
117
- | Docstring AC trace | `FR-007-AC-01` inside a test docstring `Description:` block |
118
- | Docstring `Trace:` | `Trace: FR-001` |
119
- | Module docstring | `"""Tests for FR-017: Context Management."""` |
120
- | Test-case id comment / name | `# TC-041`, or a test whose name maps to `TC-041` |
121
-
122
- Build `{tag → [test file :: test name]}`, then reconcile against the matrix by hand for the
123
- same four finding kinds.
124
-
125
- ## Optionally run the suite
126
-
127
- If the user wants execution evidence rather than static reconciliation, run `make test` and
128
- note failures and skips against matrix rows. This is what turns marker drift from a guess
129
- into a finding. Don't block on it if the environment can't run tests; say so.
130
-
131
- ## Rollup
132
-
133
- `totals.backed` / `totals.total` feeds `## Coverage`, with the per-document breakdown from
134
- `groups` where it helps. Report the numbers the tool produced — do not recompute them, and
135
- do not quote a figure from an earlier run whose provenance you cannot state.
136
-
137
- ## Output of this step
138
-
139
- Findings (unbacked rows, status lies, untracked tests, marker drift) with `Refs` from the
140
- report, the backed/total count, and which reconciliation path ran.
141
-
142
- ## Notes
143
-
144
- - A backed row proves *traceability*, not *correctness* — whether the test is a good test is
145
- Step 4 (underspecified/stub) and Step 5 (semantic). Keep this step about presence + trace.
146
- - The command performs no network or service I/O and executes none of the code it reads
147
- (FR-050-CON-2, FR-051-CON-1), so it is safe to run in any repo.
@@ -1,63 +0,0 @@
1
- # Step 4: Underspecified Code (reverse gap)
2
-
3
- **Goal**: Find the *reverse* gap — code and behavior that exist with **no owning
4
- requirement**, plus stubs that masquerade as complete. Steps 2–3 verify spec→code/test
5
- coverage; this step verifies code→spec, catching scope that was implemented but never
6
- specified.
7
-
8
- Reuse the detection heuristics in
9
- `~/dev/agent_skills/implementation-gap-analysis/SKILL.md` — don't reinvent them.
10
-
11
- ## A. Untraced behavior (code with no requirement)
12
-
13
- 1. **Inventory the surface.** List the component's real behaviors — public
14
- functions/methods, CLI commands/flags, HTTP endpoints, events, config knobs.
15
- 2. **Trace each to a requirement.** A behavior is *traced* if it maps to an StR/US/FR/NFR
16
- (via the matrix `Traces To`, a requirement that describes it, or a Task `references`
17
- edge that owns it).
18
- 3. **Flag the untraced.** Behavior with no owning requirement → finding:
19
- - `high` if it is user-visible or security/data-affecting (an endpoint, a CLI command, a
20
- destructive operation) — unspecified surface area.
21
- - `medium` for internal-but-meaningful logic with no requirement.
22
- - `low` for trivial helpers/glue.
23
- `Refs` = the code location (`path::symbol`).
24
-
25
- ## B. Implied requirements from code patterns
26
-
27
- Map suspicious patterns to the requirement that *should* exist (per the
28
- implementation-gap-analysis table):
29
-
30
- | Code pattern | Missing requirement type |
31
- | --- | --- |
32
- | Defensive code (try/catch, null guards) | Robustness (NFR) |
33
- | Ambiguous identity/equality logic | Integrity (StR) |
34
- | Side effects / IO in core logic | Determinism (StR) |
35
- | Recursion / unbounded structures | Topology / limits (NFR) |
36
- | Unmapped constraints | Traceability (FR/StR/NFR) |
37
-
38
- Each unstated-but-implemented constraint → `medium` finding.
39
-
40
- ## C. Stubs masquerading as complete
41
-
42
- Scan **source** (not just tests) for hollow implementations the plan/matrix may report as
43
- done:
44
-
45
- | Stub | Detect | Severity |
46
- | --- | --- | --- |
47
- | Tiny file (≤5 lines, excl. `__init__`) | line count | high |
48
- | `pass` / placeholder return (`{}`,`[]`,`None`,`"not implemented"`) body | grep/AST | high |
49
- | Protocol/ABC-only with no concrete impl | structure | high |
50
- | Re-export-only module | structure | medium (may be intentional) |
51
- | Trivially-covered stub (≤5 lines @ 100% cov) | coverage + size | medium |
52
-
53
- A stub behind a `done` task or a ✅ matrix row is a `high` finding (false completion).
54
-
55
- ## Output of this step
56
-
57
- Findings for untraced behavior, implied-but-missing requirements, and stubs, each with
58
- `Refs` = code location, plus a count of untraced behaviors/stubs for `## Coverage`.
59
-
60
- ## Notes
61
-
62
- - This is the bridge to better specs: untraced behavior usually means a requirement should
63
- be authored (`/specify`) — but gap-analysis only **reports** it; it does not author specs.