@agent-ix/quoin 0.23.1 → 0.26.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,32 +0,0 @@
|
|
|
1
|
-
# CC8 - Change Management
|
|
2
|
-
|
|
3
|
-
**Category**: Common Criteria
|
|
4
|
-
**Focus**: Authorization and control of changes
|
|
5
|
-
|
|
6
|
-
## When to Apply
|
|
7
|
-
|
|
8
|
-
Apply CC8 when your component:
|
|
9
|
-
- Has code or configuration changes
|
|
10
|
-
- Impacts production systems
|
|
11
|
-
- Requires testing before deployment
|
|
12
|
-
|
|
13
|
-
## Controls
|
|
14
|
-
|
|
15
|
-
| Control | Name | Description |
|
|
16
|
-
|---------|------|-------------|
|
|
17
|
-
| CC8.1 | Change Authorization | Entity authorizes, designs, develops, configures, documents, tests, approves, and implements changes |
|
|
18
|
-
|
|
19
|
-
## Mapping Guidance
|
|
20
|
-
|
|
21
|
-
CC8.1 is comprehensive and maps to:
|
|
22
|
-
- **Code review requirements** → NFR-XXX
|
|
23
|
-
- **CI/CD pipeline** → NFR-XXX
|
|
24
|
-
- **Testing requirements** → NFR-XXX
|
|
25
|
-
- **Approval workflows** → Process documentation
|
|
26
|
-
- **Rollback capability** → NFR-XXX
|
|
27
|
-
|
|
28
|
-
For software components, CC8 is typically satisfied by:
|
|
29
|
-
- Git-based version control
|
|
30
|
-
- Pull request reviews
|
|
31
|
-
- Automated testing
|
|
32
|
-
- Deployment pipelines
|
|
@@ -1,34 +0,0 @@
|
|
|
1
|
-
# CC9 - Risk Mitigation
|
|
2
|
-
|
|
3
|
-
**Category**: Common Criteria
|
|
4
|
-
**Focus**: Risk mitigation and vendor management
|
|
5
|
-
|
|
6
|
-
## When to Apply
|
|
7
|
-
|
|
8
|
-
Apply CC9 when your component:
|
|
9
|
-
- Uses third-party libraries or services
|
|
10
|
-
- Integrates with external vendors
|
|
11
|
-
- Depends on other services
|
|
12
|
-
|
|
13
|
-
## Controls
|
|
14
|
-
|
|
15
|
-
| Control | Name | Description |
|
|
16
|
-
|---------|------|-------------|
|
|
17
|
-
| CC9.1 | Risk Mitigation | Entity identifies, selects, and develops risk mitigation activities |
|
|
18
|
-
| CC9.2 | Vendor Risk | Entity assesses and manages risks associated with vendors and business partners |
|
|
19
|
-
|
|
20
|
-
## Mapping Guidance
|
|
21
|
-
|
|
22
|
-
For software components:
|
|
23
|
-
- **Dependency scanning** → CC9.1, CC9.2
|
|
24
|
-
- **Vendor security reviews** → CC9.2
|
|
25
|
-
- **Fallback mechanisms** → CC9.1
|
|
26
|
-
- **Circuit breakers** → CC9.1
|
|
27
|
-
- **Supply chain verification** → CC9.2
|
|
28
|
-
|
|
29
|
-
### Example Mappings
|
|
30
|
-
|
|
31
|
-
| Control | Typical NFR |
|
|
32
|
-
|---------|-------------|
|
|
33
|
-
| CC9.1 | NFR-XXX (fail-safe), NFR-XXX (graceful degradation) |
|
|
34
|
-
| CC9.2 | NFR-XXX (dependency policy), NFR-XXX (vendout security) |
|
|
@@ -1,46 +0,0 @@
|
|
|
1
|
-
# SOC 2 Trust Services Criteria
|
|
2
|
-
|
|
3
|
-
**Version**: 2017 TSC
|
|
4
|
-
**Scope**: Service organization controls
|
|
5
|
-
**Region**: Global (primarily US-focused)
|
|
6
|
-
|
|
7
|
-
## When to Apply
|
|
8
|
-
|
|
9
|
-
Apply SOC 2 when your component:
|
|
10
|
-
- Provides services to other businesses (B2B)
|
|
11
|
-
- Handles customer data on behalf of others
|
|
12
|
-
- Is part of a service organization's control environment
|
|
13
|
-
- Needs to demonstrate security controls to customers/auditors
|
|
14
|
-
|
|
15
|
-
## Category Selection Guide
|
|
16
|
-
|
|
17
|
-
**Use this to decide which category to investigate:**
|
|
18
|
-
|
|
19
|
-
| If your component... | Read Category |
|
|
20
|
-
|---------------------|---------------|
|
|
21
|
-
| Implements authentication | [CC6-LogicalPhysicalAccess](CC6-LogicalPhysicalAccess.md) |
|
|
22
|
-
| Implements authorization/RBAC/ABAC | [CC6-LogicalPhysicalAccess](CC6-LogicalPhysicalAccess.md) |
|
|
23
|
-
| Uses encryption or TLS | [CC6-LogicalPhysicalAccess](CC6-LogicalPhysicalAccess.md) |
|
|
24
|
-
| Produces audit logs or metrics | [CC7-SystemOperations](CC7-SystemOperations.md) |
|
|
25
|
-
| Has configuration changes | [CC8-ChangeManagement](CC8-ChangeManagement.md) |
|
|
26
|
-
| Uses third-party dependencies | [CC9-RiskMitigation](CC9-RiskMitigation.md) |
|
|
27
|
-
| Communicates with external systems | [CC2-CommunicationInformation](CC2-CommunicationInformation.md) |
|
|
28
|
-
|
|
29
|
-
## Criteria Categories
|
|
30
|
-
|
|
31
|
-
| Category | Primary For | Skip If |
|
|
32
|
-
|----------|-------------|---------|
|
|
33
|
-
| [CC1-ControlEnvironment](CC1-ControlEnvironment.md) | Governance | Always organizational |
|
|
34
|
-
| [CC2-CommunicationInformation](CC2-CommunicationInformation.md) | External APIs, docs | Internal-only |
|
|
35
|
-
| [CC3-RiskAssessment](CC3-RiskAssessment.md) | Threat modeling | Already documented |
|
|
36
|
-
| [CC4-MonitoringActivities](CC4-MonitoringActivities.md) | Health checks | Pre-production only |
|
|
37
|
-
| [CC5-ControlActivities](CC5-ControlActivities.md) | Control implementation | Covered in CC6 |
|
|
38
|
-
| [CC6-LogicalPhysicalAccess](CC6-LogicalPhysicalAccess.md) | **Auth, authz, crypto** | No access control |
|
|
39
|
-
| [CC7-SystemOperations](CC7-SystemOperations.md) | Logging, monitoring | No security events |
|
|
40
|
-
| [CC8-ChangeManagement](CC8-ChangeManagement.md) | Version control, CI/CD | All software |
|
|
41
|
-
| [CC9-RiskMitigation](CC9-RiskMitigation.md) | Dependencies, vendors | No external deps |
|
|
42
|
-
|
|
43
|
-
## Quick Reference
|
|
44
|
-
|
|
45
|
-
**Most software components**: Focus on CC6, CC7, CC8
|
|
46
|
-
**Physical controls (CC6.4-6.5)**: Assign to Infrastructure
|
|
@@ -1,46 +0,0 @@
|
|
|
1
|
-
# Security Standards Reference
|
|
2
|
-
|
|
3
|
-
Index of security standards for compliance analysis. Each standard has its own directory with chapter-level detail.
|
|
4
|
-
|
|
5
|
-
## When to Apply
|
|
6
|
-
|
|
7
|
-
**ALL standards apply to ALL components.** Apply comprehensive coverage, then scope based on component function.
|
|
8
|
-
|
|
9
|
-
| Standard | Primary Application | Key Indicator |
|
|
10
|
-
|----------|---------------------|---------------|
|
|
11
|
-
| [SOC 2](soc2/index.md) | Service organization controls | Any B2B SaaS or service provider |
|
|
12
|
-
| [ISO 27001](iso27001/index.md) | Information security management | Enterprise, international, or certified requirements |
|
|
13
|
-
| [NIST 800-53](nist-800-53/index.md) | Federal information systems | US government, federal contractors |
|
|
14
|
-
| [OWASP ASVS](owasp-asvs/index.md) | Application security verification | Web applications, APIs, mobile |
|
|
15
|
-
| [GDPR](gdpr/index.md) | EU data protection | Any EU user data processing |
|
|
16
|
-
|
|
17
|
-
## Standard Summaries
|
|
18
|
-
|
|
19
|
-
### SOC 2 (2017 TSC)
|
|
20
|
-
Trust Services Criteria for service organizations. Focuses on Security (mandatory), plus optional Availability, Processing Integrity, Confidentiality, and Privacy.
|
|
21
|
-
|
|
22
|
-
**Apply when**: Building B2B services, cloud services, or handling customer data for other organizations.
|
|
23
|
-
|
|
24
|
-
### ISO/IEC 27001:2022
|
|
25
|
-
International standard for Information Security Management Systems (ISMS). Annex A provides 93 controls across 4 themes.
|
|
26
|
-
|
|
27
|
-
**Apply when**: International operations, enterprise customers, or seeking certification.
|
|
28
|
-
|
|
29
|
-
### NIST SP 800-53 Rev 5.2.0
|
|
30
|
-
Comprehensive security and privacy controls for federal information systems. 20 control families covering all aspects of security.
|
|
31
|
-
|
|
32
|
-
**Apply when**: US federal systems, government contractors, or as comprehensive baseline.
|
|
33
|
-
|
|
34
|
-
### OWASP ASVS 5.0.0
|
|
35
|
-
Application Security Verification Standard. 14 verification areas for testing application security.
|
|
36
|
-
|
|
37
|
-
**Apply when**: Web applications, APIs, any user-facing software.
|
|
38
|
-
|
|
39
|
-
### EU GDPR 2016/679
|
|
40
|
-
General Data Protection Regulation for EU data protection and privacy.
|
|
41
|
-
|
|
42
|
-
**Apply when**: Processing personal data of EU residents.
|
|
43
|
-
|
|
44
|
-
## Quick Reference
|
|
45
|
-
|
|
46
|
-
For component-type specific guidance, see [component-type-mapping.md](component-type-mapping.md).
|
|
@@ -1,88 +0,0 @@
|
|
|
1
|
-
---
|
|
2
|
-
name: spec-to-plan
|
|
3
|
-
description: Convert ISO spec requirements (StR, FR, NFR) into a TDD-based project plan with dependency analysis, parallel execution tracks, quality gates, and task decomposition. Selects or starts a plan and writes a frontmatter-typed plan bundle under plan/<Plan-id>-<slug>/ (Plan + Task + index + log).
|
|
4
|
-
---
|
|
5
|
-
|
|
6
|
-
# Spec to Plan
|
|
7
|
-
|
|
8
|
-
This skill provides a structured workflow for converting ISO/IEC/IEEE 29148 compliant specifications into an executable, dependency-aware project plan with parallel execution tracks and quality gates.
|
|
9
|
-
|
|
10
|
-
A project may hold **multiple plans** — each a named group of tasks (e.g. "core app",
|
|
11
|
-
"packaging", "a11y hardening"). Every plan is a self-describing **bundle** under
|
|
12
|
-
`plan/<Plan-id>-<slug>/` containing an `index.md`, a `log.md`, the `plan.md` itself,
|
|
13
|
-
and a `tasks/` directory. Plans, tasks, and the index/log files are
|
|
14
|
-
**frontmatter-typed** (`Plan`, `Task`, `index`, `log`) so the dependency graph and
|
|
15
|
-
all task metadata are machine-parseable and quire-validatable.
|
|
16
|
-
|
|
17
|
-
## Purpose
|
|
18
|
-
|
|
19
|
-
Use this skill when:
|
|
20
|
-
- You are starting a new implementation effort based on an existing Spec.
|
|
21
|
-
- You want to add a *new* plan to a project that already has one or more.
|
|
22
|
-
- You need to generate a Test Plan before writing code (TDD).
|
|
23
|
-
- You want to ensure full traceability from Requirements (StR/FR/NFR) to Tests.
|
|
24
|
-
- You need to identify what can be parallelized vs what must be serial.
|
|
25
|
-
- You want quality gates to catch fundamental problems before downstream work is wasted.
|
|
26
|
-
|
|
27
|
-
## Pre-conditions (Readiness Gate)
|
|
28
|
-
|
|
29
|
-
Task generation MAY begin only when ALL of the following are true:
|
|
30
|
-
|
|
31
|
-
- All requirements are atomic and testable.
|
|
32
|
-
- Ownership is assigned (see `spec-scope-boundary-analysis`).
|
|
33
|
-
- Dependencies are known (see `spec-dependency-analysis`).
|
|
34
|
-
- Risks are classified (see `spec-risk-complexity-analysis`).
|
|
35
|
-
- Verification strategy is defined (see `spec-evidence-analysis`).
|
|
36
|
-
- Failure-domain analysis is complete (see `spec-failure-domain-analysis`).
|
|
37
|
-
|
|
38
|
-
Failure to meet these conditions WILL result in unstable tasking. If any condition is unmet, stop and complete the corresponding analysis skill first.
|
|
39
|
-
|
|
40
|
-
## Steps
|
|
41
|
-
All steps required!
|
|
42
|
-
|
|
43
|
-
0. **[Plan Selection](references/step-0-plan-selection.md)**: Select an existing plan to continue, or start a new one. Skip only if the target plan is already fixed in this session's context. Scaffolds the bundle (`index.md`, `log.md`, `tasks/`).
|
|
44
|
-
1. **[Analysis](references/step-1-analysis.md)**: Analyze the spec structure and map dependencies into the bundle's `plan.md`.
|
|
45
|
-
2. **[Test Plan](references/step-2-test-plan.md)**: Generate the list of required tests.
|
|
46
|
-
3. **[Execution Plan](references/step-3-execution-plan.md)**: Derive dependency graph, critical path, parallel tracks, quality gates, and task decomposition into frontmatter-typed `Task` files.
|
|
47
|
-
|
|
48
|
-
## Output
|
|
49
|
-
|
|
50
|
-
This skill produces or updates a **plan bundle** at `<project_root>/plan/<Plan-id>-<slug>/`:
|
|
51
|
-
|
|
52
|
-
- `plan.md` (`type: Plan`): The central living document — requirements summary,
|
|
53
|
-
dependency graph, execution tracks, quality gates, and test plan. It is an
|
|
54
|
-
**orchestration overview, not a mirror of the bundle**: ownership, the DAG, and test
|
|
55
|
-
traces are authoritative in the task frontmatter, so `plan.md` states each fact once
|
|
56
|
-
(see `references/step-3-execution-plan.md`). Frontmatter `relationships:` trace
|
|
57
|
-
(`references`) the requirements the plan covers.
|
|
58
|
-
- `tasks/Task-NNN-<slug>.md` (`type: Task`): One file per task. Frontmatter carries
|
|
59
|
-
the machine contract — `status`, `track`, `priority`, and `relationships:` edges
|
|
60
|
-
(`depends_on` for the DAG, `references` for requirement ownership, `verifies` for
|
|
61
|
-
test traces). The body holds the human sections (Scope/Subtasks/Deliverables/Notes).
|
|
62
|
-
- `index.md` (`type: index`): `## Contents` link list to `plan.md` and every task —
|
|
63
|
-
the bundle's table of contents.
|
|
64
|
-
- `log.md` (`type: log`): `## History` of dated plan lifecycle events (plan created,
|
|
65
|
-
tasks added, status changes).
|
|
66
|
-
|
|
67
|
-
Validate the bundle with:
|
|
68
|
-
`quire validate --scope <project_root> "plan/**/*.md"`
|
|
69
|
-
|
|
70
|
-
> **`--scope` is the repository root, and must be passed explicitly.** Since quire-cli
|
|
71
|
-
> v0.16.0 (quire-rs CR-045) the command derives **two roots** from it and never
|
|
72
|
-
> interchanges them: spec documents are read from `<repo>/spec` only, trace tags from
|
|
73
|
-
> the source tree at `<repo>` excluding `spec/`. A repo with no `spec/` exits with a
|
|
74
|
-
> diagnostic naming the missing document root rather than scanning the whole tree, and a
|
|
75
|
-
> matrix outside `spec/` (a fixture, a `plan/` copy) mints nothing. A relative glob
|
|
76
|
-
> resolves under `--scope` only in scoped mode (no `--module`); with `--module` it
|
|
77
|
-
> resolves against the process working directory, and an omitted `--scope` defaults to
|
|
78
|
-
> `.` — so a run launched from a parent directory validates the **wrong tree** and exits
|
|
79
|
-
> 0 for whatever it matched. Check `quire --version` ≥ 0.16.0 before relying on any of
|
|
80
|
-
> this; ≤ 0.15.0 has the pre-split traversal semantics.
|
|
81
|
-
|
|
82
|
-
|
|
83
|
-
## Open in the review cockpit
|
|
84
|
-
|
|
85
|
-
After the bundle validates, run `filament open <plan-bundle>/plan.md` to open the
|
|
86
|
-
plan in the running filament-ide cockpit (it fires the `filament-ide://` deep link
|
|
87
|
-
and prints a clickable link as a fallback). Skip silently if the `filament`
|
|
88
|
-
command is not installed.
|
|
@@ -1,121 +0,0 @@
|
|
|
1
|
-
# Step 0: Plan Selection
|
|
2
|
-
|
|
3
|
-
**Goal**: Decide which plan this run targets — continue an existing one or start a
|
|
4
|
-
new one — and scaffold the plan bundle so Steps 1–3 have a place to write.
|
|
5
|
-
|
|
6
|
-
A project holds **multiple plans** under `plan/`, each a bundle
|
|
7
|
-
`plan/<Plan-id>-<slug>/`. This step picks exactly one target bundle.
|
|
8
|
-
|
|
9
|
-
## Process
|
|
10
|
-
|
|
11
|
-
### 1. Resolve the target plan
|
|
12
|
-
|
|
13
|
-
1. **Already in context?** If the user named a plan (an arg like `Plan-002`, or a
|
|
14
|
-
plan established earlier this session), use it and skip the prompt.
|
|
15
|
-
2. **Discover existing plans.** Glob `plan/*/plan.md`. For each, read the frontmatter
|
|
16
|
-
`id`, `title`, and `status`. Present them:
|
|
17
|
-
|
|
18
|
-
```
|
|
19
|
-
Existing plans:
|
|
20
|
-
- Plan-001 electron-hello core app (active)
|
|
21
|
-
- Plan-002 packaging & distribution (active)
|
|
22
|
-
|
|
23
|
-
Continue one of these, or start a new plan?
|
|
24
|
-
```
|
|
25
|
-
3. **Continue** (update an existing plan, e.g. after a spec change) → use the chosen
|
|
26
|
-
bundle and **update it in place** (see below). **New** → go to step 2 below.
|
|
27
|
-
|
|
28
|
-
#### Updating an existing plan
|
|
29
|
-
|
|
30
|
-
A common flow is: the spec changed (a requirement was added, edited, or removed),
|
|
31
|
-
now regenerate the plan. Continue the existing bundle — **never spawn a second plan
|
|
32
|
-
for the same effort**:
|
|
33
|
-
|
|
34
|
-
- **Diff coverage.** Re-read the current requirements and compare them to the plan's
|
|
35
|
-
`relationships: references` and existing `tasks/`. Identify requirements that are
|
|
36
|
-
new, changed, or removed.
|
|
37
|
-
- **Add only what's missing.** Create `Task` files for newly covered requirements,
|
|
38
|
-
continuing the existing `Task-NNN` numbering. Do **not** duplicate tasks that
|
|
39
|
-
already exist for unchanged requirements.
|
|
40
|
-
- **Reconcile changed/removed.** For a changed requirement, update its task's scope
|
|
41
|
-
and `verifies`/`references` edges. For a removed requirement, drop or mark its task
|
|
42
|
-
(don't silently leave an orphan).
|
|
43
|
-
- **Preserve progress.** Leave `status` on tasks already `in_progress`/`done` intact.
|
|
44
|
-
- **Update the plan doc + edges.** Extend `plan.md`'s `relationships: references` and
|
|
45
|
-
body (dependency graph, tracks) to include the new work.
|
|
46
|
-
- **Refresh index + log.** Update `index.md`'s `## Contents` for any added/removed
|
|
47
|
-
task files, and append a dated `log.md` `## History` entry describing the change
|
|
48
|
-
(e.g. "Regenerated after FR-008 added: +Task-013").
|
|
49
|
-
|
|
50
|
-
### 2. Create a new plan bundle
|
|
51
|
-
|
|
52
|
-
1. **Allocate the id.** Next `Plan-NNN` after the highest existing id (zero-padded
|
|
53
|
-
to 3 digits, e.g. `Plan-003`). If none exist, `Plan-001`.
|
|
54
|
-
2. **Derive `slug` and `title`.** Slug is kebab-case, no id prefix (e.g.
|
|
55
|
-
`electron-hello-core`). Title is human-readable.
|
|
56
|
-
3. **Scope the requirements.** Collect the requirement ids (StR/FR/NFR) this plan
|
|
57
|
-
covers — these become the plan's `relationships: references` edges.
|
|
58
|
-
4. **Scaffold the bundle** at `plan/<Plan-id>-<slug>/`:
|
|
59
|
-
|
|
60
|
-
- `plan.md` — `type: Plan` frontmatter (Step 1 fills the body):
|
|
61
|
-
|
|
62
|
-
```yaml
|
|
63
|
-
---
|
|
64
|
-
id: Plan-003
|
|
65
|
-
title: "Packaging & distribution"
|
|
66
|
-
type: Plan
|
|
67
|
-
status: active
|
|
68
|
-
relationships:
|
|
69
|
-
- target: ix://<org>/<component>/FR-008
|
|
70
|
-
type: references
|
|
71
|
-
# …one per covered requirement
|
|
72
|
-
---
|
|
73
|
-
```
|
|
74
|
-
`<org>`/`<component>` come from the spec's `spec.md` frontmatter (`org`, `name`).
|
|
75
|
-
|
|
76
|
-
- `index.md` — `type: index`, body `## Contents` (link list; starts with `plan.md`,
|
|
77
|
-
grows as tasks are added in Step 3):
|
|
78
|
-
|
|
79
|
-
```markdown
|
|
80
|
-
---
|
|
81
|
-
type: index
|
|
82
|
-
title: "Plan-003 — Packaging & distribution"
|
|
83
|
-
description: "Contents of the Plan-003 bundle."
|
|
84
|
-
okf_version: "0.1"
|
|
85
|
-
---
|
|
86
|
-
# Plan-003 — Packaging & distribution
|
|
87
|
-
|
|
88
|
-
## Contents
|
|
89
|
-
|
|
90
|
-
* [Plan-003: Packaging & distribution](./plan.md) - Plan overview, DAG, tracks, gates.
|
|
91
|
-
```
|
|
92
|
-
|
|
93
|
-
- `log.md` — `type: log`, body `## History` (dated entries; seed with creation):
|
|
94
|
-
|
|
95
|
-
```markdown
|
|
96
|
-
---
|
|
97
|
-
type: log
|
|
98
|
-
title: "Plan-003 — Update Log"
|
|
99
|
-
description: "Chronological log of changes to the Plan-003 bundle."
|
|
100
|
-
---
|
|
101
|
-
# Plan-003 — Update Log
|
|
102
|
-
|
|
103
|
-
## History
|
|
104
|
-
|
|
105
|
-
* **<YYYY-MM-DD>** — Plan created from spec; scoped to FR-008, FR-009, NFR-004.
|
|
106
|
-
```
|
|
107
|
-
|
|
108
|
-
- `tasks/` — empty directory (Step 3 populates it).
|
|
109
|
-
|
|
110
|
-
### 3. Hand off
|
|
111
|
-
|
|
112
|
-
State the resolved bundle path (e.g. `plan/Plan-003-packaging-distribution/`)
|
|
113
|
-
explicitly so Steps 1–3 — and any downstream skill — write to the right place.
|
|
114
|
-
|
|
115
|
-
## Notes
|
|
116
|
-
|
|
117
|
-
- **Never write to a second plan's files** during this run. One run targets one bundle.
|
|
118
|
-
- Use **today's date** (real calendar date) in `log.md`; do not invent or reuse a
|
|
119
|
-
date from the skeleton.
|
|
120
|
-
- `index.md`/`log.md` follow the reserved OKF archetypes from `spec-artifacts-iso`
|
|
121
|
-
(`skeletons/index.md`, `skeletons/log.md`).
|
|
@@ -1,88 +0,0 @@
|
|
|
1
|
-
# Step 1: Requirements Analysis
|
|
2
|
-
|
|
3
|
-
**Goal**: Analyze the ISO specification to understand what needs to be built, map dependencies, and identify the requirement dependency graph that drives execution planning.
|
|
4
|
-
|
|
5
|
-
## Process
|
|
6
|
-
|
|
7
|
-
1. **Locate References**:
|
|
8
|
-
- Find the component specification (usually `spec.md` or `specs/`).
|
|
9
|
-
- Identify `stakeholder/*.md`, `functional/*.md`, and `non-functional/*.md`.
|
|
10
|
-
|
|
11
|
-
2. **Order of Analysis**:
|
|
12
|
-
- **Stakeholder Requirements (StR)**: Understand the "Why" and "Who". Identify normative constraints.
|
|
13
|
-
- **Functional Requirements (FR)**: Understand the "What". These map directly to logic and Unit/Integration tests.
|
|
14
|
-
- **Non-Functional Requirements (NFR)**: Understand the "How" (Quality). These map to performance/security constraints and Verification tests.
|
|
15
|
-
|
|
16
|
-
3. **Dependency Extraction**:
|
|
17
|
-
- **Primary source**: YAML `traces:` and `relationships:` frontmatter arrays in each spec file.
|
|
18
|
-
- **Secondary source**: Normative references in requirement text (e.g., "SHALL use GenericXLog" implies a dependency on the WAL requirement).
|
|
19
|
-
- **Shared algorithms**: If two FRs describe the same underlying algorithm (e.g., graph traversal used by both scan and insert), note this as a shared dependency even if not explicitly linked in frontmatter.
|
|
20
|
-
- **Build a DAG**: Express dependencies as directed edges with reasons. This graph drives Step 3 execution planning.
|
|
21
|
-
|
|
22
|
-
4. **Traceability Mapping**:
|
|
23
|
-
- Create or update the target bundle's `plan/<Plan-id>-<slug>/plan.md` (the
|
|
24
|
-
bundle resolved in Step 0) with a requirements checklist.
|
|
25
|
-
- Include the full dependency graph with edge labels.
|
|
26
|
-
- Ensure the plan's frontmatter `relationships:` carries one `references` edge
|
|
27
|
-
per requirement the plan covers (see the frontmatter block below); this is
|
|
28
|
-
the machine-readable trace.
|
|
29
|
-
|
|
30
|
-
## Output Format (plan/<Plan-id>-<slug>/plan.md)
|
|
31
|
-
|
|
32
|
-
The file is a `type: Plan` artifact. Frontmatter is the machine contract; the body
|
|
33
|
-
below is the human-facing plan. `<org>`/`<component>` come from `spec.md`
|
|
34
|
-
frontmatter (`org`, `name`).
|
|
35
|
-
|
|
36
|
-
```markdown
|
|
37
|
-
---
|
|
38
|
-
id: Plan-001
|
|
39
|
-
title: "[Component] — [plan title]"
|
|
40
|
-
type: Plan
|
|
41
|
-
status: active
|
|
42
|
-
relationships:
|
|
43
|
-
- target: ix://<org>/<component>/FR-001
|
|
44
|
-
type: references
|
|
45
|
-
- target: ix://<org>/<component>/NFR-001
|
|
46
|
-
type: references
|
|
47
|
-
# …one `references` edge per covered requirement
|
|
48
|
-
---
|
|
49
|
-
# Implementation Plan: [Plan title]
|
|
50
|
-
|
|
51
|
-
## Requirements Summary
|
|
52
|
-
|
|
53
|
-
### Stakeholder Requirements
|
|
54
|
-
- [ ] **StR-001**: [Summary]
|
|
55
|
-
|
|
56
|
-
### Functional Requirements
|
|
57
|
-
- [ ] **FR-001**: [Summary]
|
|
58
|
-
- [ ] **FR-002**: [Summary]
|
|
59
|
-
|
|
60
|
-
### Non-Functional Requirements
|
|
61
|
-
- [ ] **NFR-001**: [Summary]
|
|
62
|
-
|
|
63
|
-
## Dependency Graph
|
|
64
|
-
|
|
65
|
-
### Core dependency edges
|
|
66
|
-
- `FR-001 -> FR-002, FR-003`
|
|
67
|
-
Reason: [why FR-002 and FR-003 depend on FR-001]
|
|
68
|
-
- `FR-004 + FR-005 -> FR-006`
|
|
69
|
-
Reason: [why FR-006 needs both]
|
|
70
|
-
|
|
71
|
-
### Shared dependencies
|
|
72
|
-
- [Algorithm/component X] is needed by FR-007, FR-008, and FR-009.
|
|
73
|
-
Extract as a discrete deliverable before any of them start.
|
|
74
|
-
|
|
75
|
-
### Cross-cutting constraints
|
|
76
|
-
- `NFR-001` applies to [which code paths].
|
|
77
|
-
- `NFR-002` applies to [which merge points].
|
|
78
|
-
|
|
79
|
-
### The seams (optional)
|
|
80
|
-
One short paragraph grounding the plan in the existing code — the concrete files,
|
|
81
|
-
functions, or boundaries each track attaches to (e.g. "FR-021 widens the write guard in
|
|
82
|
-
`authorize.ts`; FR-022 reuses the existing `chokidar-change-source.ts`"). Keep it to a
|
|
83
|
-
few sentences; omit if the spec is greenfield.
|
|
84
|
-
```
|
|
85
|
-
|
|
86
|
-
This is the **single** dependency-graph representation for the bundle. Step 3 references
|
|
87
|
-
it — it does not re-emit a "Remaining Dependency Graph" or a separate "Execution Tracks"
|
|
88
|
-
section.
|
|
@@ -1,43 +0,0 @@
|
|
|
1
|
-
# Step 2: Test Plan Creation
|
|
2
|
-
|
|
3
|
-
**Goal**: Define a comprehensive list of tests *before* writing any code (TDD).
|
|
4
|
-
|
|
5
|
-
## Process
|
|
6
|
-
|
|
7
|
-
1. **Derive Tests from FRs**:
|
|
8
|
-
- For each Functional Requirement (FR), identify the necessary **Unit Tests** (pure logic) and **Integration Tests** (component interaction).
|
|
9
|
-
- Define the *Entrance Criteria* (Setup) and *Exit Criteria* (Assertions).
|
|
10
|
-
|
|
11
|
-
2. **Enumerate Acceptance Criteria**:
|
|
12
|
-
- For each FR and NFR, explicitly list all Acceptance Criteria (AC IDs) from the spec.
|
|
13
|
-
- If no formal ACs exist in the spec, derive them and document in the plan for traceability.
|
|
14
|
-
- This ensures implementation progress is trackable per-criterion, not just per-requirement.
|
|
15
|
-
|
|
16
|
-
3. **Derive Verification from NFRs**:
|
|
17
|
-
- For each Non-Functional Requirement (NFR), define the **Verification Method** (e.g., Load Test script, Static Analysis check, Manual Inspection).
|
|
18
|
-
|
|
19
|
-
4. **Structure the Plan**:
|
|
20
|
-
- Append a "Test Plan" section to the bundle's `plan/<Plan-id>-<slug>/plan.md`.
|
|
21
|
-
- Group tests by the component/module they target.
|
|
22
|
-
- Note the TC ids here — Step 3 wires them onto each task as
|
|
23
|
-
`relationships: verifies` edges, so keep them stable.
|
|
24
|
-
|
|
25
|
-
## Output Format (appended to plan/<Plan-id>-<slug>/plan.md)
|
|
26
|
-
|
|
27
|
-
```markdown
|
|
28
|
-
## Test Plan
|
|
29
|
-
|
|
30
|
-
### Unit Tests
|
|
31
|
-
- [ ] **test_valid_input_processing** (FR-001): Verify X returns Y given Z.
|
|
32
|
-
- [ ] **test_error_handling_invalid_id** (FR-001): Verify System raises ValueError on invalid ID.
|
|
33
|
-
|
|
34
|
-
### Integration Tests
|
|
35
|
-
- [ ] **test_database_persistence** (FR-002): Verify data is strictly committed to DB.
|
|
36
|
-
|
|
37
|
-
### Verification (NFRs)
|
|
38
|
-
- [ ] **verify_response_time** (NFR-001): Run load test to ensure p95 < 200ms.
|
|
39
|
-
```
|
|
40
|
-
|
|
41
|
-
This is the **single** TC enumeration for the bundle. Downstream sections reference TC
|
|
42
|
-
ids only via the Step 3 **Task File Mapping** table — do not re-list them per track or in
|
|
43
|
-
track exit-criteria.
|