@agent-ix/quoin 0.23.1 → 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.
- package/README.md +8 -258
- package/bin/launcher.js +138 -0
- package/package.json +22 -123
- package/.agents/plugins/marketplace.json +0 -14
- package/.claude-plugin/marketplace.json +0 -16
- package/.claude-plugin/plugin.json +0 -8
- package/.codex-plugin/plugin.json +0 -27
- package/.github/plugin/marketplace.json +0 -16
- package/bin/quoin.js +0 -21
- package/default-modules.yaml +0 -107
- package/dist/advisor/advise.d.ts +0 -199
- package/dist/advisor/advise.d.ts.map +0 -1
- package/dist/advisor/index.d.ts +0 -10
- package/dist/advisor/index.d.ts.map +0 -1
- package/dist/advisor/methods.d.ts +0 -60
- package/dist/advisor/methods.d.ts.map +0 -1
- package/dist/advisor-B0rESCx1.js +0 -63
- package/dist/assurance/graph.d.ts +0 -87
- package/dist/assurance/graph.d.ts.map +0 -1
- package/dist/assurance/index.d.ts +0 -9
- package/dist/assurance/index.d.ts.map +0 -1
- package/dist/assurance/render.d.ts +0 -3
- package/dist/assurance/render.d.ts.map +0 -1
- package/dist/auditor/audit.d.ts +0 -146
- package/dist/auditor/audit.d.ts.map +0 -1
- package/dist/auditor/combinatorial.d.ts +0 -53
- package/dist/auditor/combinatorial.d.ts.map +0 -1
- package/dist/auditor/index.d.ts +0 -9
- package/dist/auditor/index.d.ts.map +0 -1
- package/dist/auditor-Dd3i9Aqx.js +0 -340
- package/dist/base-gAClyCNd.js +0 -137
- package/dist/base.d.ts +0 -23
- package/dist/base.d.ts.map +0 -1
- package/dist/catalog.d.ts +0 -33
- package/dist/catalog.d.ts.map +0 -1
- package/dist/change-assurance/attestations.d.ts +0 -7
- package/dist/change-assurance/attestations.d.ts.map +0 -1
- package/dist/change-assurance/index.d.ts +0 -14
- package/dist/change-assurance/index.d.ts.map +0 -1
- package/dist/change-assurance/integrity.d.ts +0 -11
- package/dist/change-assurance/integrity.d.ts.map +0 -1
- package/dist/change-assurance/records.d.ts +0 -22
- package/dist/change-assurance/records.d.ts.map +0 -1
- package/dist/change-assurance/schema-assets.d.ts +0 -8
- package/dist/change-assurance/schema-assets.d.ts.map +0 -1
- package/dist/change-assurance/store.d.ts +0 -18
- package/dist/change-assurance/store.d.ts.map +0 -1
- package/dist/change-assurance/types.d.ts +0 -180
- package/dist/change-assurance/types.d.ts.map +0 -1
- package/dist/change-assurance/verify.d.ts +0 -4
- package/dist/change-assurance/verify.d.ts.map +0 -1
- package/dist/change-assurance-CyKLPeKa.js +0 -1236
- package/dist/cli.d.ts +0 -61
- package/dist/cli.d.ts.map +0 -1
- package/dist/cli.js +0 -34
- package/dist/commands/advise.d.ts +0 -16
- package/dist/commands/advise.d.ts.map +0 -1
- package/dist/commands/advise.js +0 -234
- package/dist/commands/assurance.d.ts +0 -14
- package/dist/commands/assurance.d.ts.map +0 -1
- package/dist/commands/assurance.js +0 -204
- package/dist/commands/catalog/index.d.ts +0 -2
- package/dist/commands/catalog/index.d.ts.map +0 -1
- package/dist/commands/catalog/index.js +0 -2
- package/dist/commands/catalog/list.d.ts +0 -11
- package/dist/commands/catalog/list.d.ts.map +0 -1
- package/dist/commands/catalog/list.js +0 -22
- package/dist/commands/catalog/methods.d.ts +0 -12
- package/dist/commands/catalog/methods.d.ts.map +0 -1
- package/dist/commands/catalog/methods.js +0 -43
- package/dist/commands/catalog/show.d.ts +0 -13
- package/dist/commands/catalog/show.d.ts.map +0 -1
- package/dist/commands/catalog/show.js +0 -25
- package/dist/commands/catalog/validate.d.ts +0 -10
- package/dist/commands/catalog/validate.d.ts.map +0 -1
- package/dist/commands/catalog/validate.js +0 -27
- package/dist/commands/change-assurance/common.d.ts +0 -37
- package/dist/commands/change-assurance/common.d.ts.map +0 -1
- package/dist/commands/change-assurance/index.d.ts +0 -8
- package/dist/commands/change-assurance/index.d.ts.map +0 -1
- package/dist/commands/change-assurance/index.js +0 -12
- package/dist/commands/change-assurance/intake.d.ts +0 -15
- package/dist/commands/change-assurance/intake.d.ts.map +0 -1
- package/dist/commands/change-assurance/intake.js +0 -53
- package/dist/commands/change-assurance/receipt.d.ts +0 -21
- package/dist/commands/change-assurance/receipt.d.ts.map +0 -1
- package/dist/commands/change-assurance/receipt.js +0 -99
- package/dist/commands/change-assurance/recover.d.ts +0 -13
- package/dist/commands/change-assurance/recover.d.ts.map +0 -1
- package/dist/commands/change-assurance/recover.js +0 -29
- package/dist/commands/change-assurance/schema.d.ts +0 -13
- package/dist/commands/change-assurance/schema.d.ts.map +0 -1
- package/dist/commands/change-assurance/schema.js +0 -40
- package/dist/commands/change-assurance/seal-attestation.d.ts +0 -15
- package/dist/commands/change-assurance/seal-attestation.d.ts.map +0 -1
- package/dist/commands/change-assurance/seal-attestation.js +0 -58
- package/dist/commands/change-assurance/seal-record.d.ts +0 -14
- package/dist/commands/change-assurance/seal-record.d.ts.map +0 -1
- package/dist/commands/change-assurance/seal-record.js +0 -53
- package/dist/commands/change-assurance/verify-receipt.d.ts +0 -13
- package/dist/commands/change-assurance/verify-receipt.d.ts.map +0 -1
- package/dist/commands/change-assurance/verify-receipt.js +0 -41
- package/dist/commands/completeness.d.ts +0 -16
- package/dist/commands/completeness.d.ts.map +0 -1
- package/dist/commands/completeness.js +0 -49
- package/dist/commands/config/doctor.d.ts +0 -7
- package/dist/commands/config/doctor.d.ts.map +0 -1
- package/dist/commands/config/doctor.js +0 -15
- package/dist/commands/config/edit.d.ts +0 -7
- package/dist/commands/config/edit.d.ts.map +0 -1
- package/dist/commands/config/edit.js +0 -13
- package/dist/commands/config/get.d.ts +0 -11
- package/dist/commands/config/get.d.ts.map +0 -1
- package/dist/commands/config/get.js +0 -20
- package/dist/commands/config/index.d.ts +0 -2
- package/dist/commands/config/index.d.ts.map +0 -1
- package/dist/commands/config/index.js +0 -2
- package/dist/commands/config/set.d.ts +0 -12
- package/dist/commands/config/set.d.ts.map +0 -1
- package/dist/commands/config/set.js +0 -26
- package/dist/commands/evidence/affirm.d.ts +0 -17
- package/dist/commands/evidence/affirm.d.ts.map +0 -1
- package/dist/commands/evidence/affirm.js +0 -65
- package/dist/commands/evidence/audit.d.ts +0 -34
- package/dist/commands/evidence/audit.d.ts.map +0 -1
- package/dist/commands/evidence/audit.js +0 -107
- package/dist/commands/evidence/baseline.d.ts +0 -14
- package/dist/commands/evidence/baseline.d.ts.map +0 -1
- package/dist/commands/evidence/baseline.js +0 -89
- package/dist/commands/evidence/gc.d.ts +0 -13
- package/dist/commands/evidence/gc.d.ts.map +0 -1
- package/dist/commands/evidence/gc.js +0 -35
- package/dist/commands/evidence/index.d.ts +0 -8
- package/dist/commands/evidence/index.d.ts.map +0 -1
- package/dist/commands/evidence/index.js +0 -18
- package/dist/commands/evidence/inspect-mocks.d.ts +0 -16
- package/dist/commands/evidence/inspect-mocks.d.ts.map +0 -1
- package/dist/commands/evidence/inspect-mocks.js +0 -49
- package/dist/commands/evidence/record.d.ts +0 -22
- package/dist/commands/evidence/record.d.ts.map +0 -1
- package/dist/commands/evidence/record.js +0 -144
- package/dist/commands/graph/change-impact.d.ts +0 -16
- package/dist/commands/graph/change-impact.d.ts.map +0 -1
- package/dist/commands/graph/change-impact.js +0 -29
- package/dist/commands/graph/churn.d.ts +0 -14
- package/dist/commands/graph/churn.d.ts.map +0 -1
- package/dist/commands/graph/churn.js +0 -15
- package/dist/commands/graph/common.d.ts +0 -16
- package/dist/commands/graph/common.d.ts.map +0 -1
- package/dist/commands/graph/fan-out.d.ts +0 -14
- package/dist/commands/graph/fan-out.d.ts.map +0 -1
- package/dist/commands/graph/fan-out.js +0 -15
- package/dist/commands/graph/index.d.ts +0 -8
- package/dist/commands/graph/index.d.ts.map +0 -1
- package/dist/commands/graph/index.js +0 -12
- package/dist/commands/matrix.d.ts +0 -14
- package/dist/commands/matrix.d.ts.map +0 -1
- package/dist/commands/matrix.js +0 -15
- package/dist/commands/measurement/index.d.ts +0 -7
- package/dist/commands/measurement/index.d.ts.map +0 -1
- package/dist/commands/measurement/index.js +0 -11
- package/dist/commands/measurement/intervention.d.ts +0 -11
- package/dist/commands/measurement/intervention.d.ts.map +0 -1
- package/dist/commands/measurement/intervention.js +0 -31
- package/dist/commands/measurement/operational-release.d.ts +0 -11
- package/dist/commands/measurement/operational-release.d.ts.map +0 -1
- package/dist/commands/measurement/operational-release.js +0 -31
- package/dist/commands/measurement/record.d.ts +0 -10
- package/dist/commands/measurement/record.d.ts.map +0 -1
- package/dist/commands/measurement/record.js +0 -36
- package/dist/commands/module/ensure-defaults.d.ts +0 -8
- package/dist/commands/module/ensure-defaults.d.ts.map +0 -1
- package/dist/commands/module/ensure-defaults.js +0 -17
- package/dist/commands/module/index.d.ts +0 -2
- package/dist/commands/module/index.d.ts.map +0 -1
- package/dist/commands/module/index.js +0 -2
- package/dist/commands/module/install.d.ts +0 -11
- package/dist/commands/module/install.d.ts.map +0 -1
- package/dist/commands/module/install.js +0 -22
- package/dist/commands/module/list.d.ts +0 -8
- package/dist/commands/module/list.d.ts.map +0 -1
- package/dist/commands/module/list.js +0 -13
- package/dist/commands/module/remove.d.ts +0 -10
- package/dist/commands/module/remove.d.ts.map +0 -1
- package/dist/commands/module/remove.js +0 -16
- package/dist/commands/plugin/deprecation.d.ts +0 -10
- package/dist/commands/plugin/deprecation.d.ts.map +0 -1
- package/dist/commands/plugin/ensure-defaults.d.ts +0 -8
- package/dist/commands/plugin/ensure-defaults.d.ts.map +0 -1
- package/dist/commands/plugin/ensure-defaults.js +0 -12
- package/dist/commands/plugin/index.d.ts +0 -2
- package/dist/commands/plugin/index.d.ts.map +0 -1
- package/dist/commands/plugin/index.js +0 -2
- package/dist/commands/plugin/install.d.ts +0 -8
- package/dist/commands/plugin/install.d.ts.map +0 -1
- package/dist/commands/plugin/install.js +0 -12
- package/dist/commands/plugin/list.d.ts +0 -8
- package/dist/commands/plugin/list.d.ts.map +0 -1
- package/dist/commands/plugin/list.js +0 -12
- package/dist/commands/plugin/remove.d.ts +0 -8
- package/dist/commands/plugin/remove.d.ts.map +0 -1
- package/dist/commands/plugin/remove.js +0 -12
- package/dist/commands/report.d.ts +0 -19
- package/dist/commands/report.d.ts.map +0 -1
- package/dist/commands/report.js +0 -96
- package/dist/commands/review.d.ts +0 -14
- package/dist/commands/review.d.ts.map +0 -1
- package/dist/commands/review.js +0 -15
- package/dist/commands/to-plan.d.ts +0 -14
- package/dist/commands/to-plan.d.ts.map +0 -1
- package/dist/commands/to-plan.js +0 -15
- package/dist/commands/update.d.ts +0 -13
- package/dist/commands/update.d.ts.map +0 -1
- package/dist/commands/update.js +0 -34
- package/dist/commands/validate.d.ts +0 -13
- package/dist/commands/validate.d.ts.map +0 -1
- package/dist/commands/validate.js +0 -123
- package/dist/commands/write.d.ts +0 -16
- package/dist/commands/write.d.ts.map +0 -1
- package/dist/commands/write.js +0 -33
- package/dist/common-B1ZJ8CSO.js +0 -36
- package/dist/common-DTrmnvL-.js +0 -35
- package/dist/completeness/assess.d.ts +0 -82
- package/dist/completeness/assess.d.ts.map +0 -1
- package/dist/completeness/bundle.d.ts +0 -52
- package/dist/completeness/bundle.d.ts.map +0 -1
- package/dist/completeness/declarations.d.ts +0 -46
- package/dist/completeness/declarations.d.ts.map +0 -1
- package/dist/completeness/index.d.ts +0 -11
- package/dist/completeness/index.d.ts.map +0 -1
- package/dist/completeness/run.d.ts +0 -35
- package/dist/completeness/run.d.ts.map +0 -1
- package/dist/completeness-BzBuNq6w.js +0 -228
- package/dist/config-schema-Dp-vlxuR.js +0 -13
- package/dist/config-schema.d.ts +0 -52
- package/dist/config-schema.d.ts.map +0 -1
- package/dist/deprecation-fRxUHoxv.js +0 -4
- package/dist/evidence/adapters/agent-eval.d.ts +0 -26
- package/dist/evidence/adapters/agent-eval.d.ts.map +0 -1
- package/dist/evidence/adapters/audit-script.d.ts +0 -25
- package/dist/evidence/adapters/audit-script.d.ts.map +0 -1
- package/dist/evidence/adapters/cargo-mutants.d.ts +0 -3
- package/dist/evidence/adapters/cargo-mutants.d.ts.map +0 -1
- package/dist/evidence/adapters/contract-conformance.d.ts +0 -16
- package/dist/evidence/adapters/contract-conformance.d.ts.map +0 -1
- package/dist/evidence/adapters/differential-report.d.ts +0 -18
- package/dist/evidence/adapters/differential-report.d.ts.map +0 -1
- package/dist/evidence/adapters/junit.d.ts +0 -17
- package/dist/evidence/adapters/junit.d.ts.map +0 -1
- package/dist/evidence/adapters/registry.d.ts +0 -63
- package/dist/evidence/adapters/registry.d.ts.map +0 -1
- package/dist/evidence/adapters/sarif.d.ts +0 -35
- package/dist/evidence/adapters/sarif.d.ts.map +0 -1
- package/dist/evidence/adapters/sbom.d.ts +0 -35
- package/dist/evidence/adapters/sbom.d.ts.map +0 -1
- package/dist/evidence/adapters/types.d.ts +0 -86
- package/dist/evidence/adapters/types.d.ts.map +0 -1
- package/dist/evidence/index.d.ts +0 -27
- package/dist/evidence/index.d.ts.map +0 -1
- package/dist/evidence/mock-inspection.d.ts +0 -16
- package/dist/evidence/mock-inspection.d.ts.map +0 -1
- package/dist/evidence/record.d.ts +0 -58
- package/dist/evidence/record.d.ts.map +0 -1
- package/dist/evidence/store.d.ts +0 -215
- package/dist/evidence/store.d.ts.map +0 -1
- package/dist/evidence/types.d.ts +0 -281
- package/dist/evidence/types.d.ts.map +0 -1
- package/dist/evidence-OyqpqHLS.js +0 -614
- package/dist/flow-command-CCRTE5Oe.js +0 -88
- package/dist/flow-command.d.ts +0 -25
- package/dist/flow-command.d.ts.map +0 -1
- package/dist/flows.d.ts +0 -7
- package/dist/flows.d.ts.map +0 -1
- package/dist/graph-analysis/analysis.d.ts +0 -106
- package/dist/graph-analysis/analysis.d.ts.map +0 -1
- package/dist/graph-analysis/index.d.ts +0 -6
- package/dist/graph-analysis/index.d.ts.map +0 -1
- package/dist/graph-analysis/input.d.ts +0 -33
- package/dist/graph-analysis/input.d.ts.map +0 -1
- package/dist/graph-analysis/load.d.ts +0 -21
- package/dist/graph-analysis/load.d.ts.map +0 -1
- package/dist/graph-analysis/render.d.ts +0 -4
- package/dist/graph-analysis/render.d.ts.map +0 -1
- package/dist/graph-analysis-IWaoJJSN.js +0 -657
- package/dist/hooks/command-not-found.d.ts +0 -23
- package/dist/hooks/command-not-found.d.ts.map +0 -1
- package/dist/hooks/command-not-found.js +0 -8
- package/dist/index.d.ts +0 -13
- package/dist/index.d.ts.map +0 -1
- package/dist/index.js +0 -12
- package/dist/measurement/agent-eval-intervention.d.ts +0 -6
- package/dist/measurement/agent-eval-intervention.d.ts.map +0 -1
- package/dist/measurement/atomic-file.d.ts +0 -5
- package/dist/measurement/atomic-file.d.ts.map +0 -1
- package/dist/measurement/compare.d.ts +0 -4
- package/dist/measurement/compare.d.ts.map +0 -1
- package/dist/measurement/date-time.d.ts +0 -3
- package/dist/measurement/date-time.d.ts.map +0 -1
- package/dist/measurement/github-release-operational.d.ts +0 -7
- package/dist/measurement/github-release-operational.d.ts.map +0 -1
- package/dist/measurement/graph-adapters.d.ts +0 -304
- package/dist/measurement/graph-adapters.d.ts.map +0 -1
- package/dist/measurement/graph-portfolio-load.d.ts +0 -3
- package/dist/measurement/graph-portfolio-load.d.ts.map +0 -1
- package/dist/measurement/graph-portfolio.d.ts +0 -158
- package/dist/measurement/graph-portfolio.d.ts.map +0 -1
- package/dist/measurement/index.d.ts +0 -22
- package/dist/measurement/index.d.ts.map +0 -1
- package/dist/measurement/intervention-report.d.ts +0 -24
- package/dist/measurement/intervention-report.d.ts.map +0 -1
- package/dist/measurement/intervention-schema.d.ts +0 -144
- package/dist/measurement/intervention-schema.d.ts.map +0 -1
- package/dist/measurement/intervention-types.d.ts +0 -105
- package/dist/measurement/intervention-types.d.ts.map +0 -1
- package/dist/measurement/intervention.d.ts +0 -16
- package/dist/measurement/intervention.d.ts.map +0 -1
- package/dist/measurement/operational-report.d.ts +0 -17
- package/dist/measurement/operational-report.d.ts.map +0 -1
- package/dist/measurement/operational-schema.d.ts +0 -461
- package/dist/measurement/operational-schema.d.ts.map +0 -1
- package/dist/measurement/operational-types.d.ts +0 -121
- package/dist/measurement/operational-types.d.ts.map +0 -1
- package/dist/measurement/operational.d.ts +0 -13
- package/dist/measurement/operational.d.ts.map +0 -1
- package/dist/measurement/plans.d.ts +0 -6
- package/dist/measurement/plans.d.ts.map +0 -1
- package/dist/measurement/portfolio.d.ts +0 -54
- package/dist/measurement/portfolio.d.ts.map +0 -1
- package/dist/measurement/profiles.d.ts +0 -9
- package/dist/measurement/profiles.d.ts.map +0 -1
- package/dist/measurement/report.d.ts +0 -48
- package/dist/measurement/report.d.ts.map +0 -1
- package/dist/measurement/schemas/operational-evidence-v1.schema.json.d.ts +0 -384
- package/dist/measurement/store.d.ts +0 -14
- package/dist/measurement/store.d.ts.map +0 -1
- package/dist/measurement/types.d.ts +0 -85
- package/dist/measurement/types.d.ts.map +0 -1
- package/dist/measurement/validate.d.ts +0 -9
- package/dist/measurement/validate.d.ts.map +0 -1
- package/dist/measurement-j8sDSqx5.js +0 -2980
- package/dist/modules-DDQkKC4l.js +0 -23
- package/dist/modules.d.ts +0 -10
- package/dist/modules.d.ts.map +0 -1
- package/dist/org.d.ts +0 -61
- package/dist/org.d.ts.map +0 -1
- package/dist/plugins-CHpYhpEI.js +0 -77
- package/dist/plugins.d.ts +0 -13
- package/dist/plugins.d.ts.map +0 -1
- package/dist/quire/assurance.d.ts +0 -109
- package/dist/quire/assurance.d.ts.map +0 -1
- package/dist/quire/contract.d.ts +0 -88
- package/dist/quire/contract.d.ts.map +0 -1
- package/dist/quire/exec.d.ts +0 -66
- package/dist/quire/exec.d.ts.map +0 -1
- package/dist/quire/index.d.ts +0 -13
- package/dist/quire/index.d.ts.map +0 -1
- package/dist/quire/types.d.ts +0 -415
- package/dist/quire/types.d.ts.map +0 -1
- package/dist/quire/validate.d.ts +0 -39
- package/dist/quire/validate.d.ts.map +0 -1
- package/dist/quire-BsVj1xIR.js +0 -4968
- package/dist/schema-assets-HZWo_iFN.js +0 -233
- package/dist/schemas/assurance-v1.schema.json +0 -225
- package/dist/schemas/change-assurance-record-v1.schema.json +0 -234
- package/dist/schemas/coverage-v1.schema.json +0 -1111
- package/dist/schemas/operational-evidence-v1.schema.json +0 -381
- package/dist/schemas/proof-attestation-v1.schema.json +0 -96
- package/dist/schemas/properties-v1.schema.json +0 -159
- package/dist/schemas/verification-receipt-v1.schema.json +0 -208
- package/dist/validators/gates.d.ts +0 -18
- package/dist/validators/gates.d.ts.map +0 -1
- package/dist/validators/index.d.ts +0 -2
- package/dist/validators/index.d.ts.map +0 -1
- package/dist/version-CMxMIh5g.js +0 -17
- package/dist/version.d.ts +0 -3
- package/dist/version.d.ts.map +0 -1
- package/dist/write-CGTI0dRO.js +0 -157
- package/dist/write.d.ts +0 -28
- package/dist/write.d.ts.map +0 -1
- package/skills/assurance-status-report/SKILL.md +0 -135
- package/skills/assurance-status-report/references/report-contract.md +0 -110
- package/skills/gap-analysis/SKILL.md +0 -111
- package/skills/gap-analysis/references/step-1-target-selection.md +0 -53
- package/skills/gap-analysis/references/step-2-plan-completion.md +0 -49
- package/skills/gap-analysis/references/step-3-matrix-verification.md +0 -147
- package/skills/gap-analysis/references/step-4-underspecified-code.md +0 -92
- package/skills/gap-analysis/references/step-5-semantic-review.md +0 -51
- package/skills/gap-analysis/references/step-6-specreview-artifact.md +0 -108
- package/skills/spec-app-review/SKILL.md +0 -51
- package/skills/spec-app-review/references/checklist.md +0 -197
- package/skills/spec-architecture-evaluation/SKILL.md +0 -30
- package/skills/spec-correctness/SKILL.md +0 -96
- package/skills/spec-correctness/assets/strategy-table.md +0 -101
- package/skills/spec-correctness/assets/templates/fast-check.ts.md +0 -169
- package/skills/spec-correctness/assets/templates/hypothesis.py.md +0 -156
- package/skills/spec-correctness/assets/templates/proptest.rs.md +0 -147
- package/skills/spec-correctness/references/step-0-scope-and-harness.md +0 -94
- package/skills/spec-correctness/references/step-1-census.md +0 -53
- package/skills/spec-correctness/references/step-2-clause-grounding.md +0 -159
- package/skills/spec-correctness/references/step-3-strategy-selection.md +0 -85
- package/skills/spec-correctness/references/step-4-generate-tests.md +0 -117
- package/skills/spec-correctness/references/step-5-second-pass.md +0 -81
- package/skills/spec-correctness/references/step-6-review-artifact.md +0 -134
- package/skills/spec-correctness/references/step-7-report-and-handoff.md +0 -102
- package/skills/spec-dependency-analysis/SKILL.md +0 -90
- package/skills/spec-ears-analysis/SKILL.md +0 -102
- package/skills/spec-evidence-analysis/SKILL.md +0 -156
- package/skills/spec-failure-domain-analysis/SKILL.md +0 -59
- package/skills/spec-fuzz/SKILL.md +0 -133
- package/skills/spec-fuzz/assets/templates/atheris.py.md +0 -74
- package/skills/spec-fuzz/assets/templates/cargo-fuzz.rs.md +0 -83
- package/skills/spec-fuzz/assets/templates/fast-check.ts.md +0 -76
- package/skills/spec-fuzz/references/step-0-scope-and-harness.md +0 -51
- package/skills/spec-fuzz/references/step-1-select-obligations.md +0 -47
- package/skills/spec-fuzz/references/step-2-ground-entry-point.md +0 -55
- package/skills/spec-fuzz/references/step-3-emit-targets.md +0 -65
- package/skills/spec-fuzz/references/step-4-report.md +0 -56
- package/skills/spec-ideation/SKILL.md +0 -46
- package/skills/spec-integrity-analysis/SKILL.md +0 -62
- package/skills/spec-matrix/SKILL.md +0 -186
- package/skills/spec-matrix/assets/test-cases/TC-001.md +0 -35
- package/skills/spec-matrix/assets/test-cases/TC-002.md +0 -37
- package/skills/spec-matrix/assets/test-cases/TC-006.md +0 -50
- package/skills/spec-matrix/assets/test-matrix-example.md +0 -104
- package/skills/spec-matrix/assets/test-matrix-template.md +0 -123
- package/skills/spec-matrix/workflow-assets/dist/index.d.ts +0 -146
- package/skills/spec-matrix/workflow-assets/dist/index.d.ts.map +0 -1
- package/skills/spec-matrix/workflow-assets/dist/index.js +0 -7525
- package/skills/spec-matrix/workflow-assets/dist/invariants.d.ts +0 -6
- package/skills/spec-matrix/workflow-assets/dist/invariants.d.ts.map +0 -1
- package/skills/spec-matrix/workflow-assets/skills/matrix/SKILL.md +0 -35
- package/skills/spec-matrix/workflow-assets/skills/matrix/scripts/invariants.js +0 -1
- package/skills/spec-matrix/workflow-assets/skills/matrix/templates/report/default.md +0 -30
- package/skills/spec-matrix/workflow-assets/skills/matrix/workflows/matrix/def.yaml +0 -82
- package/skills/spec-object-review/SKILL.md +0 -125
- package/skills/spec-object-review/references/object-type-guide.md +0 -118
- package/skills/spec-review/SKILL.md +0 -92
- package/skills/spec-review/references/checklist.md +0 -50
- package/skills/spec-review/workflow-assets/dist/index.d.ts +0 -146
- package/skills/spec-review/workflow-assets/dist/index.d.ts.map +0 -1
- package/skills/spec-review/workflow-assets/dist/index.js +0 -7525
- package/skills/spec-review/workflow-assets/dist/invariants.d.ts +0 -6
- package/skills/spec-review/workflow-assets/dist/invariants.d.ts.map +0 -1
- package/skills/spec-review/workflow-assets/skills/review/SKILL.md +0 -96
- package/skills/spec-review/workflow-assets/skills/review/scripts/invariants.js +0 -61
- package/skills/spec-review/workflow-assets/skills/review/workflows/review/def.yaml +0 -68
- package/skills/spec-risk-complexity-analysis/SKILL.md +0 -92
- package/skills/spec-scope-boundary-analysis/SKILL.md +0 -101
- package/skills/spec-security-analysis/SKILL.md +0 -84
- package/skills/spec-security-analysis/assets/security-analysis-example.md +0 -89
- package/skills/spec-security-analysis/assets/security-analysis-template.md +0 -73
- package/skills/spec-security-analysis/references/component-type-mapping.md +0 -161
- package/skills/spec-security-analysis/references/gdpr/ChII-Principles.md +0 -58
- package/skills/spec-security-analysis/references/gdpr/ChIII-DataSubjectRights.md +0 -84
- package/skills/spec-security-analysis/references/gdpr/ChIV-ControllerProcessor.md +0 -83
- package/skills/spec-security-analysis/references/gdpr/ChV-DataTransfers.md +0 -62
- package/skills/spec-security-analysis/references/gdpr/index.md +0 -54
- package/skills/spec-security-analysis/references/iso27001/A5-OrganizationalControls.md +0 -64
- package/skills/spec-security-analysis/references/iso27001/A6-PeopleControls.md +0 -30
- package/skills/spec-security-analysis/references/iso27001/A7-PhysicalControls.md +0 -35
- package/skills/spec-security-analysis/references/iso27001/A8-TechnologicalControls.md +0 -66
- package/skills/spec-security-analysis/references/iso27001/index.md +0 -43
- package/skills/spec-security-analysis/references/nist-800-53/AC-AccessControl.md +0 -57
- package/skills/spec-security-analysis/references/nist-800-53/AU-AuditAccountability.md +0 -49
- package/skills/spec-security-analysis/references/nist-800-53/CM-ConfigurationManagement.md +0 -36
- package/skills/spec-security-analysis/references/nist-800-53/IA-IdentificationAuthentication.md +0 -44
- package/skills/spec-security-analysis/references/nist-800-53/SA-SystemServicesAcquisition.md +0 -50
- package/skills/spec-security-analysis/references/nist-800-53/SC-SystemCommunications.md +0 -53
- package/skills/spec-security-analysis/references/nist-800-53/SI-SystemInformationIntegrity.md +0 -52
- package/skills/spec-security-analysis/references/nist-800-53/index.md +0 -58
- package/skills/spec-security-analysis/references/owasp-asvs/V1-Architecture.md +0 -33
- package/skills/spec-security-analysis/references/owasp-asvs/V10-MaliciousCode.md +0 -33
- package/skills/spec-security-analysis/references/owasp-asvs/V11-BusinessLogic.md +0 -32
- package/skills/spec-security-analysis/references/owasp-asvs/V12-Files.md +0 -34
- package/skills/spec-security-analysis/references/owasp-asvs/V13-API.md +0 -34
- package/skills/spec-security-analysis/references/owasp-asvs/V14-Configuration.md +0 -35
- package/skills/spec-security-analysis/references/owasp-asvs/V2-Authentication.md +0 -36
- package/skills/spec-security-analysis/references/owasp-asvs/V3-SessionManagement.md +0 -35
- package/skills/spec-security-analysis/references/owasp-asvs/V4-AccessControl.md +0 -39
- package/skills/spec-security-analysis/references/owasp-asvs/V5-Validation.md +0 -37
- package/skills/spec-security-analysis/references/owasp-asvs/V6-Cryptography.md +0 -34
- package/skills/spec-security-analysis/references/owasp-asvs/V7-ErrorLogging.md +0 -37
- package/skills/spec-security-analysis/references/owasp-asvs/V8-DataProtection.md +0 -34
- package/skills/spec-security-analysis/references/owasp-asvs/V9-Communication.md +0 -32
- package/skills/spec-security-analysis/references/owasp-asvs/index.md +0 -59
- package/skills/spec-security-analysis/references/soc2/CC1-ControlEnvironment.md +0 -31
- package/skills/spec-security-analysis/references/soc2/CC2-CommunicationInformation.md +0 -27
- package/skills/spec-security-analysis/references/soc2/CC3-RiskAssessment.md +0 -29
- package/skills/spec-security-analysis/references/soc2/CC4-MonitoringActivities.md +0 -27
- package/skills/spec-security-analysis/references/soc2/CC5-ControlActivities.md +0 -28
- package/skills/spec-security-analysis/references/soc2/CC6-LogicalPhysicalAccess.md +0 -45
- package/skills/spec-security-analysis/references/soc2/CC7-SystemOperations.md +0 -42
- package/skills/spec-security-analysis/references/soc2/CC8-ChangeManagement.md +0 -32
- package/skills/spec-security-analysis/references/soc2/CC9-RiskMitigation.md +0 -34
- package/skills/spec-security-analysis/references/soc2/index.md +0 -46
- package/skills/spec-security-analysis/references/standards-index.md +0 -46
- package/skills/spec-to-plan/SKILL.md +0 -88
- package/skills/spec-to-plan/references/step-0-plan-selection.md +0 -121
- package/skills/spec-to-plan/references/step-1-analysis.md +0 -88
- package/skills/spec-to-plan/references/step-2-test-plan.md +0 -43
- package/skills/spec-to-plan/references/step-3-execution-plan.md +0 -218
- package/skills/spec-to-plan/workflow-assets/dist/index.d.ts +0 -146
- package/skills/spec-to-plan/workflow-assets/dist/index.d.ts.map +0 -1
- package/skills/spec-to-plan/workflow-assets/dist/index.js +0 -7525
- package/skills/spec-to-plan/workflow-assets/dist/invariants.d.ts +0 -6
- package/skills/spec-to-plan/workflow-assets/dist/invariants.d.ts.map +0 -1
- package/skills/spec-to-plan/workflow-assets/skills/to-plan/SKILL.md +0 -35
- package/skills/spec-to-plan/workflow-assets/skills/to-plan/scripts/invariants.js +0 -1
- package/skills/spec-to-plan/workflow-assets/skills/to-plan/templates/implementation-plan/default.md +0 -44
- package/skills/spec-to-plan/workflow-assets/skills/to-plan/workflows/to-plan/def.yaml +0 -85
- package/skills/specify/SKILL.md +0 -154
- package/skills/specify/assets/app-spec-template.md +0 -143
- package/skills/specify/assets/spec-template.md +0 -299
- package/skills/specify/references/integration-tests.md +0 -72
- package/skills/specify/references/us-to-fr.md +0 -40
- package/skills/specify/references/writing-good-requirements.md +0 -61
|
@@ -1,6 +0,0 @@
|
|
|
1
|
-
import { InvariantEvaluator } from '@agent-ix/workflow-core';
|
|
2
|
-
export declare const artifactFrontmatterValid: InvariantEvaluator;
|
|
3
|
-
export declare const artifactRelationshipsResolve: InvariantEvaluator;
|
|
4
|
-
export declare function clearProjectRegistryCache(): void;
|
|
5
|
-
export declare const specInvariants: Record<string, InvariantEvaluator>;
|
|
6
|
-
//# sourceMappingURL=invariants.d.ts.map
|
|
@@ -1 +0,0 @@
|
|
|
1
|
-
{"version":3,"file":"invariants.d.ts","sourceRoot":"","sources":["../src/invariants.ts"],"names":[],"mappings":"AACA,OAAO,EAEL,KAAK,kBAAkB,EACxB,MAAM,yBAAyB,CAAC;AAqDjC,eAAO,MAAM,wBAAwB,EAAE,kBAqHtC,CAAC;AAIF,eAAO,MAAM,4BAA4B,EAAE,kBAiG1C,CAAC;AA4DF,wBAAgB,yBAAyB,IAAI,IAAI,CAEhD;AAED,eAAO,MAAM,cAAc,EAAE,MAAM,CAAC,MAAM,EAAE,kBAAkB,CAG7D,CAAC"}
|
|
@@ -1,35 +0,0 @@
|
|
|
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.
|
|
@@ -1 +0,0 @@
|
|
|
1
|
-
export { specInvariants as invariants } from "../../../dist/index.js";
|
|
@@ -1,30 +0,0 @@
|
|
|
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.
|
|
@@ -1,82 +0,0 @@
|
|
|
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
|
|
@@ -1,125 +0,0 @@
|
|
|
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.
|
|
@@ -1,118 +0,0 @@
|
|
|
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)`.
|
|
@@ -1,92 +0,0 @@
|
|
|
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
|
-
|
|
56
|
-
> **`--scope` is the repository root, and must be passed explicitly.** Since quire-cli
|
|
57
|
-
> v0.16.0 (quire-rs CR-045) the command derives **two roots** from it and never
|
|
58
|
-
> interchanges them: spec documents are read from `<repo>/spec` only, trace tags from
|
|
59
|
-
> the source tree at `<repo>` excluding `spec/`. A repo with no `spec/` exits with a
|
|
60
|
-
> diagnostic naming the missing document root rather than scanning the whole tree, and a
|
|
61
|
-
> matrix outside `spec/` (a fixture, a `plan/` copy) mints nothing. A relative glob
|
|
62
|
-
> resolves under `--scope` only in scoped mode (no `--module`); with `--module` it
|
|
63
|
-
> resolves against the process working directory, and an omitted `--scope` defaults to
|
|
64
|
-
> `.` — so a run launched from a parent directory validates the **wrong tree** and exits
|
|
65
|
-
> 0 for whatever it matched. Check `quire --version` ≥ 0.16.0 before relying on any of
|
|
66
|
-
> this; ≤ 0.15.0 has the pre-split traversal semantics.
|
|
67
|
-
|
|
68
|
-
- The docs sync into filament-core as `SpecReview` artifacts; do not proceed to
|
|
69
|
-
implementation until reviewed.
|
|
70
|
-
|
|
71
|
-
## Enforced runs (workflow mode)
|
|
72
|
-
|
|
73
|
-
`quoin review` drives this through `ix-flow`, which **records the chosen set and hard-blocks
|
|
74
|
-
acceptance until every selected analysis has produced a validated `SpecReview` doc** (the
|
|
75
|
-
`selected_analyses_covered` gate). Use it when you want the choice enforced rather than
|
|
76
|
-
trusted to discipline. The per-analysis `SpecReview` structure + the findings table are
|
|
77
|
-
defined in the workflow skill (`workflow-assets/skills/review/SKILL.md`).
|
|
78
|
-
|
|
79
|
-
## Common Issues
|
|
80
|
-
|
|
81
|
-
- Vague Criteria: "Fast", "User-friendly". -> Make measurable.
|
|
82
|
-
- Missing Errors: Only happy path. -> Add error modes.
|
|
83
|
-
- No Coverage: AC without TC. -> Add tests.
|
|
84
|
-
- Inconsistent IDs: `US-1` instead of `US-001`. -> Fix formatting.
|
|
85
|
-
|
|
86
|
-
## Output contract
|
|
87
|
-
|
|
88
|
-
The `SpecReview` this skill emits carries `analysis: base` — the generic review value — this skill runs the analysis lenses and writes one document per lens, so it is the default rather than a lens of its own.
|
|
89
|
-
|
|
90
|
-
Stated here because nothing checked it (quoin#202): a skill and its declared
|
|
91
|
-
output were unlinked, so drift between them was invisible until a document
|
|
92
|
-
failed validation in an unrelated session.
|
|
@@ -1,50 +0,0 @@
|
|
|
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.
|