@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.
- package/README.md +8 -258
- package/bin/launcher.js +138 -0
- package/package.json +22 -119
- 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-BkgwDKvQ.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-C3bSmPD_.js +0 -340
- package/dist/base-CqKNs2Kd.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/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/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 -140
- 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/record.d.ts +0 -10
- package/dist/commands/measurement/record.d.ts.map +0 -1
- package/dist/commands/measurement/record.js +0 -35
- 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 -15
- package/dist/commands/report.d.ts.map +0 -1
- package/dist/commands/report.js +0 -70
- 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/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-DamWradt.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/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 -55
- package/dist/evidence/adapters/types.d.ts.map +0 -1
- package/dist/evidence/index.d.ts +0 -24
- 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-DD0CHzJ0.js +0 -533
- package/dist/flow-command-BfFNY0Rv.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/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 -12
- package/dist/index.d.ts.map +0 -1
- package/dist/index.js +0 -10
- package/dist/measurement/compare.d.ts +0 -4
- package/dist/measurement/compare.d.ts.map +0 -1
- package/dist/measurement/index.d.ts +0 -9
- package/dist/measurement/index.d.ts.map +0 -1
- package/dist/measurement/plans.d.ts +0 -4
- package/dist/measurement/plans.d.ts.map +0 -1
- package/dist/measurement/portfolio.d.ts +0 -48
- 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 -44
- package/dist/measurement/report.d.ts.map +0 -1
- package/dist/measurement/store.d.ts +0 -7
- package/dist/measurement/store.d.ts.map +0 -1
- package/dist/measurement/types.d.ts +0 -83
- 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-CzB74Q07.js +0 -595
- package/dist/modules-ez9httBA.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-C-ta0llj.js +0 -77
- package/dist/plugins.d.ts +0 -13
- package/dist/plugins.d.ts.map +0 -1
- package/dist/quire/contract.d.ts +0 -87
- 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 -12
- 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 -34
- package/dist/quire/validate.d.ts.map +0 -1
- package/dist/quire-D8tCpgyA.js +0 -4961
- package/dist/schemas/coverage-v1.schema.json +0 -1111
- package/dist/schemas/properties-v1.schema.json +0 -159
- package/dist/store--2sAv12X.js +0 -219
- 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-Dg0e6CZU.js +0 -17
- package/dist/version.d.ts +0 -3
- package/dist/version.d.ts.map +0 -1
- package/dist/write-DElwS9xc.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 -63
- package/skills/gap-analysis/references/step-5-semantic-review.md +0 -51
- package/skills/gap-analysis/references/step-6-specreview-artifact.md +0 -107
- 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 -132
- 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,51 +0,0 @@
|
|
|
1
|
-
# Step 5: Semantic Review (OPTIONAL)
|
|
2
|
-
|
|
3
|
-
**Goal**: Go beyond presence and traceability to *meaning* — for each requirement↔test↔code
|
|
4
|
-
triple, judge whether they actually agree. This is the expensive, judgment-heavy pass.
|
|
5
|
-
|
|
6
|
-
## Gate first
|
|
7
|
-
|
|
8
|
-
**Do not run this step unless the user opts in.** Ask explicitly:
|
|
9
|
-
|
|
10
|
-
> Run the optional semantic review (intent↔test↔code)? It's slower but verifies tests truly
|
|
11
|
-
> validate requirement intent and exercise real code, and that code matches intent.
|
|
12
|
-
|
|
13
|
-
If declined, skip and note "semantic review: skipped" in the SpecReview `## Coverage`.
|
|
14
|
-
|
|
15
|
-
## What to judge (per requirement)
|
|
16
|
-
|
|
17
|
-
For each requirement (FR/US/StR) in scope, with its tagged test(s) (from Step 3) and the
|
|
18
|
-
code it governs (from Step 4), assess three axes:
|
|
19
|
-
|
|
20
|
-
1. **(a) Test validates intent** — does the test actually check the *behavior the
|
|
21
|
-
requirement describes*, including its acceptance criteria, or only an incidental/trivial
|
|
22
|
-
aspect? A test tagged `FR-007-AC-1` that asserts something unrelated to AC-1 fails here.
|
|
23
|
-
2. **(b) Test exercises the code** — does the test run the real implementation, or is it
|
|
24
|
-
hollow? Reuse the implementation-gap-analysis **test-stub / coverage-inflation**
|
|
25
|
-
heuristics: no assertions, weak-only assertions (`is not None`, `isinstance`),
|
|
26
|
-
mock-everything (no real code path), import-only, circular-mock-of-a-stub.
|
|
27
|
-
3. **(c) Code matches intent** — does the implementation actually do what the requirement
|
|
28
|
-
says (semantics, edge cases, error behavior), or has it drifted?
|
|
29
|
-
|
|
30
|
-
Each failing axis → a finding:
|
|
31
|
-
- `high` — test does not validate intent **or** does not exercise code (false confidence),
|
|
32
|
-
or code contradicts the requirement.
|
|
33
|
-
- `medium` — partial validation, meaningful edge cases unchecked, minor drift.
|
|
34
|
-
|
|
35
|
-
`Refs` = `FR-xxx` + test path + `path::symbol`.
|
|
36
|
-
|
|
37
|
-
## How to run it (thoroughness)
|
|
38
|
-
|
|
39
|
-
Fan out for breadth and independence — **one subagent per FR (or per cohesive area)**, each
|
|
40
|
-
returning a structured verdict per axis. Then aggregate the findings. This keeps each
|
|
41
|
-
judgment focused and lets many run concurrently. For a small scope, a single pass is fine.
|
|
42
|
-
|
|
43
|
-
## Output of this step
|
|
44
|
-
|
|
45
|
-
Per-requirement semantic findings (axis a/b/c failures) with `Refs`, plus a note for
|
|
46
|
-
`## Coverage` that semantic review ran and over how many requirements.
|
|
47
|
-
|
|
48
|
-
## Notes
|
|
49
|
-
|
|
50
|
-
- Keep verdicts evidence-based: quote the requirement clause, the assertion, and the code
|
|
51
|
-
line that justify the finding. Avoid speculative "looks wrong" calls.
|
|
@@ -1,107 +0,0 @@
|
|
|
1
|
-
# Step 6: SpecReview Artifact
|
|
2
|
-
|
|
3
|
-
**Goal**: Emit the findings from Steps 1–5 as a single **quire-validated `SpecReview`**
|
|
4
|
-
document with a Verdict, at `reviews/YY-MM-DD-<slug>.md`.
|
|
5
|
-
|
|
6
|
-
## Fetch the template, then author (guardrail)
|
|
7
|
-
|
|
8
|
-
The `SpecReview` archetype lives in `spec-artifacts-process`. Fetch its skeleton first, then
|
|
9
|
-
author, then validate (the ecosystem direct-render-then-validate model):
|
|
10
|
-
|
|
11
|
-
```
|
|
12
|
-
quoin write --types SpecReview
|
|
13
|
-
```
|
|
14
|
-
|
|
15
|
-
If `quoin write` is unavailable in the working tree, read the skeleton directly from
|
|
16
|
-
`~/.ix/filament/modules/spec-artifacts-process/skeletons/SpecReview.md`.
|
|
17
|
-
|
|
18
|
-
## Frontmatter
|
|
19
|
-
|
|
20
|
-
```yaml
|
|
21
|
-
---
|
|
22
|
-
id: SR-001 # ^[A-Z]{2,4}-[0-9]+$ — SR- default is fine; bump if SR-001 exists
|
|
23
|
-
title: "Gap analysis — <Plan-id> <slug>"
|
|
24
|
-
type: SpecReview
|
|
25
|
-
analysis: gap-analysis # the dedicated analysis value
|
|
26
|
-
scope: "plan/<Plan-id>-<slug>/, spec/matrix.md"
|
|
27
|
-
review_set: subset
|
|
28
|
-
relationships:
|
|
29
|
-
- { target: "ix://<org>/<component>/<Plan-id>", type: reviews }
|
|
30
|
-
- { target: "ix://<org>/<component>/<TestMatrix-id>", type: references }
|
|
31
|
-
---
|
|
32
|
-
```
|
|
33
|
-
|
|
34
|
-
`<org>`/`<component>` come from `spec/spec.md` (`org`, `name`); the `<Plan-id>` and
|
|
35
|
-
`<TestMatrix-id>` from Step 1.
|
|
36
|
-
|
|
37
|
-
## Body
|
|
38
|
-
|
|
39
|
-
`## Summary` and `## Findings` are **required and validated** by `quire validate`; the others
|
|
40
|
-
are extra sections (allowed).
|
|
41
|
-
|
|
42
|
-
```markdown
|
|
43
|
-
## Summary
|
|
44
|
-
|
|
45
|
-
<1–2 sentences: what plan/matrix/code was audited and the headline result.>
|
|
46
|
-
|
|
47
|
-
## Verdict
|
|
48
|
-
|
|
49
|
-
**PASS | CONDITIONAL | FAIL** — <one line justifying the gate, per the verdict rule>.
|
|
50
|
-
|
|
51
|
-
## Findings
|
|
52
|
-
|
|
53
|
-
| ID | Severity | Summary | Refs |
|
|
54
|
-
| ------- | -------- | ------------------------------------------------ | ------------------ |
|
|
55
|
-
| FND-001 | high | Task-007 still in_progress (P0, critical path) | Task-007, FR-004 |
|
|
56
|
-
| FND-002 | high | Matrix TC-012 has no backing tagged test | TC-012, FR-006 |
|
|
57
|
-
| FND-003 | medium | `cli.ts::--force` flag has no owning requirement | cli.ts::--force |
|
|
58
|
-
|
|
59
|
-
## Coverage
|
|
60
|
-
|
|
61
|
-
- Reconciliation: quire coverage (module <name> <version>) | grep fallback — no active module declares a traceability model
|
|
62
|
-
- Tasks done: X / Y
|
|
63
|
-
- Rows backed by a tagged test: X / Y (from `totals`; `0 / 0` means the model matched nothing, not full coverage)
|
|
64
|
-
- Untraced behaviors / stubs: N
|
|
65
|
-
- Semantic review: ran over N requirements | skipped
|
|
66
|
-
```
|
|
67
|
-
|
|
68
|
-
The reconciliation line is not optional. A number from the engine and a number from a grep
|
|
69
|
-
are not the same claim — grep matches a tag wherever it sits, including places the engine
|
|
70
|
-
will not bind it — and a reader cannot tell which they are looking at unless it says so.
|
|
71
|
-
|
|
72
|
-
### Findings table contract (validated)
|
|
73
|
-
|
|
74
|
-
- Headers EXACTLY: `ID | Severity | Summary | Refs`.
|
|
75
|
-
- `ID` matches `^FND-\d+$`; ≥1 row.
|
|
76
|
-
- `Severity` ∈ `low | medium | high`.
|
|
77
|
-
- A clean audit still records one row: `FND-001 | low | No gaps found | -`.
|
|
78
|
-
|
|
79
|
-
## Verdict rule
|
|
80
|
-
|
|
81
|
-
- **FAIL** — any incomplete/blocked task, any unbacked matrix Test Case, or any `high` finding.
|
|
82
|
-
- **CONDITIONAL** — only `medium`/`low` findings.
|
|
83
|
-
- **PASS** — no gaps (single `No gaps found` row).
|
|
84
|
-
|
|
85
|
-
## Validate
|
|
86
|
-
|
|
87
|
-
```
|
|
88
|
-
quire validate --scope <project_root> "reviews/**/*.md"
|
|
89
|
-
```
|
|
90
|
-
|
|
91
|
-
**Always pass `--scope <project_root>` explicitly, as above.** A relative glob resolves
|
|
92
|
-
under `--scope` only in scoped mode (no `--module`); with `--module` it resolves against
|
|
93
|
-
the process working directory, and an omitted `--scope` defaults to `.`. A sweep launched
|
|
94
|
-
from a parent directory therefore validates the **wrong tree** and exits 0 for whatever
|
|
95
|
-
it did match — that is the trap. (A glob matching *nothing* is not silent: the CLI exits
|
|
96
|
-
1 with `document glob matched no files`. Only the wrong-tree half is quiet.)
|
|
97
|
-
|
|
98
|
-
Fix any validation error (frontmatter pattern, `analysis` enum, findings headers/ids/severity)
|
|
99
|
-
before reporting completion. Then tell the user the artifact path and the Verdict.
|
|
100
|
-
|
|
101
|
-
## Notes
|
|
102
|
-
|
|
103
|
-
- File name: `reviews/<YYYY-MM-DD>-<short-slug>.md` (today's real date; slug from the plan,
|
|
104
|
-
e.g. `2026-06-22-plan-002-packaging`).
|
|
105
|
-
- `reviews/` is **repo root** for this skill (deliberate); validation is path-agnostic.
|
|
106
|
-
- One run → one SpecReview doc (the `analysis: gap-analysis` lens), matching the one-doc-per-
|
|
107
|
-
analysis model used by `quoin:spec-review`.
|
|
@@ -1,51 +0,0 @@
|
|
|
1
|
-
---
|
|
2
|
-
name: spec-app-review
|
|
3
|
-
description: Review an application-type spec for completeness against UI rendering requirements and golden-path structure.
|
|
4
|
-
---
|
|
5
|
-
|
|
6
|
-
# Review Application Specification
|
|
7
|
-
|
|
8
|
-
Validate a `component_type: application` spec against what the spec-editor-ui **actually renders** and the structural requirements from `specify`.
|
|
9
|
-
|
|
10
|
-
## When to Use
|
|
11
|
-
|
|
12
|
-
- After creating or updating an application spec
|
|
13
|
-
- Before submitting a spec for formal review
|
|
14
|
-
- When debugging why sections appear empty in the spec-editor-ui Application Detail view
|
|
15
|
-
|
|
16
|
-
## Process
|
|
17
|
-
|
|
18
|
-
1. **Locate spec**: Read `spec/spec.md` in the target repo. Verify `component_type: application` in frontmatter.
|
|
19
|
-
2. **Run checklist**: Evaluate every item in [references/checklist.md](references/checklist.md).
|
|
20
|
-
3. **Report findings**: Group issues by severity (FAIL = will break UI, WARN = degraded display, INFO = quality improvement).
|
|
21
|
-
4. **Fix or flag**: If instructed to fix, apply corrections. Otherwise, output the report.
|
|
22
|
-
|
|
23
|
-
## Quick Reference
|
|
24
|
-
|
|
25
|
-
The spec-editor-ui `ApplicationDetailPage` has 7 tabs. Each tab extracts data from specific sections/artifacts:
|
|
26
|
-
|
|
27
|
-
| Tab | Data Source |
|
|
28
|
-
|-----|------------|
|
|
29
|
-
| Overview | Purpose, In Scope, Out of Scope, Operational Boundaries, API Endpoints, Components (catalog), Standards (frontmatter) |
|
|
30
|
-
| Architecture | Mermaid diagrams (tagged `logical`/`deployment`), FR diagrams, Aggregated Objects (catalog) |
|
|
31
|
-
| Integration | Artifacts with `tags: [integration]` in frontmatter |
|
|
32
|
-
| Security | Trust Boundaries table, artifacts with `tags: [security]`, Standards |
|
|
33
|
-
| Requirements | StR/US/FR/NFR tables parsed from spec.md |
|
|
34
|
-
| Decisions | ADR artifacts (`type: ADR`) or inline ADR sections |
|
|
35
|
-
| Spec | Raw markdown rendering |
|
|
36
|
-
|
|
37
|
-
## Key Parsing Rules (Quire Library)
|
|
38
|
-
|
|
39
|
-
These are the **exact** parser behaviors that determine whether content renders:
|
|
40
|
-
|
|
41
|
-
- **Out of Scope**: `parseDelegations()` only recognizes `(Handled by X)` or `(Delegated to X)` patterns. Other parentheticals won't extract delegation targets.
|
|
42
|
-
- **In Scope**: `parseBulletList()` default pattern is `bold-description` (`**Title** — Description`). Plain bullets fall back to title-only.
|
|
43
|
-
- **Operational Boundaries**: `parseBulletList({ pattern: 'bold-colon' })` requires `**Name**: detail` format.
|
|
44
|
-
- **Trust Boundaries**: `parseTable()` on section "Trust Boundaries" — expects 3 columns: Role, Capabilities, Restrictions.
|
|
45
|
-
- **Mermaid tags**: `findDiagramByTag()` matches `%% @type: logical` and `%% @type: deployment` comments in mermaid blocks.
|
|
46
|
-
- **Integration tab**: Filters artifacts by `tags: [integration]` in YAML frontmatter (case-insensitive).
|
|
47
|
-
- **Security tab**: Filters artifacts by `tags: [security]` in YAML frontmatter.
|
|
48
|
-
|
|
49
|
-
## Golden Reference
|
|
50
|
-
|
|
51
|
-
Use a known well-formed application spec in your org as a comparison reference when reviewing.
|
|
@@ -1,197 +0,0 @@
|
|
|
1
|
-
# Application Spec Review Checklist
|
|
2
|
-
|
|
3
|
-
Evaluate each item. Report as FAIL (breaks UI), WARN (degraded display), or INFO (quality).
|
|
4
|
-
|
|
5
|
-
---
|
|
6
|
-
|
|
7
|
-
## 1. Frontmatter (spec.md)
|
|
8
|
-
|
|
9
|
-
- [ ] `type: master-requirements` is set
|
|
10
|
-
- [ ] `component_type: application` is set
|
|
11
|
-
- [ ] `name` matches repo name
|
|
12
|
-
- [ ] `org: <your-org>` is set
|
|
13
|
-
- [ ] `depends_on` lists all component repos
|
|
14
|
-
- [ ] `standards_alignment` includes at least `iso-iec-ieee-29148`
|
|
15
|
-
- [ ] `tags` is a non-empty array (renders in MasterRequirementsViewer)
|
|
16
|
-
- [ ] `security_critical` is set (boolean)
|
|
17
|
-
|
|
18
|
-
**Severity**: FAIL if `type` or `component_type` wrong (UI won't route to app view). WARN for missing tags.
|
|
19
|
-
|
|
20
|
-
---
|
|
21
|
-
|
|
22
|
-
## 2. Required Sections (spec.md)
|
|
23
|
-
|
|
24
|
-
The `parseSpec()` function in `ApplicationDetailPage.tsx` extracts these by heading name. Section names must match exactly (case-insensitive heading search via Quire `section()`).
|
|
25
|
-
|
|
26
|
-
### 2.1 Purpose
|
|
27
|
-
- [ ] Section titled `Purpose` exists
|
|
28
|
-
- [ ] Contains 2-3 sentences describing what the app solves
|
|
29
|
-
|
|
30
|
-
**Severity**: WARN if missing (falls back to `repo.description`)
|
|
31
|
-
|
|
32
|
-
### 2.2 Scope Boundaries
|
|
33
|
-
- [ ] Section titled `Scope Boundaries` exists
|
|
34
|
-
|
|
35
|
-
**Severity**: WARN (card hidden if missing)
|
|
36
|
-
|
|
37
|
-
### 2.3 In Scope
|
|
38
|
-
- [ ] Subsection titled `In Scope` exists
|
|
39
|
-
- [ ] Content is a bullet list (`- Item`)
|
|
40
|
-
- [ ] For rich display: use `**Title** — Description` format per bullet
|
|
41
|
-
|
|
42
|
-
**Severity**: WARN (shows "Not defined in spec")
|
|
43
|
-
|
|
44
|
-
### 2.4 Out of Scope
|
|
45
|
-
- [ ] Subsection titled `Out of Scope` exists
|
|
46
|
-
- [ ] Each bullet uses `(Handled by X)` or `(Delegated to X)` parenthetical
|
|
47
|
-
- [ ] Do NOT use `(deferred to ...)`, `(future work)`, or other patterns — `parseDelegations()` regex: `/\((?:handled by|delegated to)\s+(.+?)\)/i`
|
|
48
|
-
|
|
49
|
-
**Severity**: WARN if section missing. INFO if delegation format wrong (items render but without arrow delegation labels).
|
|
50
|
-
|
|
51
|
-
### 2.5 Operational Boundaries
|
|
52
|
-
- [ ] Subsection titled `Operational Boundaries` exists
|
|
53
|
-
- [ ] Each bullet uses `**Name**: description` format (bold-colon pattern)
|
|
54
|
-
|
|
55
|
-
**Severity**: WARN (shows "Not defined" in Design Principles card)
|
|
56
|
-
|
|
57
|
-
### 2.6 Architecture Rationale
|
|
58
|
-
- [ ] Section titled `Architecture Rationale` exists
|
|
59
|
-
- [ ] Contains at least ADR-001
|
|
60
|
-
|
|
61
|
-
**Severity**: WARN (Decisions tab empty)
|
|
62
|
-
|
|
63
|
-
---
|
|
64
|
-
|
|
65
|
-
## 3. Mermaid Diagrams
|
|
66
|
-
|
|
67
|
-
### 3.1 Logical View
|
|
68
|
-
- [ ] At least one mermaid code block exists in spec.md
|
|
69
|
-
- [ ] The primary dependency graph has `%% @type: logical` comment on line 1 (inside the fence)
|
|
70
|
-
- [ ] Falls back to first diagram if no tag — but tag is recommended
|
|
71
|
-
|
|
72
|
-
**Severity**: WARN (Architecture tab shows no logical view)
|
|
73
|
-
|
|
74
|
-
### 3.2 Deployment View
|
|
75
|
-
- [ ] A second mermaid code block with `%% @type: deployment` exists
|
|
76
|
-
- [ ] Shows namespace, pods, ingress, secrets, databases
|
|
77
|
-
|
|
78
|
-
**Severity**: WARN (Architecture tab deployment toggle hidden)
|
|
79
|
-
|
|
80
|
-
---
|
|
81
|
-
|
|
82
|
-
## 4. Requirement Tables (spec.md)
|
|
83
|
-
|
|
84
|
-
These tables are parsed by `parseTable()` on the section content. Column order matters (positional extraction).
|
|
85
|
-
|
|
86
|
-
### 4.1 Stakeholder Requirements
|
|
87
|
-
- [ ] Section `Stakeholder Requirements` exists with table
|
|
88
|
-
- [ ] Table columns: `ID | Title | Artifact`
|
|
89
|
-
- [ ] At least 1 StR row
|
|
90
|
-
|
|
91
|
-
### 4.2 User Stories
|
|
92
|
-
- [ ] Section `User Stories` exists with table
|
|
93
|
-
- [ ] Table columns: `ID | Title | Role | Artifact`
|
|
94
|
-
- [ ] Multiple US covering different roles
|
|
95
|
-
|
|
96
|
-
### 4.3 Functional Requirements
|
|
97
|
-
- [ ] Section `Functional Requirements` exists with table
|
|
98
|
-
- [ ] Table columns: `ID | Title | Object Type | Artifact`
|
|
99
|
-
- [ ] Required object types present:
|
|
100
|
-
- [ ] `domain` (FR-001: bounded context + ER diagram)
|
|
101
|
-
- [ ] `process` (at least 1 cross-service workflow)
|
|
102
|
-
- [ ] `configuration` (shared config across services)
|
|
103
|
-
- [ ] `integration` (consumer contract)
|
|
104
|
-
|
|
105
|
-
### 4.4 Non-Functional Requirements
|
|
106
|
-
- [ ] Section `Non-Functional Requirements` exists with table
|
|
107
|
-
- [ ] Table columns: `ID | Title | Artifact`
|
|
108
|
-
- [ ] Required NFRs:
|
|
109
|
-
- [ ] Security Constraints (NFR-001)
|
|
110
|
-
- [ ] System Reliability (NFR-002)
|
|
111
|
-
- [ ] Deployment Topology (NFR-003)
|
|
112
|
-
|
|
113
|
-
**Severity**: FAIL if tables missing (Requirements tab empty). WARN if required object types absent.
|
|
114
|
-
|
|
115
|
-
---
|
|
116
|
-
|
|
117
|
-
## 5. Security Model (spec.md)
|
|
118
|
-
|
|
119
|
-
### 5.1 Trust Boundaries
|
|
120
|
-
- [ ] Section titled `Trust Boundaries` exists (under Security Model)
|
|
121
|
-
- [ ] Contains a table with 3 columns: Role | Capabilities | Restrictions
|
|
122
|
-
- [ ] Includes at minimum: anonymous, user, admin, operator roles
|
|
123
|
-
|
|
124
|
-
**Severity**: WARN (Security tab shows "No security trust boundaries defined")
|
|
125
|
-
|
|
126
|
-
---
|
|
127
|
-
|
|
128
|
-
## 6. Artifact Frontmatter Tags
|
|
129
|
-
|
|
130
|
-
The Integration and Security tabs discover artifacts via `tags` in individual artifact YAML frontmatter, not from spec.md.
|
|
131
|
-
|
|
132
|
-
### 6.1 Integration Artifacts
|
|
133
|
-
- [ ] FR with `object: integration` also has `tags: [integration]` in frontmatter
|
|
134
|
-
- [ ] Without this tag, Integration tab shows "No integration contracts found"
|
|
135
|
-
|
|
136
|
-
### 6.2 Security Artifacts
|
|
137
|
-
- [ ] NFR-001 (Security) has `tags: [security]` in frontmatter
|
|
138
|
-
- [ ] Without this tag, Security tab falls back to parsed NFR table only (no full content rendering)
|
|
139
|
-
|
|
140
|
-
**Severity**: WARN (tabs show empty/fallback states)
|
|
141
|
-
|
|
142
|
-
---
|
|
143
|
-
|
|
144
|
-
## 7. Individual Artifact Quality
|
|
145
|
-
|
|
146
|
-
For each artifact file (StR, US, FR, NFR):
|
|
147
|
-
|
|
148
|
-
### 7.1 Frontmatter
|
|
149
|
-
- [ ] `id` matches filename pattern (e.g., `FR-001`)
|
|
150
|
-
- [ ] `title` is present and descriptive
|
|
151
|
-
- [ ] `type` matches the directory (StR, US, FR, NFR)
|
|
152
|
-
|
|
153
|
-
### 7.2 Heading
|
|
154
|
-
- [ ] H1 follows pattern: `# [ID] Title`
|
|
155
|
-
- [ ] ID in brackets matches frontmatter `id`
|
|
156
|
-
|
|
157
|
-
### 7.3 Acceptance Criteria (FR, NFR)
|
|
158
|
-
- [ ] AC table exists with columns: `ID | Criteria | Verification Method`
|
|
159
|
-
- [ ] AC IDs follow pattern: `{artifact-id}-AC-{n}` (e.g., `FR-001-AC-1`)
|
|
160
|
-
|
|
161
|
-
### 7.4 Constraints (FR, NFR)
|
|
162
|
-
- [ ] Constraint table with columns: `ID | Constraint | Type | Rationale | Validation`
|
|
163
|
-
- [ ] Constraint IDs follow pattern: `{artifact-id}-CON-{n}`
|
|
164
|
-
|
|
165
|
-
### 7.5 Traceability
|
|
166
|
-
- [ ] `From:` and `Drives:` links present (or Traceability table)
|
|
167
|
-
- [ ] References are bidirectional (if FR-001 drives FR-002, FR-002 traces from FR-001)
|
|
168
|
-
|
|
169
|
-
### 7.6 User Stories
|
|
170
|
-
- [ ] AC use H3 headings with IDs: `### US-001-AC-1: Title`
|
|
171
|
-
- [ ] `From:` traces to StR, `Drives:` traces to FR
|
|
172
|
-
|
|
173
|
-
**Severity**: INFO for most. WARN if AC IDs missing (test matrix can't trace).
|
|
174
|
-
|
|
175
|
-
---
|
|
176
|
-
|
|
177
|
-
## 8. Test Matrix (tests.md)
|
|
178
|
-
|
|
179
|
-
- [ ] File `spec/tests.md` exists
|
|
180
|
-
- [ ] Coverage table maps every AC to at least one TC
|
|
181
|
-
- [ ] TC entries include Type and Priority, each a single value from the
|
|
182
|
-
enforced vocabularies (see `spec-matrix/SKILL.md` § Test Case Summary —
|
|
183
|
-
`Security` is not one of them; a security test takes the Type that
|
|
184
|
-
describes how it runs)
|
|
185
|
-
- [ ] Component ownership note explains which repo runs each TC
|
|
186
|
-
- [ ] Constraint boundary tests section maps CON IDs to TCs
|
|
187
|
-
|
|
188
|
-
**Severity**: WARN if missing (no test traceability)
|
|
189
|
-
|
|
190
|
-
---
|
|
191
|
-
|
|
192
|
-
## 9. Cross-Reference Integrity
|
|
193
|
-
|
|
194
|
-
- [ ] Every artifact linked in spec.md tables exists as a file
|
|
195
|
-
- [ ] Every `From:` / `Drives:` reference resolves to a real artifact ID
|
|
196
|
-
- [ ] `depends_on` in frontmatter matches Component Registry table
|
|
197
|
-
- [ ] FR relationship targets (e.g., `ix://<your-org>/...`) use valid repo names
|
|
@@ -1,30 +0,0 @@
|
|
|
1
|
-
---
|
|
2
|
-
name: spec-architecture-evaluation
|
|
3
|
-
description: Evaluate a repository's implemented architecture against its stated boundaries, quality goals, and operating scenarios, producing an evidence-backed SpecReview. Use for architecture reviews; do not use for general test-gap or code-style review.
|
|
4
|
-
---
|
|
5
|
-
|
|
6
|
-
# Architecture Evaluation
|
|
7
|
-
|
|
8
|
-
Evaluate the architecture that exists, including its specifications and code. Do not infer health from diagrams, test counts, or a single aggregate score.
|
|
9
|
-
|
|
10
|
-
## Evaluation
|
|
11
|
-
|
|
12
|
-
1. Establish the scope and named quality goals from the repository's architecture decisions, requirements, and current implementation.
|
|
13
|
-
2. Walk representative success, failure, recovery, and change scenarios across component boundaries. Follow data, control, and ownership; record the concrete files or artifacts that establish each claim.
|
|
14
|
-
3. Check whether responsibilities have one clear owner, dependencies point in the intended direction, failure and recovery cross boundaries coherently, and measurement or policy code is separated from presentation and orchestration.
|
|
15
|
-
4. For each problem, state what is wrong, where it occurs, why it matters in a named scenario, and the smallest credible repair. Distinguish a demonstrated defect from a risk that still needs measurement.
|
|
16
|
-
5. Prefer a small number of supported findings. Do not invent a numeric architecture score or treat an unavailable metric as zero.
|
|
17
|
-
|
|
18
|
-
## Output contract
|
|
19
|
-
|
|
20
|
-
Write one Quire-validated `SpecReview` under `reviews/YY-MM-DD-<slug>.md` with:
|
|
21
|
-
|
|
22
|
-
- `type: SpecReview`
|
|
23
|
-
- `analysis: architecture-evaluation`
|
|
24
|
-
- an exact `scope` and `review_set`
|
|
25
|
-
- a substantive `## Summary`
|
|
26
|
-
- a `## Findings` table with the module's required columns
|
|
27
|
-
|
|
28
|
-
Each finding must name evidence in `Refs` and contain enough location and causal detail to be actionable. If no defect is demonstrated, record a low-severity “No issues found” row and summarize the scenarios actually examined.
|
|
29
|
-
|
|
30
|
-
Validate the result with the repository's real `quire validate` command. This review is advisory evidence unless the repository separately declares it as a gate.
|
|
@@ -1,96 +0,0 @@
|
|
|
1
|
-
---
|
|
2
|
-
name: spec-correctness
|
|
3
|
-
description: Turn classified acceptance criteria into runnable property tests. Consumes
|
|
4
|
-
`quire properties --json` per-criterion records, grounds each criterion's domain,
|
|
5
|
-
precondition and oracle in the spec and the code, and emits property tests in the
|
|
6
|
-
repo's own harness (proptest / fast-check / hypothesis) keyed on `row_id`. Emits a
|
|
7
|
-
validated SpecReview recording every criterion it could not ground and why.
|
|
8
|
-
---
|
|
9
|
-
|
|
10
|
-
# Spec Correctness
|
|
11
|
-
|
|
12
|
-
Use this skill to **generate property tests from acceptance criteria you already wrote**.
|
|
13
|
-
|
|
14
|
-
`quire properties` classifies every binding acceptance criterion by property shape and
|
|
15
|
-
stops there — it names no test framework and its deterministic recall has a measured
|
|
16
|
-
ceiling. This skill closes the three gaps that leaves:
|
|
17
|
-
|
|
18
|
-
1. **The harness.** The shape→harness mapping is this skill's, not the engine's.
|
|
19
|
-
2. **The clauses.** Domain/precondition/oracle spans reach only a small minority of
|
|
20
|
-
criteria, so this skill grounds them from the spec and the code itself.
|
|
21
|
-
3. **The residue.** Criteria the deterministic pass labelled `example` or `unclassified`
|
|
22
|
-
go to an LLM second pass — review-gated, so it can afford recall the engine cannot.
|
|
23
|
-
|
|
24
|
-
Specified by [FR-028](../../spec/functional/FR-028-generate-property-tests-from-criteria.md).
|
|
25
|
-
|
|
26
|
-
## The one rule that is not negotiable
|
|
27
|
-
|
|
28
|
-
**A low extractable ratio is data, never a verdict.** This skill reports counts. It emits
|
|
29
|
-
no threshold, no grade, no pass/fail, and it never suggests rewording a criterion to score
|
|
30
|
-
better. A criterion that describes one concrete scenario is a good criterion; it just isn't
|
|
31
|
-
a property. (quire-rs FR-052-CON-1.)
|
|
32
|
-
|
|
33
|
-
Two more, inherited:
|
|
34
|
-
|
|
35
|
-
- **Never write a framework name into `spec/**`.** (CON-2.)
|
|
36
|
-
- **Never propose a new regex or lexicon entry for quire-rs.** 31.3% recall at 93.3%
|
|
37
|
-
precision is a measured ceiling, not a bug. (quire-rs#45.)
|
|
38
|
-
|
|
39
|
-
## When to use
|
|
40
|
-
|
|
41
|
-
- After acceptance criteria are written and validated, to give them verification.
|
|
42
|
-
- Before `gap-analysis`, so the matrix rows it reconciles have real backing tests.
|
|
43
|
-
- On an existing repo, to find which criteria have no test and why.
|
|
44
|
-
|
|
45
|
-
Not for: authoring criteria (`specify`), building the matrix (`spec-matrix`), or judging
|
|
46
|
-
whether existing tests are good (`gap-analysis`).
|
|
47
|
-
|
|
48
|
-
## Inputs
|
|
49
|
-
|
|
50
|
-
- The target repo and its spec glob (default `spec/**/*.md`).
|
|
51
|
-
- `quire properties --scope <repo> --json '<glob>'` output — quire-cli ≥ 0.12.0.
|
|
52
|
-
- The repo's source and test trees.
|
|
53
|
-
|
|
54
|
-
## Steps
|
|
55
|
-
|
|
56
|
-
0. **[Scope and harness](references/step-0-scope-and-harness.md)**: resolve the repo and
|
|
57
|
-
glob, run `quire properties --json`, detect the harness, test dir, and the repo's
|
|
58
|
-
existing tracking-tag style.
|
|
59
|
-
1. **[Census](references/step-1-census.md)**: bucket records by `property` × `extraction`.
|
|
60
|
-
Data only — no verdict, no threshold, no rewording suggestion.
|
|
61
|
-
2. **[Clause grounding](references/step-2-clause-grounding.md)**: derive domain,
|
|
62
|
-
precondition and oracle for each record, each cited to a `file:line`. No citation, no
|
|
63
|
-
test.
|
|
64
|
-
3. **[Strategy selection](references/step-3-strategy-selection.md)**: pick the assertion
|
|
65
|
-
skeleton from `property`, and the routing lane from `extraction`.
|
|
66
|
-
4. **[Generate tests](references/step-4-generate-tests.md)**: emit into the repo's harness
|
|
67
|
-
with the `row_id` tracking tags and the provenance line.
|
|
68
|
-
5. **[Second pass](references/step-5-second-pass.md)**: the LLM pass over `example`,
|
|
69
|
-
`unclassified`, and anything step 2 refused to ground.
|
|
70
|
-
6. **[Review artifact](references/step-6-review-artifact.md)**: the `SpecReview` at
|
|
71
|
-
`reviews/YY-MM-DD-<slug>.md` recording what could not be grounded, and why.
|
|
72
|
-
7. **[Report and handoff](references/step-7-report-and-handoff.md)**: the run report, the
|
|
73
|
-
`Property` rows for `spec-matrix`, and the reconciliation check against `gap-analysis`.
|
|
74
|
-
|
|
75
|
-
Steps 0–4 and 6–7 always run. Step 5 is an expensive LLM pass — **ask before running it**
|
|
76
|
-
when the residue is large (say, more than 30 records).
|
|
77
|
-
|
|
78
|
-
## Outputs
|
|
79
|
-
|
|
80
|
-
| Path | What |
|
|
81
|
-
| --- | --- |
|
|
82
|
-
| `tests/props/<per-harness naming>` | Property tests, all of them runnable |
|
|
83
|
-
| `reviews/YY-MM-DD-<slug>.md` | A `SpecReview` (`analysis: spec-correctness`) recording what could not be grounded |
|
|
84
|
-
|
|
85
|
-
Nothing else is written to the tree (FR-028-CON-1). No skipped tests, no `_review/`
|
|
86
|
-
directory, no ad-hoc report file. A generated test arrives in a pull request, and that is
|
|
87
|
-
what puts it under review; the artifact carries the one thing a PR does not — why a
|
|
88
|
-
criterion was left ungrounded.
|
|
89
|
-
|
|
90
|
-
## Two facts that will bite if you assume otherwise
|
|
91
|
-
|
|
92
|
-
- **`shape` is not `property`.** `shape` is the FR-047 grammar axis
|
|
93
|
-
(`assertion | obligation | given-when-then | unstructured`). `property` is the 10-value
|
|
94
|
-
taxonomy. **Strategy selects on `property`.** Routing selects on `extraction`.
|
|
95
|
-
- **StR scores highest, not lowest** — 29.1% against FR's 19.2%. Do not down-weight
|
|
96
|
-
stakeholder requirements (quire-rs CR-029 falsified the CR-020 prediction).
|
|
@@ -1,101 +0,0 @@
|
|
|
1
|
-
# Strategy Table
|
|
2
|
-
|
|
3
|
-
The full `property` → test-strategy mapping. `extraction` decides the lane (see
|
|
4
|
-
`references/step-3-strategy-selection.md`); this table decides the test.
|
|
5
|
-
|
|
6
|
-
`shape` (`assertion | obligation | given-when-then | unstructured`) never appears here —
|
|
7
|
-
it is the FR-047 grammar axis, not the property axis.
|
|
8
|
-
|
|
9
|
-
---
|
|
10
|
-
|
|
11
|
-
## `round-trip`
|
|
12
|
-
|
|
13
|
-
- **Needs** two symbols, an encoder and its inverse. Only one found → no test, one finding.
|
|
14
|
-
- **Domain** the *inner* type — generate `x`, not the encoded form, so every value is
|
|
15
|
-
reachable and shrinking is meaningful.
|
|
16
|
-
- **Oracle** `dec(enc(x)) == x`.
|
|
17
|
-
- **Lossy variant** when the FR says normalization happens: `norm(dec(enc(x))) == norm(x)`.
|
|
18
|
-
Cite the FR line that states the loss; do not assume it.
|
|
19
|
-
- **Trap** encoding invalid inputs. If `enc` is partial, filter the domain rather than
|
|
20
|
-
catching an error — an error there is a different criterion.
|
|
21
|
-
|
|
22
|
-
## `idempotence`
|
|
23
|
-
|
|
24
|
-
- **Domain** `x`, **seeded with `f`'s own outputs** so the already-normalized branch is hit.
|
|
25
|
-
A generator that never produces a fixpoint tests only half the property.
|
|
26
|
-
- **Oracle** `f(f(x)) == f(x)`.
|
|
27
|
-
- **Trap** `f` that is idempotent only on valid input — add the validity precondition from
|
|
28
|
-
`## Behavior`, cited.
|
|
29
|
-
|
|
30
|
-
## `ordering`
|
|
31
|
-
|
|
32
|
-
- **Domain** `xs : list<T>`, length `0..32`. Include the empty and singleton cases; they
|
|
33
|
-
are where ordering code breaks.
|
|
34
|
-
- **Oracle — pick one by the criterion's verb**:
|
|
35
|
-
- *sorted*, *in order*, *ascending* → `is_sorted_by(key, f(xs))`
|
|
36
|
-
- *regardless of order*, *independent of order* → `f(xs) == f(shuffle(xs))`
|
|
37
|
-
- *reorders*, *preserves*, *without loss* → `multiset(f(xs)) == multiset(xs)`
|
|
38
|
-
- **Trap** asserting a total order when the criterion states a stable partial one. Sort by
|
|
39
|
-
the stated key only.
|
|
40
|
-
|
|
41
|
-
## `invariant`
|
|
42
|
-
|
|
43
|
-
- **Domain** `x : Domain`.
|
|
44
|
-
- **Oracle** `P(f(x))` for a pure function. For stateful code, generate an op sequence and
|
|
45
|
-
assert `P(state)` **after every op**, not only at the end.
|
|
46
|
-
- **`P` is the entire risk.** It must come from a `SHALL` predicate or a code-level bound,
|
|
47
|
-
cited. `assert result is not None` is not an invariant — that is a refusal.
|
|
48
|
-
|
|
49
|
-
## `error-case`
|
|
50
|
-
|
|
51
|
-
- **Domain** the **negative** one: the complement of the valid domain, built with
|
|
52
|
-
`prop_filter` / `fc.pre` / `assume`.
|
|
53
|
-
- **Oracle** two assertions, both required:
|
|
54
|
-
1. it fails with the stated error class;
|
|
55
|
-
2. the payload matches the stated shape (message fragment, exit code, error variant).
|
|
56
|
-
- **Where the error class comes from**: the code. The engine emits
|
|
57
|
-
`span:refused-weak-boundary` on these criteria, meaning it *declined* to guess the
|
|
58
|
-
boundary. Read the error enum or exception class; do not infer it from the prose.
|
|
59
|
-
- **Trap** a filter so narrow the generator exhausts. Prefer constructing the negative
|
|
60
|
-
domain directly over filtering a large valid one.
|
|
61
|
-
|
|
62
|
-
## `lifecycle`
|
|
63
|
-
|
|
64
|
-
- **Generatable only if** the states and transitions are enumerable from `## Behavior`.
|
|
65
|
-
Otherwise refuse with `no-state-machine`.
|
|
66
|
-
- **Domain** an op sequence, length `1..24`, drawn from the op set.
|
|
67
|
-
- **Oracle** per op: `sut.apply(op).ok == model.allows(op)`; then the invariant; then the
|
|
68
|
-
terminal state at the end of the sequence.
|
|
69
|
-
- The model is a few lines of plain data — a set of legal ops per state. If writing it
|
|
70
|
-
requires reimplementing the SUT, refuse instead.
|
|
71
|
-
|
|
72
|
-
## `concurrency`
|
|
73
|
-
|
|
74
|
-
- **Domain** interleaved or parallel op sequences over a small op set.
|
|
75
|
-
- **Oracle** the concurrent result is *some* linearization of the sequential model, and no
|
|
76
|
-
invariant is violated at any interleaving.
|
|
77
|
-
- **Rust** `loom` for exhaustive interleaving of a small model; `proptest-state-machine`
|
|
78
|
-
parallel mode when the op set is large.
|
|
79
|
-
- **TypeScript** `fc.scheduler()` — deterministic and shrinkable.
|
|
80
|
-
- **Python** hypothesis has no interleaving scheduler. Emit a `RuleBasedStateMachine`
|
|
81
|
-
sketch over the async model, **always with a finding** recording the downgrade.
|
|
82
|
-
|
|
83
|
-
## `universal`
|
|
84
|
-
|
|
85
|
-
- The default family and the largest bucket in practice.
|
|
86
|
-
- **Domain** the clause subject, typed from the code signature.
|
|
87
|
-
- **Oracle** a direct translation of the criterion's predicate.
|
|
88
|
-
- **Trap** translating the implementation instead of the criterion. If the assertion reads
|
|
89
|
-
like the function body, it proves nothing — re-derive from `## Behavior`.
|
|
90
|
-
|
|
91
|
-
## `example`
|
|
92
|
-
|
|
93
|
-
- **Not a property.** Step 5 owns it.
|
|
94
|
-
- May become a reclassified property (with citations) or a `Unit` witness test. A witness
|
|
95
|
-
is recorded as a finding and is **not** counted as property coverage.
|
|
96
|
-
|
|
97
|
-
## `unclassified`
|
|
98
|
-
|
|
99
|
-
- **Not a property.** Step 5 owns it.
|
|
100
|
-
- Absence of a signal is not absence of a property — but it is also not evidence of one.
|
|
101
|
-
Ground it or record nothing.
|