diff --git a/CHANGELOG.md b/CHANGELOG.md index aba77ff..dd525c2 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -2,6 +2,8 @@ ## Unreleased +- Accept the user-requested, reviewed Skills update at `472c216f2f043f0add1f83540cc46ea53d20a7cd` as `0.1.0-dev.5`, including collaboration principles and bundled quality-validation guidance. Preserve automatic sensitive-change holds; this update uses a separate protected PR. + - Record independently verified live source-push dispatch, automatic protected update/merge, post-merge no-op, and sensitive-change hold receipts; retain explicit host-runtime and scheduled-timer coverage limits. - Update packaged skills from `ffb5025dfa9f25fab868a4f12f9fb661ac7bfb87` to `14b8ad3dbba8ea820478d3ea2d379c2863de56d9` (0.1.0-dev.4). diff --git a/VERSION b/VERSION index a783c47..93d301f 100644 --- a/VERSION +++ b/VERSION @@ -1 +1 @@ -0.1.0-dev.4 +0.1.0-dev.5 diff --git a/plugins/claude/.claude-plugin/plugin.json b/plugins/claude/.claude-plugin/plugin.json index 10a57f8..ccf67b4 100644 --- a/plugins/claude/.claude-plugin/plugin.json +++ b/plugins/claude/.claude-plugin/plugin.json @@ -5,5 +5,5 @@ "description": "Vstack portable workflows and engineering principles.", "license": "MIT", "name": "vstack", - "version": "0.1.0-dev.4" + "version": "0.1.0-dev.5" } diff --git a/plugins/claude/SOURCE.json b/plugins/claude/SOURCE.json index 6057c12..f216ea8 100644 --- a/plugins/claude/SOURCE.json +++ b/plugins/claude/SOURCE.json @@ -1,13 +1,13 @@ { "files": { - ".claude-plugin/plugin.json": "ae919c00243ca616f002953a6310cdf7da451788152ea722f1f7ccae1b1912c0", + ".claude-plugin/plugin.json": "6451f853284b73851d66d22b81907f8c99153221c0420b93ab549d83df4864bc", "LICENSE": "24ba061a4603738ddd5105ef4abc198eeded5ac7efce23b360561816f4dd6559", "skills/build-landing-page/README.md": "46a280eadac8962180cf3f0c42eb0e845a3b0156a644569182d932881e1d51f8", "skills/build-landing-page/SKILL.md": "b08e4963d6149f3647b28a0d9dccdc8793812abab95a1d081d93699e142de0f0", "skills/build-landing-page/references/copywriting-formulas.md": "6d19f6166e1badcfdda0af4f8b303160e94ee6e6149321157e12849654cc013e", "skills/build-landing-page/references/review-rubric.md": "6c06f95eea847f63e2327b34c89fb167fec0f52360cd50bcfa257f9f96f33b0e", "skills/build-landing-page/references/structure-blueprints.md": "1f0a52ecb8d4d78f3f9eea6d89db8f471188986e1a9ad39b19587e52001e99e3", - "skills/build-landing-page/references/vstack/protocols/quality-validation.md": "522c097cb146a9fd016fd91facadb3faa13b0d6f7f14707d7bdf23aca3143b19", + "skills/build-landing-page/references/vstack/protocols/quality-validation.md": "e53fca023d31b907d60019c68a5d823e0d89ae83d09e49e68c71bc9ec5a1303a", "skills/build-project/SKILL.md": "719bff37da357fb73062ff302a86650e4d1611f5b7d8712155a94a6802a985d0", "skills/build-project/references/vstack/capabilities/convex-components/REFERENCE.md": "ebd776c115b578aff19f6bfceee61cb694afe63546a882de50cb020f6ba996e5", "skills/build-project/references/vstack/capabilities/eslint-configuration/REFERENCE.md": "5a2e090a253b89b6dee9c474a7044cd10be81427792c51b7a3322c0f163ae44b", @@ -16,9 +16,9 @@ "skills/build-project/references/vstack/capabilities/stack-packages/references/github-npm.md": "c1731affd8f0be4c62b988e45659b754948513e9b6ef8c61b96cab10bc0ffef2", "skills/build-project/references/vstack/capabilities/typescript-configuration/REFERENCE.md": "baccc320777d2050be44ccd2219e38f0dbf199127da11598642d53e71c594bba", "skills/build-project/references/vstack/capabilities/workspace-turborepo/REFERENCE.md": "af854042419d04d4f6af4454bcee41f3275fb70c466fd6efefa1bff273e295ab", - "skills/build-project/references/vstack/protocols/quality-validation.md": "522c097cb146a9fd016fd91facadb3faa13b0d6f7f14707d7bdf23aca3143b19", + "skills/build-project/references/vstack/protocols/quality-validation.md": "e53fca023d31b907d60019c68a5d823e0d89ae83d09e49e68c71bc9ec5a1303a", "skills/build-prototype/SKILL.md": "7a27f04b673c733ab6aa0e4f3eed68f8fa1ce82884e22eda6ec24cbba5ab162e", - "skills/build-prototype/references/vstack/protocols/quality-validation.md": "522c097cb146a9fd016fd91facadb3faa13b0d6f7f14707d7bdf23aca3143b19", + "skills/build-prototype/references/vstack/protocols/quality-validation.md": "e53fca023d31b907d60019c68a5d823e0d89ae83d09e49e68c71bc9ec5a1303a", "skills/deliver-issue/SKILL.md": "a81532ec0e731f80092f4be969d73f923b84fdc240b58781b86e3b8095b288bc", "skills/deliver-issue/references/vstack/capabilities/code-architecture/DEEPENING.md": "9850a1364402229df25d0fd686b6905bbcbdaa52fccaf7d5344307fd900fed2e", "skills/deliver-issue/references/vstack/capabilities/code-architecture/INTERFACE-DESIGN.md": "60d6651b5cd0de5479f60b7840b6e156cb41f2f80ae4a91c661f67874c5dbee8", @@ -28,7 +28,7 @@ "skills/deliver-issue/references/vstack/capabilities/convex-components/REFERENCE.md": "ebd776c115b578aff19f6bfceee61cb694afe63546a882de50cb020f6ba996e5", "skills/deliver-issue/references/vstack/capabilities/nextjs-tests/REFERENCE.md": "3447bd768cbf50efd1a12a60c72060f5a2ec1335fa56d45da091e376858780a9", "skills/deliver-issue/references/vstack/capabilities/ui-accessibility/REFERENCE.md": "f265d321d975a0319ab5455b7fefd74e4852de63b7bd14d1f9d044c78371c25b", - "skills/deliver-issue/references/vstack/protocols/quality-validation.md": "522c097cb146a9fd016fd91facadb3faa13b0d6f7f14707d7bdf23aca3143b19", + "skills/deliver-issue/references/vstack/protocols/quality-validation.md": "e53fca023d31b907d60019c68a5d823e0d89ae83d09e49e68c71bc9ec5a1303a", "skills/deliver-pull-request/SKILL.md": "afdf9ef8ae23fd899e5cbd246440efd6c2e10be2016599d85034bf89304df96c", "skills/deliver-pull-request/references/vstack/capabilities/ci-optimization/REFERENCE.md": "b376d64c2297e6ba535b581474bddb6c777c8a847d3424cdcc77fef7cd0d99a9", "skills/deliver-pull-request/references/vstack/capabilities/ci-optimization/references/scenarios.md": "731de32df4a92fcb78047b7f9c8b71ab9697ea1daebdc101295fdbc26a5c9320", @@ -47,12 +47,12 @@ "skills/deliver-pull-request/references/vstack/capabilities/release-readiness/references/release-messaging.md": "4f5cc13e7fd30cd84ccf84dbd02f0d5696ccb52a3b27c8f448a29c983e28a4c1", "skills/deliver-pull-request/references/vstack/capabilities/release-readiness/references/version-sync.md": "3e9ecae39a8e5f5a33914a4097ea5728c24ce9292618bd295761297fb1d7cb78", "skills/deliver-pull-request/references/vstack/capabilities/runtime-performance/REFERENCE.md": "6692e8fdd6a736d06b8adec108e07b6b19f8bcf0d62051cacc0d24f73a3ebcd9", - "skills/deliver-pull-request/references/vstack/protocols/quality-validation.md": "522c097cb146a9fd016fd91facadb3faa13b0d6f7f14707d7bdf23aca3143b19", + "skills/deliver-pull-request/references/vstack/protocols/quality-validation.md": "e53fca023d31b907d60019c68a5d823e0d89ae83d09e49e68c71bc9ec5a1303a", "skills/explain-subject/SKILL.md": "909b948a392bf37264d5747626fd8e75541d0b6a528c70bd2176a5ff0e9e8b85", "skills/explain-subject/references/vstack/capabilities/reasoning-assumptions/REFERENCE.md": "edf4b1bf183541c7198f8ec6a00e25db790c8510fe4fcf6c1060d9b2b4f9e50d", - "skills/explain-subject/references/vstack/protocols/quality-validation.md": "522c097cb146a9fd016fd91facadb3faa13b0d6f7f14707d7bdf23aca3143b19", + "skills/explain-subject/references/vstack/protocols/quality-validation.md": "e53fca023d31b907d60019c68a5d823e0d89ae83d09e49e68c71bc9ec5a1303a", "skills/explore-decisions/SKILL.md": "07a1f5daa4543de924cd3b5bc8dfd2b482aeb0e94da8338d328402fb5505d11b", - "skills/explore-decisions/references/vstack/protocols/quality-validation.md": "522c097cb146a9fd016fd91facadb3faa13b0d6f7f14707d7bdf23aca3143b19", + "skills/explore-decisions/references/vstack/protocols/quality-validation.md": "e53fca023d31b907d60019c68a5d823e0d89ae83d09e49e68c71bc9ec5a1303a", "skills/improve-code/SKILL.md": "98cf3810fcb70580dbbb915d6bd7aee5f664b4c3e3b64dc4743253574a452d46", "skills/improve-code/references/vstack/capabilities/code-architecture/DEEPENING.md": "9850a1364402229df25d0fd686b6905bbcbdaa52fccaf7d5344307fd900fed2e", "skills/improve-code/references/vstack/capabilities/code-architecture/INTERFACE-DESIGN.md": "60d6651b5cd0de5479f60b7840b6e156cb41f2f80ae4a91c661f67874c5dbee8", @@ -64,7 +64,7 @@ "skills/improve-code/references/vstack/capabilities/code-test-management/references/test-doubles.md": "c3006a6f6fef0039b8c8e879bfcf728bd553c85ce80f512521a08161c3c40a28", "skills/improve-code/references/vstack/capabilities/runtime-performance/REFERENCE.md": "6692e8fdd6a736d06b8adec108e07b6b19f8bcf0d62051cacc0d24f73a3ebcd9", "skills/improve-code/references/vstack/capabilities/workspace-turborepo/REFERENCE.md": "af854042419d04d4f6af4454bcee41f3275fb70c466fd6efefa1bff273e295ab", - "skills/improve-code/references/vstack/protocols/quality-validation.md": "522c097cb146a9fd016fd91facadb3faa13b0d6f7f14707d7bdf23aca3143b19", + "skills/improve-code/references/vstack/protocols/quality-validation.md": "e53fca023d31b907d60019c68a5d823e0d89ae83d09e49e68c71bc9ec5a1303a", "skills/improve-project/SKILL.md": "7d7a175d64e3180341c59d0d9b7cc4d1a2d20df37452673937701ac171b73e86", "skills/improve-project/references/vstack/capabilities/ci-optimization/REFERENCE.md": "b376d64c2297e6ba535b581474bddb6c777c8a847d3424cdcc77fef7cd0d99a9", "skills/improve-project/references/vstack/capabilities/ci-optimization/references/scenarios.md": "731de32df4a92fcb78047b7f9c8b71ab9697ea1daebdc101295fdbc26a5c9320", @@ -76,13 +76,13 @@ "skills/improve-project/references/vstack/capabilities/stack-packages/references/github-npm.md": "c1731affd8f0be4c62b988e45659b754948513e9b6ef8c61b96cab10bc0ffef2", "skills/improve-project/references/vstack/capabilities/typescript-configuration/REFERENCE.md": "baccc320777d2050be44ccd2219e38f0dbf199127da11598642d53e71c594bba", "skills/improve-project/references/vstack/capabilities/workspace-turborepo/REFERENCE.md": "af854042419d04d4f6af4454bcee41f3275fb70c466fd6efefa1bff273e295ab", - "skills/improve-project/references/vstack/protocols/quality-validation.md": "522c097cb146a9fd016fd91facadb3faa13b0d6f7f14707d7bdf23aca3143b19", + "skills/improve-project/references/vstack/protocols/quality-validation.md": "e53fca023d31b907d60019c68a5d823e0d89ae83d09e49e68c71bc9ec5a1303a", "skills/improve-ui/SKILL.md": "91989dc9cad28ee29e8f899132bf4e2de9dfe152aec653e03038287ab2b452d1", "skills/improve-ui/references/vstack/capabilities/ui-accessibility/REFERENCE.md": "f265d321d975a0319ab5455b7fefd74e4852de63b7bd14d1f9d044c78371c25b", "skills/improve-ui/references/vstack/capabilities/web-performance/REFERENCE.md": "52fb4ebb9e024fa6184da9187f3311d17a53c40691a63f5b2b6c471729f760ff", "skills/improve-ui/references/vstack/capabilities/web-performance/references/eval-audits.md": "d94253fb08c7059329022026843088c46c23a8615d134ace36eea4cb61fa9a6c", "skills/improve-ui/references/vstack/capabilities/web-performance/references/optimization-playbook.md": "0acdedcb0496f4926bee2d23a2294a152a8107c88c5e9f934afa8334e74fde13", - "skills/improve-ui/references/vstack/protocols/quality-validation.md": "522c097cb146a9fd016fd91facadb3faa13b0d6f7f14707d7bdf23aca3143b19", + "skills/improve-ui/references/vstack/protocols/quality-validation.md": "e53fca023d31b907d60019c68a5d823e0d89ae83d09e49e68c71bc9ec5a1303a", "skills/manage-defects/SKILL.md": "04d0501484ab5c507ace3ec204aae38b29b0cafd6f80747955c9118f8b0d97ba", "skills/manage-defects/references/vstack/capabilities/code-architecture/DEEPENING.md": "9850a1364402229df25d0fd686b6905bbcbdaa52fccaf7d5344307fd900fed2e", "skills/manage-defects/references/vstack/capabilities/code-architecture/INTERFACE-DESIGN.md": "60d6651b5cd0de5479f60b7840b6e156cb41f2f80ae4a91c661f67874c5dbee8", @@ -93,7 +93,7 @@ "skills/manage-defects/references/vstack/capabilities/nextjs-tests/REFERENCE.md": "3447bd768cbf50efd1a12a60c72060f5a2ec1335fa56d45da091e376858780a9", "skills/manage-defects/references/vstack/capabilities/runtime-performance/REFERENCE.md": "6692e8fdd6a736d06b8adec108e07b6b19f8bcf0d62051cacc0d24f73a3ebcd9", "skills/manage-defects/references/vstack/capabilities/ui-accessibility/REFERENCE.md": "f265d321d975a0319ab5455b7fefd74e4852de63b7bd14d1f9d044c78371c25b", - "skills/manage-defects/references/vstack/protocols/quality-validation.md": "522c097cb146a9fd016fd91facadb3faa13b0d6f7f14707d7bdf23aca3143b19", + "skills/manage-defects/references/vstack/protocols/quality-validation.md": "e53fca023d31b907d60019c68a5d823e0d89ae83d09e49e68c71bc9ec5a1303a", "skills/manage-issues/README.md": "867654dad179b039a3c058844f089939bfcf947096ba3ac1ce92a6015d9ac63a", "skills/manage-issues/SKILL.md": "36174c90206a6c3cf58a0b15ee32c07a4a4609aeb3563c939f34bb6b7b88d861", "skills/manage-issues/references/docs-alignment.md": "cd6c59a9488fa7f0353eb6b4726a243974f4019e7e0272d60015f46cdeeac210", @@ -101,19 +101,19 @@ "skills/manage-issues/references/parallelize.md": "16455c43dde811e86682cfd206192479bacfefd45e827da993a13fae3fcec1de", "skills/manage-issues/references/quality-gate.md": "43d3ca7e14041c4b49ca676d51be1ce5b7c9a13f6cfdf497aa1ab762d6988c37", "skills/manage-issues/references/stale.md": "f190ad3c0f3292418de9d86a5811d3c4de3c8feff6189267bbc126cd8a612004", - "skills/manage-issues/references/vstack/protocols/quality-validation.md": "522c097cb146a9fd016fd91facadb3faa13b0d6f7f14707d7bdf23aca3143b19", + "skills/manage-issues/references/vstack/protocols/quality-validation.md": "e53fca023d31b907d60019c68a5d823e0d89ae83d09e49e68c71bc9ec5a1303a", "skills/manage-issues/templates/issue-template.md": "ba25b30b6c1991b88f72146e9770f89a81959a1c92305bf2fe080880b9b245b0", "skills/manage-roadmap/SKILL.md": "759565e546f800a6126ce97a6afee94d7685219fd946ee86ddda5ab6027b1ae6", "skills/manage-roadmap/references/format.md": "67e052640c1bb6b6ff933de6ce7a9d386e460ec193226e29c7b561314d0f8d4e", "skills/manage-roadmap/references/parallel.md": "c38bd2a8c3228552852f15255a64113ad95ef1ec44214991cc71bb0508b48105", - "skills/manage-roadmap/references/vstack/protocols/quality-validation.md": "522c097cb146a9fd016fd91facadb3faa13b0d6f7f14707d7bdf23aca3143b19", + "skills/manage-roadmap/references/vstack/protocols/quality-validation.md": "e53fca023d31b907d60019c68a5d823e0d89ae83d09e49e68c71bc9ec5a1303a", "skills/manage-rules/SKILL.md": "8b68d3dc576ba3cc31efda6ce7e99ab3fbba2e9406bc91c1dc93a35faa390c6f", - "skills/manage-rules/references/vstack/protocols/quality-validation.md": "522c097cb146a9fd016fd91facadb3faa13b0d6f7f14707d7bdf23aca3143b19", + "skills/manage-rules/references/vstack/protocols/quality-validation.md": "e53fca023d31b907d60019c68a5d823e0d89ae83d09e49e68c71bc9ec5a1303a", "skills/manage-skills/SKILL.md": "05bf1e174bd54cd4561d7dfd3c2278c48278a044fd755c27e12612064e255c3a", - "skills/manage-skills/references/vstack/protocols/quality-validation.md": "522c097cb146a9fd016fd91facadb3faa13b0d6f7f14707d7bdf23aca3143b19", + "skills/manage-skills/references/vstack/protocols/quality-validation.md": "e53fca023d31b907d60019c68a5d823e0d89ae83d09e49e68c71bc9ec5a1303a", "skills/manage-vision/SKILL.md": "d1c3fa2e276dd7939b91b25fc840986a07aa9184ddf51645aa2f71549f7cc647", "skills/manage-vision/references/format.md": "d9a2ca5b92f8194f7cab5ad4fdd8722d72888e0eeb4875503fec9d3d5d1ff3c4", - "skills/manage-vision/references/vstack/protocols/quality-validation.md": "522c097cb146a9fd016fd91facadb3faa13b0d6f7f14707d7bdf23aca3143b19", + "skills/manage-vision/references/vstack/protocols/quality-validation.md": "e53fca023d31b907d60019c68a5d823e0d89ae83d09e49e68c71bc9ec5a1303a", "skills/plan-issues/SKILL.md": "dedf1efea18b847278e5c6530ec14d5396d150780d6c81f059e7c3fd81853f35", "skills/plan-issues/references/vstack/capabilities/agent-tooling-review/REFERENCE.md": "7b727fbe19c53878de4ba729e1bacea2d0a953444050232d35db2ad7b673fcc3", "skills/plan-issues/references/vstack/capabilities/compliance-review/REFERENCE.md": "3532a9686e5d52da0a82850d15b284b6acd82b0da8506c3679e17c8924f68694", @@ -123,21 +123,21 @@ "skills/plan-issues/references/vstack/capabilities/compliance-review/references/privacy.md": "8a1aa4a96b0cf786c0099e76f4b46d255ee5135dcf1caf53b123fec7e4e11a8d", "skills/plan-issues/references/vstack/capabilities/infrastructure-costs/REFERENCE.md": "407b208fd7f2d9c1a611197154d9594a23d0506d637e298aa543a24bcb9fafd0", "skills/plan-issues/references/vstack/capabilities/infrastructure-review/REFERENCE.md": "17bd7a5b3d341d5b6ad08f917efbca69f3901b1fba545b75d2b4909cf831e4f8", - "skills/plan-issues/references/vstack/protocols/quality-validation.md": "522c097cb146a9fd016fd91facadb3faa13b0d6f7f14707d7bdf23aca3143b19", + "skills/plan-issues/references/vstack/protocols/quality-validation.md": "e53fca023d31b907d60019c68a5d823e0d89ae83d09e49e68c71bc9ec5a1303a", "skills/plan-work/SKILL.md": "4cc59fa808209d47d636ad1c65890d46e7b45729d7a211a8bc83ff5df3314886", - "skills/plan-work/references/vstack/protocols/quality-validation.md": "522c097cb146a9fd016fd91facadb3faa13b0d6f7f14707d7bdf23aca3143b19", + "skills/plan-work/references/vstack/protocols/quality-validation.md": "e53fca023d31b907d60019c68a5d823e0d89ae83d09e49e68c71bc9ec5a1303a", "skills/review-ui/SKILL.md": "b9e18bd0a294238486119a1d302a0d5ab06f4f77d5f5d37b77980ec68e6a580c", "skills/review-ui/references/vstack/capabilities/ui-accessibility/REFERENCE.md": "f265d321d975a0319ab5455b7fefd74e4852de63b7bd14d1f9d044c78371c25b", "skills/review-ui/references/vstack/capabilities/web-performance/REFERENCE.md": "52fb4ebb9e024fa6184da9187f3311d17a53c40691a63f5b2b6c471729f760ff", "skills/review-ui/references/vstack/capabilities/web-performance/references/eval-audits.md": "d94253fb08c7059329022026843088c46c23a8615d134ace36eea4cb61fa9a6c", "skills/review-ui/references/vstack/capabilities/web-performance/references/optimization-playbook.md": "0acdedcb0496f4926bee2d23a2294a152a8107c88c5e9f934afa8334e74fde13", - "skills/review-ui/references/vstack/protocols/quality-validation.md": "522c097cb146a9fd016fd91facadb3faa13b0d6f7f14707d7bdf23aca3143b19", - "skills/vllnt-collaboration-principles/SKILL.md": "a2540f13682fbe29defdaafc8c14221ea05f4cba60b0e6c2c2fd595fb55489f1", + "skills/review-ui/references/vstack/protocols/quality-validation.md": "e53fca023d31b907d60019c68a5d823e0d89ae83d09e49e68c71bc9ec5a1303a", + "skills/vllnt-collaboration-principles/SKILL.md": "d706dd9d89a602c9f70803e6b37714b1b68b8f3105f6f6b8cc3ad91cf7b3a478", "skills/vllnt-orchestration-principles/SKILL.md": "16d0df9b250499fa1f5f45e616bb5d126d0ae5fe5901548a476f07e5e94cb3a1", "skills/vllnt-thinking-principles/SKILL.md": "3d1229f311f9d58ec3335a35e9019afda8cf59dff5c20730a42593c17b40b0b9" }, "upstream": { - "commit": "14b8ad3dbba8ea820478d3ea2d379c2863de56d9", + "commit": "472c216f2f043f0add1f83540cc46ea53d20a7cd", "repository": "https://github.com/vllnt/skills.git" } } diff --git a/plugins/claude/skills/build-landing-page/references/vstack/protocols/quality-validation.md b/plugins/claude/skills/build-landing-page/references/vstack/protocols/quality-validation.md index e038fe9..9a0d797 100644 --- a/plugins/claude/skills/build-landing-page/references/vstack/protocols/quality-validation.md +++ b/plugins/claude/skills/build-landing-page/references/vstack/protocols/quality-validation.md @@ -15,9 +15,9 @@ 1. Reuse the caller's validation contract. Record candidate, mode, required criteria, evidence or checks, unacceptable outcomes, and useful review perspectives from the request, applicable instructions, principles, and owning workflow. 2. Have the producer self-assess each criterion as pass, fail, or unverified with evidence. Return known defects to the caller before independent review. A score may summarize a defined rubric but cannot replace required proof. -3. For substantive work, use distinct subagents for review of correctness, completeness, and preserved behavior, and critique of assumptions, necessity, simplicity, and alternatives. Give each the same contract, candidate, evidence, and bounded scope. Use direct checks for mechanical work; without subagents, assess sequentially and report unavailable independence. If independent review is required but unavailable, return `BLOCKED`. +3. For substantive work, obtain review of correctness, completeness, and preserved behavior, and critique of assumptions, necessity, simplicity, and alternatives from reviewers independent of the producer. One reviewer may cover both; add reviewers only for required separation or non-overlapping parallel scopes. Supply scoped criteria, the candidate or diff, and current evidence. Assign checks within each reviewer's tools and authority; return missing required evidence to the caller. Use direct checks for mechanical work. Without subagents, assess sequentially and report missing independence; return `BLOCKED` if required independent review is unavailable. 4. Collect verdicts and findings with criterion, location or scenario, evidence, impact, smallest remedy, and acceptance check. Deduplicate them into required fixes, selected improvements, optional suggestions, and justified rejections. Resolve disagreements with evidence; a disputed required criterion remains open. -5. Return actionable fixes to the caller. After every authorized revision, rerun invalidated checks and request fresh verdicts from affected reviewers and critics. Reuse only evidence and acceptance unaffected by the current candidate. +5. Return fixes to the caller. After authorized revisions, send affected reviewers the reason, revised material, and invalidated evidence. Rerun invalidated checks and renew affected verdicts; retain only evidence and acceptance unaffected by changes to the candidate, inputs, or relevant environment. 6. Return `PASS` only when every required criterion has proof, required perspectives accept their scopes, and no required finding remains. Otherwise return `REVISE` with fixes for the caller to implement and resubmit, or `BLOCKED` with the unmet criterion, cause, options, recommendation, and consequence. On unchanged evidence, change approach rather than retrying or lowering criteria. ## Pitfalls diff --git a/plugins/claude/skills/build-project/references/vstack/protocols/quality-validation.md b/plugins/claude/skills/build-project/references/vstack/protocols/quality-validation.md index e038fe9..9a0d797 100644 --- a/plugins/claude/skills/build-project/references/vstack/protocols/quality-validation.md +++ b/plugins/claude/skills/build-project/references/vstack/protocols/quality-validation.md @@ -15,9 +15,9 @@ 1. Reuse the caller's validation contract. Record candidate, mode, required criteria, evidence or checks, unacceptable outcomes, and useful review perspectives from the request, applicable instructions, principles, and owning workflow. 2. Have the producer self-assess each criterion as pass, fail, or unverified with evidence. Return known defects to the caller before independent review. A score may summarize a defined rubric but cannot replace required proof. -3. For substantive work, use distinct subagents for review of correctness, completeness, and preserved behavior, and critique of assumptions, necessity, simplicity, and alternatives. Give each the same contract, candidate, evidence, and bounded scope. Use direct checks for mechanical work; without subagents, assess sequentially and report unavailable independence. If independent review is required but unavailable, return `BLOCKED`. +3. For substantive work, obtain review of correctness, completeness, and preserved behavior, and critique of assumptions, necessity, simplicity, and alternatives from reviewers independent of the producer. One reviewer may cover both; add reviewers only for required separation or non-overlapping parallel scopes. Supply scoped criteria, the candidate or diff, and current evidence. Assign checks within each reviewer's tools and authority; return missing required evidence to the caller. Use direct checks for mechanical work. Without subagents, assess sequentially and report missing independence; return `BLOCKED` if required independent review is unavailable. 4. Collect verdicts and findings with criterion, location or scenario, evidence, impact, smallest remedy, and acceptance check. Deduplicate them into required fixes, selected improvements, optional suggestions, and justified rejections. Resolve disagreements with evidence; a disputed required criterion remains open. -5. Return actionable fixes to the caller. After every authorized revision, rerun invalidated checks and request fresh verdicts from affected reviewers and critics. Reuse only evidence and acceptance unaffected by the current candidate. +5. Return fixes to the caller. After authorized revisions, send affected reviewers the reason, revised material, and invalidated evidence. Rerun invalidated checks and renew affected verdicts; retain only evidence and acceptance unaffected by changes to the candidate, inputs, or relevant environment. 6. Return `PASS` only when every required criterion has proof, required perspectives accept their scopes, and no required finding remains. Otherwise return `REVISE` with fixes for the caller to implement and resubmit, or `BLOCKED` with the unmet criterion, cause, options, recommendation, and consequence. On unchanged evidence, change approach rather than retrying or lowering criteria. ## Pitfalls diff --git a/plugins/claude/skills/build-prototype/references/vstack/protocols/quality-validation.md b/plugins/claude/skills/build-prototype/references/vstack/protocols/quality-validation.md index e038fe9..9a0d797 100644 --- a/plugins/claude/skills/build-prototype/references/vstack/protocols/quality-validation.md +++ b/plugins/claude/skills/build-prototype/references/vstack/protocols/quality-validation.md @@ -15,9 +15,9 @@ 1. Reuse the caller's validation contract. Record candidate, mode, required criteria, evidence or checks, unacceptable outcomes, and useful review perspectives from the request, applicable instructions, principles, and owning workflow. 2. Have the producer self-assess each criterion as pass, fail, or unverified with evidence. Return known defects to the caller before independent review. A score may summarize a defined rubric but cannot replace required proof. -3. For substantive work, use distinct subagents for review of correctness, completeness, and preserved behavior, and critique of assumptions, necessity, simplicity, and alternatives. Give each the same contract, candidate, evidence, and bounded scope. Use direct checks for mechanical work; without subagents, assess sequentially and report unavailable independence. If independent review is required but unavailable, return `BLOCKED`. +3. For substantive work, obtain review of correctness, completeness, and preserved behavior, and critique of assumptions, necessity, simplicity, and alternatives from reviewers independent of the producer. One reviewer may cover both; add reviewers only for required separation or non-overlapping parallel scopes. Supply scoped criteria, the candidate or diff, and current evidence. Assign checks within each reviewer's tools and authority; return missing required evidence to the caller. Use direct checks for mechanical work. Without subagents, assess sequentially and report missing independence; return `BLOCKED` if required independent review is unavailable. 4. Collect verdicts and findings with criterion, location or scenario, evidence, impact, smallest remedy, and acceptance check. Deduplicate them into required fixes, selected improvements, optional suggestions, and justified rejections. Resolve disagreements with evidence; a disputed required criterion remains open. -5. Return actionable fixes to the caller. After every authorized revision, rerun invalidated checks and request fresh verdicts from affected reviewers and critics. Reuse only evidence and acceptance unaffected by the current candidate. +5. Return fixes to the caller. After authorized revisions, send affected reviewers the reason, revised material, and invalidated evidence. Rerun invalidated checks and renew affected verdicts; retain only evidence and acceptance unaffected by changes to the candidate, inputs, or relevant environment. 6. Return `PASS` only when every required criterion has proof, required perspectives accept their scopes, and no required finding remains. Otherwise return `REVISE` with fixes for the caller to implement and resubmit, or `BLOCKED` with the unmet criterion, cause, options, recommendation, and consequence. On unchanged evidence, change approach rather than retrying or lowering criteria. ## Pitfalls diff --git a/plugins/claude/skills/deliver-issue/references/vstack/protocols/quality-validation.md b/plugins/claude/skills/deliver-issue/references/vstack/protocols/quality-validation.md index e038fe9..9a0d797 100644 --- a/plugins/claude/skills/deliver-issue/references/vstack/protocols/quality-validation.md +++ b/plugins/claude/skills/deliver-issue/references/vstack/protocols/quality-validation.md @@ -15,9 +15,9 @@ 1. Reuse the caller's validation contract. Record candidate, mode, required criteria, evidence or checks, unacceptable outcomes, and useful review perspectives from the request, applicable instructions, principles, and owning workflow. 2. Have the producer self-assess each criterion as pass, fail, or unverified with evidence. Return known defects to the caller before independent review. A score may summarize a defined rubric but cannot replace required proof. -3. For substantive work, use distinct subagents for review of correctness, completeness, and preserved behavior, and critique of assumptions, necessity, simplicity, and alternatives. Give each the same contract, candidate, evidence, and bounded scope. Use direct checks for mechanical work; without subagents, assess sequentially and report unavailable independence. If independent review is required but unavailable, return `BLOCKED`. +3. For substantive work, obtain review of correctness, completeness, and preserved behavior, and critique of assumptions, necessity, simplicity, and alternatives from reviewers independent of the producer. One reviewer may cover both; add reviewers only for required separation or non-overlapping parallel scopes. Supply scoped criteria, the candidate or diff, and current evidence. Assign checks within each reviewer's tools and authority; return missing required evidence to the caller. Use direct checks for mechanical work. Without subagents, assess sequentially and report missing independence; return `BLOCKED` if required independent review is unavailable. 4. Collect verdicts and findings with criterion, location or scenario, evidence, impact, smallest remedy, and acceptance check. Deduplicate them into required fixes, selected improvements, optional suggestions, and justified rejections. Resolve disagreements with evidence; a disputed required criterion remains open. -5. Return actionable fixes to the caller. After every authorized revision, rerun invalidated checks and request fresh verdicts from affected reviewers and critics. Reuse only evidence and acceptance unaffected by the current candidate. +5. Return fixes to the caller. After authorized revisions, send affected reviewers the reason, revised material, and invalidated evidence. Rerun invalidated checks and renew affected verdicts; retain only evidence and acceptance unaffected by changes to the candidate, inputs, or relevant environment. 6. Return `PASS` only when every required criterion has proof, required perspectives accept their scopes, and no required finding remains. Otherwise return `REVISE` with fixes for the caller to implement and resubmit, or `BLOCKED` with the unmet criterion, cause, options, recommendation, and consequence. On unchanged evidence, change approach rather than retrying or lowering criteria. ## Pitfalls diff --git a/plugins/claude/skills/deliver-pull-request/references/vstack/protocols/quality-validation.md b/plugins/claude/skills/deliver-pull-request/references/vstack/protocols/quality-validation.md index e038fe9..9a0d797 100644 --- a/plugins/claude/skills/deliver-pull-request/references/vstack/protocols/quality-validation.md +++ b/plugins/claude/skills/deliver-pull-request/references/vstack/protocols/quality-validation.md @@ -15,9 +15,9 @@ 1. Reuse the caller's validation contract. Record candidate, mode, required criteria, evidence or checks, unacceptable outcomes, and useful review perspectives from the request, applicable instructions, principles, and owning workflow. 2. Have the producer self-assess each criterion as pass, fail, or unverified with evidence. Return known defects to the caller before independent review. A score may summarize a defined rubric but cannot replace required proof. -3. For substantive work, use distinct subagents for review of correctness, completeness, and preserved behavior, and critique of assumptions, necessity, simplicity, and alternatives. Give each the same contract, candidate, evidence, and bounded scope. Use direct checks for mechanical work; without subagents, assess sequentially and report unavailable independence. If independent review is required but unavailable, return `BLOCKED`. +3. For substantive work, obtain review of correctness, completeness, and preserved behavior, and critique of assumptions, necessity, simplicity, and alternatives from reviewers independent of the producer. One reviewer may cover both; add reviewers only for required separation or non-overlapping parallel scopes. Supply scoped criteria, the candidate or diff, and current evidence. Assign checks within each reviewer's tools and authority; return missing required evidence to the caller. Use direct checks for mechanical work. Without subagents, assess sequentially and report missing independence; return `BLOCKED` if required independent review is unavailable. 4. Collect verdicts and findings with criterion, location or scenario, evidence, impact, smallest remedy, and acceptance check. Deduplicate them into required fixes, selected improvements, optional suggestions, and justified rejections. Resolve disagreements with evidence; a disputed required criterion remains open. -5. Return actionable fixes to the caller. After every authorized revision, rerun invalidated checks and request fresh verdicts from affected reviewers and critics. Reuse only evidence and acceptance unaffected by the current candidate. +5. Return fixes to the caller. After authorized revisions, send affected reviewers the reason, revised material, and invalidated evidence. Rerun invalidated checks and renew affected verdicts; retain only evidence and acceptance unaffected by changes to the candidate, inputs, or relevant environment. 6. Return `PASS` only when every required criterion has proof, required perspectives accept their scopes, and no required finding remains. Otherwise return `REVISE` with fixes for the caller to implement and resubmit, or `BLOCKED` with the unmet criterion, cause, options, recommendation, and consequence. On unchanged evidence, change approach rather than retrying or lowering criteria. ## Pitfalls diff --git a/plugins/claude/skills/explain-subject/references/vstack/protocols/quality-validation.md b/plugins/claude/skills/explain-subject/references/vstack/protocols/quality-validation.md index e038fe9..9a0d797 100644 --- a/plugins/claude/skills/explain-subject/references/vstack/protocols/quality-validation.md +++ b/plugins/claude/skills/explain-subject/references/vstack/protocols/quality-validation.md @@ -15,9 +15,9 @@ 1. Reuse the caller's validation contract. Record candidate, mode, required criteria, evidence or checks, unacceptable outcomes, and useful review perspectives from the request, applicable instructions, principles, and owning workflow. 2. Have the producer self-assess each criterion as pass, fail, or unverified with evidence. Return known defects to the caller before independent review. A score may summarize a defined rubric but cannot replace required proof. -3. For substantive work, use distinct subagents for review of correctness, completeness, and preserved behavior, and critique of assumptions, necessity, simplicity, and alternatives. Give each the same contract, candidate, evidence, and bounded scope. Use direct checks for mechanical work; without subagents, assess sequentially and report unavailable independence. If independent review is required but unavailable, return `BLOCKED`. +3. For substantive work, obtain review of correctness, completeness, and preserved behavior, and critique of assumptions, necessity, simplicity, and alternatives from reviewers independent of the producer. One reviewer may cover both; add reviewers only for required separation or non-overlapping parallel scopes. Supply scoped criteria, the candidate or diff, and current evidence. Assign checks within each reviewer's tools and authority; return missing required evidence to the caller. Use direct checks for mechanical work. Without subagents, assess sequentially and report missing independence; return `BLOCKED` if required independent review is unavailable. 4. Collect verdicts and findings with criterion, location or scenario, evidence, impact, smallest remedy, and acceptance check. Deduplicate them into required fixes, selected improvements, optional suggestions, and justified rejections. Resolve disagreements with evidence; a disputed required criterion remains open. -5. Return actionable fixes to the caller. After every authorized revision, rerun invalidated checks and request fresh verdicts from affected reviewers and critics. Reuse only evidence and acceptance unaffected by the current candidate. +5. Return fixes to the caller. After authorized revisions, send affected reviewers the reason, revised material, and invalidated evidence. Rerun invalidated checks and renew affected verdicts; retain only evidence and acceptance unaffected by changes to the candidate, inputs, or relevant environment. 6. Return `PASS` only when every required criterion has proof, required perspectives accept their scopes, and no required finding remains. Otherwise return `REVISE` with fixes for the caller to implement and resubmit, or `BLOCKED` with the unmet criterion, cause, options, recommendation, and consequence. On unchanged evidence, change approach rather than retrying or lowering criteria. ## Pitfalls diff --git a/plugins/claude/skills/explore-decisions/references/vstack/protocols/quality-validation.md b/plugins/claude/skills/explore-decisions/references/vstack/protocols/quality-validation.md index e038fe9..9a0d797 100644 --- a/plugins/claude/skills/explore-decisions/references/vstack/protocols/quality-validation.md +++ b/plugins/claude/skills/explore-decisions/references/vstack/protocols/quality-validation.md @@ -15,9 +15,9 @@ 1. Reuse the caller's validation contract. Record candidate, mode, required criteria, evidence or checks, unacceptable outcomes, and useful review perspectives from the request, applicable instructions, principles, and owning workflow. 2. Have the producer self-assess each criterion as pass, fail, or unverified with evidence. Return known defects to the caller before independent review. A score may summarize a defined rubric but cannot replace required proof. -3. For substantive work, use distinct subagents for review of correctness, completeness, and preserved behavior, and critique of assumptions, necessity, simplicity, and alternatives. Give each the same contract, candidate, evidence, and bounded scope. Use direct checks for mechanical work; without subagents, assess sequentially and report unavailable independence. If independent review is required but unavailable, return `BLOCKED`. +3. For substantive work, obtain review of correctness, completeness, and preserved behavior, and critique of assumptions, necessity, simplicity, and alternatives from reviewers independent of the producer. One reviewer may cover both; add reviewers only for required separation or non-overlapping parallel scopes. Supply scoped criteria, the candidate or diff, and current evidence. Assign checks within each reviewer's tools and authority; return missing required evidence to the caller. Use direct checks for mechanical work. Without subagents, assess sequentially and report missing independence; return `BLOCKED` if required independent review is unavailable. 4. Collect verdicts and findings with criterion, location or scenario, evidence, impact, smallest remedy, and acceptance check. Deduplicate them into required fixes, selected improvements, optional suggestions, and justified rejections. Resolve disagreements with evidence; a disputed required criterion remains open. -5. Return actionable fixes to the caller. After every authorized revision, rerun invalidated checks and request fresh verdicts from affected reviewers and critics. Reuse only evidence and acceptance unaffected by the current candidate. +5. Return fixes to the caller. After authorized revisions, send affected reviewers the reason, revised material, and invalidated evidence. Rerun invalidated checks and renew affected verdicts; retain only evidence and acceptance unaffected by changes to the candidate, inputs, or relevant environment. 6. Return `PASS` only when every required criterion has proof, required perspectives accept their scopes, and no required finding remains. Otherwise return `REVISE` with fixes for the caller to implement and resubmit, or `BLOCKED` with the unmet criterion, cause, options, recommendation, and consequence. On unchanged evidence, change approach rather than retrying or lowering criteria. ## Pitfalls diff --git a/plugins/claude/skills/improve-code/references/vstack/protocols/quality-validation.md b/plugins/claude/skills/improve-code/references/vstack/protocols/quality-validation.md index e038fe9..9a0d797 100644 --- a/plugins/claude/skills/improve-code/references/vstack/protocols/quality-validation.md +++ b/plugins/claude/skills/improve-code/references/vstack/protocols/quality-validation.md @@ -15,9 +15,9 @@ 1. Reuse the caller's validation contract. Record candidate, mode, required criteria, evidence or checks, unacceptable outcomes, and useful review perspectives from the request, applicable instructions, principles, and owning workflow. 2. Have the producer self-assess each criterion as pass, fail, or unverified with evidence. Return known defects to the caller before independent review. A score may summarize a defined rubric but cannot replace required proof. -3. For substantive work, use distinct subagents for review of correctness, completeness, and preserved behavior, and critique of assumptions, necessity, simplicity, and alternatives. Give each the same contract, candidate, evidence, and bounded scope. Use direct checks for mechanical work; without subagents, assess sequentially and report unavailable independence. If independent review is required but unavailable, return `BLOCKED`. +3. For substantive work, obtain review of correctness, completeness, and preserved behavior, and critique of assumptions, necessity, simplicity, and alternatives from reviewers independent of the producer. One reviewer may cover both; add reviewers only for required separation or non-overlapping parallel scopes. Supply scoped criteria, the candidate or diff, and current evidence. Assign checks within each reviewer's tools and authority; return missing required evidence to the caller. Use direct checks for mechanical work. Without subagents, assess sequentially and report missing independence; return `BLOCKED` if required independent review is unavailable. 4. Collect verdicts and findings with criterion, location or scenario, evidence, impact, smallest remedy, and acceptance check. Deduplicate them into required fixes, selected improvements, optional suggestions, and justified rejections. Resolve disagreements with evidence; a disputed required criterion remains open. -5. Return actionable fixes to the caller. After every authorized revision, rerun invalidated checks and request fresh verdicts from affected reviewers and critics. Reuse only evidence and acceptance unaffected by the current candidate. +5. Return fixes to the caller. After authorized revisions, send affected reviewers the reason, revised material, and invalidated evidence. Rerun invalidated checks and renew affected verdicts; retain only evidence and acceptance unaffected by changes to the candidate, inputs, or relevant environment. 6. Return `PASS` only when every required criterion has proof, required perspectives accept their scopes, and no required finding remains. Otherwise return `REVISE` with fixes for the caller to implement and resubmit, or `BLOCKED` with the unmet criterion, cause, options, recommendation, and consequence. On unchanged evidence, change approach rather than retrying or lowering criteria. ## Pitfalls diff --git a/plugins/claude/skills/improve-project/references/vstack/protocols/quality-validation.md b/plugins/claude/skills/improve-project/references/vstack/protocols/quality-validation.md index e038fe9..9a0d797 100644 --- a/plugins/claude/skills/improve-project/references/vstack/protocols/quality-validation.md +++ b/plugins/claude/skills/improve-project/references/vstack/protocols/quality-validation.md @@ -15,9 +15,9 @@ 1. Reuse the caller's validation contract. Record candidate, mode, required criteria, evidence or checks, unacceptable outcomes, and useful review perspectives from the request, applicable instructions, principles, and owning workflow. 2. Have the producer self-assess each criterion as pass, fail, or unverified with evidence. Return known defects to the caller before independent review. A score may summarize a defined rubric but cannot replace required proof. -3. For substantive work, use distinct subagents for review of correctness, completeness, and preserved behavior, and critique of assumptions, necessity, simplicity, and alternatives. Give each the same contract, candidate, evidence, and bounded scope. Use direct checks for mechanical work; without subagents, assess sequentially and report unavailable independence. If independent review is required but unavailable, return `BLOCKED`. +3. For substantive work, obtain review of correctness, completeness, and preserved behavior, and critique of assumptions, necessity, simplicity, and alternatives from reviewers independent of the producer. One reviewer may cover both; add reviewers only for required separation or non-overlapping parallel scopes. Supply scoped criteria, the candidate or diff, and current evidence. Assign checks within each reviewer's tools and authority; return missing required evidence to the caller. Use direct checks for mechanical work. Without subagents, assess sequentially and report missing independence; return `BLOCKED` if required independent review is unavailable. 4. Collect verdicts and findings with criterion, location or scenario, evidence, impact, smallest remedy, and acceptance check. Deduplicate them into required fixes, selected improvements, optional suggestions, and justified rejections. Resolve disagreements with evidence; a disputed required criterion remains open. -5. Return actionable fixes to the caller. After every authorized revision, rerun invalidated checks and request fresh verdicts from affected reviewers and critics. Reuse only evidence and acceptance unaffected by the current candidate. +5. Return fixes to the caller. After authorized revisions, send affected reviewers the reason, revised material, and invalidated evidence. Rerun invalidated checks and renew affected verdicts; retain only evidence and acceptance unaffected by changes to the candidate, inputs, or relevant environment. 6. Return `PASS` only when every required criterion has proof, required perspectives accept their scopes, and no required finding remains. Otherwise return `REVISE` with fixes for the caller to implement and resubmit, or `BLOCKED` with the unmet criterion, cause, options, recommendation, and consequence. On unchanged evidence, change approach rather than retrying or lowering criteria. ## Pitfalls diff --git a/plugins/claude/skills/improve-ui/references/vstack/protocols/quality-validation.md b/plugins/claude/skills/improve-ui/references/vstack/protocols/quality-validation.md index e038fe9..9a0d797 100644 --- a/plugins/claude/skills/improve-ui/references/vstack/protocols/quality-validation.md +++ b/plugins/claude/skills/improve-ui/references/vstack/protocols/quality-validation.md @@ -15,9 +15,9 @@ 1. Reuse the caller's validation contract. Record candidate, mode, required criteria, evidence or checks, unacceptable outcomes, and useful review perspectives from the request, applicable instructions, principles, and owning workflow. 2. Have the producer self-assess each criterion as pass, fail, or unverified with evidence. Return known defects to the caller before independent review. A score may summarize a defined rubric but cannot replace required proof. -3. For substantive work, use distinct subagents for review of correctness, completeness, and preserved behavior, and critique of assumptions, necessity, simplicity, and alternatives. Give each the same contract, candidate, evidence, and bounded scope. Use direct checks for mechanical work; without subagents, assess sequentially and report unavailable independence. If independent review is required but unavailable, return `BLOCKED`. +3. For substantive work, obtain review of correctness, completeness, and preserved behavior, and critique of assumptions, necessity, simplicity, and alternatives from reviewers independent of the producer. One reviewer may cover both; add reviewers only for required separation or non-overlapping parallel scopes. Supply scoped criteria, the candidate or diff, and current evidence. Assign checks within each reviewer's tools and authority; return missing required evidence to the caller. Use direct checks for mechanical work. Without subagents, assess sequentially and report missing independence; return `BLOCKED` if required independent review is unavailable. 4. Collect verdicts and findings with criterion, location or scenario, evidence, impact, smallest remedy, and acceptance check. Deduplicate them into required fixes, selected improvements, optional suggestions, and justified rejections. Resolve disagreements with evidence; a disputed required criterion remains open. -5. Return actionable fixes to the caller. After every authorized revision, rerun invalidated checks and request fresh verdicts from affected reviewers and critics. Reuse only evidence and acceptance unaffected by the current candidate. +5. Return fixes to the caller. After authorized revisions, send affected reviewers the reason, revised material, and invalidated evidence. Rerun invalidated checks and renew affected verdicts; retain only evidence and acceptance unaffected by changes to the candidate, inputs, or relevant environment. 6. Return `PASS` only when every required criterion has proof, required perspectives accept their scopes, and no required finding remains. Otherwise return `REVISE` with fixes for the caller to implement and resubmit, or `BLOCKED` with the unmet criterion, cause, options, recommendation, and consequence. On unchanged evidence, change approach rather than retrying or lowering criteria. ## Pitfalls diff --git a/plugins/claude/skills/manage-defects/references/vstack/protocols/quality-validation.md b/plugins/claude/skills/manage-defects/references/vstack/protocols/quality-validation.md index e038fe9..9a0d797 100644 --- a/plugins/claude/skills/manage-defects/references/vstack/protocols/quality-validation.md +++ b/plugins/claude/skills/manage-defects/references/vstack/protocols/quality-validation.md @@ -15,9 +15,9 @@ 1. Reuse the caller's validation contract. Record candidate, mode, required criteria, evidence or checks, unacceptable outcomes, and useful review perspectives from the request, applicable instructions, principles, and owning workflow. 2. Have the producer self-assess each criterion as pass, fail, or unverified with evidence. Return known defects to the caller before independent review. A score may summarize a defined rubric but cannot replace required proof. -3. For substantive work, use distinct subagents for review of correctness, completeness, and preserved behavior, and critique of assumptions, necessity, simplicity, and alternatives. Give each the same contract, candidate, evidence, and bounded scope. Use direct checks for mechanical work; without subagents, assess sequentially and report unavailable independence. If independent review is required but unavailable, return `BLOCKED`. +3. For substantive work, obtain review of correctness, completeness, and preserved behavior, and critique of assumptions, necessity, simplicity, and alternatives from reviewers independent of the producer. One reviewer may cover both; add reviewers only for required separation or non-overlapping parallel scopes. Supply scoped criteria, the candidate or diff, and current evidence. Assign checks within each reviewer's tools and authority; return missing required evidence to the caller. Use direct checks for mechanical work. Without subagents, assess sequentially and report missing independence; return `BLOCKED` if required independent review is unavailable. 4. Collect verdicts and findings with criterion, location or scenario, evidence, impact, smallest remedy, and acceptance check. Deduplicate them into required fixes, selected improvements, optional suggestions, and justified rejections. Resolve disagreements with evidence; a disputed required criterion remains open. -5. Return actionable fixes to the caller. After every authorized revision, rerun invalidated checks and request fresh verdicts from affected reviewers and critics. Reuse only evidence and acceptance unaffected by the current candidate. +5. Return fixes to the caller. After authorized revisions, send affected reviewers the reason, revised material, and invalidated evidence. Rerun invalidated checks and renew affected verdicts; retain only evidence and acceptance unaffected by changes to the candidate, inputs, or relevant environment. 6. Return `PASS` only when every required criterion has proof, required perspectives accept their scopes, and no required finding remains. Otherwise return `REVISE` with fixes for the caller to implement and resubmit, or `BLOCKED` with the unmet criterion, cause, options, recommendation, and consequence. On unchanged evidence, change approach rather than retrying or lowering criteria. ## Pitfalls diff --git a/plugins/claude/skills/manage-issues/references/vstack/protocols/quality-validation.md b/plugins/claude/skills/manage-issues/references/vstack/protocols/quality-validation.md index e038fe9..9a0d797 100644 --- a/plugins/claude/skills/manage-issues/references/vstack/protocols/quality-validation.md +++ b/plugins/claude/skills/manage-issues/references/vstack/protocols/quality-validation.md @@ -15,9 +15,9 @@ 1. Reuse the caller's validation contract. Record candidate, mode, required criteria, evidence or checks, unacceptable outcomes, and useful review perspectives from the request, applicable instructions, principles, and owning workflow. 2. Have the producer self-assess each criterion as pass, fail, or unverified with evidence. Return known defects to the caller before independent review. A score may summarize a defined rubric but cannot replace required proof. -3. For substantive work, use distinct subagents for review of correctness, completeness, and preserved behavior, and critique of assumptions, necessity, simplicity, and alternatives. Give each the same contract, candidate, evidence, and bounded scope. Use direct checks for mechanical work; without subagents, assess sequentially and report unavailable independence. If independent review is required but unavailable, return `BLOCKED`. +3. For substantive work, obtain review of correctness, completeness, and preserved behavior, and critique of assumptions, necessity, simplicity, and alternatives from reviewers independent of the producer. One reviewer may cover both; add reviewers only for required separation or non-overlapping parallel scopes. Supply scoped criteria, the candidate or diff, and current evidence. Assign checks within each reviewer's tools and authority; return missing required evidence to the caller. Use direct checks for mechanical work. Without subagents, assess sequentially and report missing independence; return `BLOCKED` if required independent review is unavailable. 4. Collect verdicts and findings with criterion, location or scenario, evidence, impact, smallest remedy, and acceptance check. Deduplicate them into required fixes, selected improvements, optional suggestions, and justified rejections. Resolve disagreements with evidence; a disputed required criterion remains open. -5. Return actionable fixes to the caller. After every authorized revision, rerun invalidated checks and request fresh verdicts from affected reviewers and critics. Reuse only evidence and acceptance unaffected by the current candidate. +5. Return fixes to the caller. After authorized revisions, send affected reviewers the reason, revised material, and invalidated evidence. Rerun invalidated checks and renew affected verdicts; retain only evidence and acceptance unaffected by changes to the candidate, inputs, or relevant environment. 6. Return `PASS` only when every required criterion has proof, required perspectives accept their scopes, and no required finding remains. Otherwise return `REVISE` with fixes for the caller to implement and resubmit, or `BLOCKED` with the unmet criterion, cause, options, recommendation, and consequence. On unchanged evidence, change approach rather than retrying or lowering criteria. ## Pitfalls diff --git a/plugins/claude/skills/manage-roadmap/references/vstack/protocols/quality-validation.md b/plugins/claude/skills/manage-roadmap/references/vstack/protocols/quality-validation.md index e038fe9..9a0d797 100644 --- a/plugins/claude/skills/manage-roadmap/references/vstack/protocols/quality-validation.md +++ b/plugins/claude/skills/manage-roadmap/references/vstack/protocols/quality-validation.md @@ -15,9 +15,9 @@ 1. Reuse the caller's validation contract. Record candidate, mode, required criteria, evidence or checks, unacceptable outcomes, and useful review perspectives from the request, applicable instructions, principles, and owning workflow. 2. Have the producer self-assess each criterion as pass, fail, or unverified with evidence. Return known defects to the caller before independent review. A score may summarize a defined rubric but cannot replace required proof. -3. For substantive work, use distinct subagents for review of correctness, completeness, and preserved behavior, and critique of assumptions, necessity, simplicity, and alternatives. Give each the same contract, candidate, evidence, and bounded scope. Use direct checks for mechanical work; without subagents, assess sequentially and report unavailable independence. If independent review is required but unavailable, return `BLOCKED`. +3. For substantive work, obtain review of correctness, completeness, and preserved behavior, and critique of assumptions, necessity, simplicity, and alternatives from reviewers independent of the producer. One reviewer may cover both; add reviewers only for required separation or non-overlapping parallel scopes. Supply scoped criteria, the candidate or diff, and current evidence. Assign checks within each reviewer's tools and authority; return missing required evidence to the caller. Use direct checks for mechanical work. Without subagents, assess sequentially and report missing independence; return `BLOCKED` if required independent review is unavailable. 4. Collect verdicts and findings with criterion, location or scenario, evidence, impact, smallest remedy, and acceptance check. Deduplicate them into required fixes, selected improvements, optional suggestions, and justified rejections. Resolve disagreements with evidence; a disputed required criterion remains open. -5. Return actionable fixes to the caller. After every authorized revision, rerun invalidated checks and request fresh verdicts from affected reviewers and critics. Reuse only evidence and acceptance unaffected by the current candidate. +5. Return fixes to the caller. After authorized revisions, send affected reviewers the reason, revised material, and invalidated evidence. Rerun invalidated checks and renew affected verdicts; retain only evidence and acceptance unaffected by changes to the candidate, inputs, or relevant environment. 6. Return `PASS` only when every required criterion has proof, required perspectives accept their scopes, and no required finding remains. Otherwise return `REVISE` with fixes for the caller to implement and resubmit, or `BLOCKED` with the unmet criterion, cause, options, recommendation, and consequence. On unchanged evidence, change approach rather than retrying or lowering criteria. ## Pitfalls diff --git a/plugins/claude/skills/manage-rules/references/vstack/protocols/quality-validation.md b/plugins/claude/skills/manage-rules/references/vstack/protocols/quality-validation.md index e038fe9..9a0d797 100644 --- a/plugins/claude/skills/manage-rules/references/vstack/protocols/quality-validation.md +++ b/plugins/claude/skills/manage-rules/references/vstack/protocols/quality-validation.md @@ -15,9 +15,9 @@ 1. Reuse the caller's validation contract. Record candidate, mode, required criteria, evidence or checks, unacceptable outcomes, and useful review perspectives from the request, applicable instructions, principles, and owning workflow. 2. Have the producer self-assess each criterion as pass, fail, or unverified with evidence. Return known defects to the caller before independent review. A score may summarize a defined rubric but cannot replace required proof. -3. For substantive work, use distinct subagents for review of correctness, completeness, and preserved behavior, and critique of assumptions, necessity, simplicity, and alternatives. Give each the same contract, candidate, evidence, and bounded scope. Use direct checks for mechanical work; without subagents, assess sequentially and report unavailable independence. If independent review is required but unavailable, return `BLOCKED`. +3. For substantive work, obtain review of correctness, completeness, and preserved behavior, and critique of assumptions, necessity, simplicity, and alternatives from reviewers independent of the producer. One reviewer may cover both; add reviewers only for required separation or non-overlapping parallel scopes. Supply scoped criteria, the candidate or diff, and current evidence. Assign checks within each reviewer's tools and authority; return missing required evidence to the caller. Use direct checks for mechanical work. Without subagents, assess sequentially and report missing independence; return `BLOCKED` if required independent review is unavailable. 4. Collect verdicts and findings with criterion, location or scenario, evidence, impact, smallest remedy, and acceptance check. Deduplicate them into required fixes, selected improvements, optional suggestions, and justified rejections. Resolve disagreements with evidence; a disputed required criterion remains open. -5. Return actionable fixes to the caller. After every authorized revision, rerun invalidated checks and request fresh verdicts from affected reviewers and critics. Reuse only evidence and acceptance unaffected by the current candidate. +5. Return fixes to the caller. After authorized revisions, send affected reviewers the reason, revised material, and invalidated evidence. Rerun invalidated checks and renew affected verdicts; retain only evidence and acceptance unaffected by changes to the candidate, inputs, or relevant environment. 6. Return `PASS` only when every required criterion has proof, required perspectives accept their scopes, and no required finding remains. Otherwise return `REVISE` with fixes for the caller to implement and resubmit, or `BLOCKED` with the unmet criterion, cause, options, recommendation, and consequence. On unchanged evidence, change approach rather than retrying or lowering criteria. ## Pitfalls diff --git a/plugins/claude/skills/manage-skills/references/vstack/protocols/quality-validation.md b/plugins/claude/skills/manage-skills/references/vstack/protocols/quality-validation.md index e038fe9..9a0d797 100644 --- a/plugins/claude/skills/manage-skills/references/vstack/protocols/quality-validation.md +++ b/plugins/claude/skills/manage-skills/references/vstack/protocols/quality-validation.md @@ -15,9 +15,9 @@ 1. Reuse the caller's validation contract. Record candidate, mode, required criteria, evidence or checks, unacceptable outcomes, and useful review perspectives from the request, applicable instructions, principles, and owning workflow. 2. Have the producer self-assess each criterion as pass, fail, or unverified with evidence. Return known defects to the caller before independent review. A score may summarize a defined rubric but cannot replace required proof. -3. For substantive work, use distinct subagents for review of correctness, completeness, and preserved behavior, and critique of assumptions, necessity, simplicity, and alternatives. Give each the same contract, candidate, evidence, and bounded scope. Use direct checks for mechanical work; without subagents, assess sequentially and report unavailable independence. If independent review is required but unavailable, return `BLOCKED`. +3. For substantive work, obtain review of correctness, completeness, and preserved behavior, and critique of assumptions, necessity, simplicity, and alternatives from reviewers independent of the producer. One reviewer may cover both; add reviewers only for required separation or non-overlapping parallel scopes. Supply scoped criteria, the candidate or diff, and current evidence. Assign checks within each reviewer's tools and authority; return missing required evidence to the caller. Use direct checks for mechanical work. Without subagents, assess sequentially and report missing independence; return `BLOCKED` if required independent review is unavailable. 4. Collect verdicts and findings with criterion, location or scenario, evidence, impact, smallest remedy, and acceptance check. Deduplicate them into required fixes, selected improvements, optional suggestions, and justified rejections. Resolve disagreements with evidence; a disputed required criterion remains open. -5. Return actionable fixes to the caller. After every authorized revision, rerun invalidated checks and request fresh verdicts from affected reviewers and critics. Reuse only evidence and acceptance unaffected by the current candidate. +5. Return fixes to the caller. After authorized revisions, send affected reviewers the reason, revised material, and invalidated evidence. Rerun invalidated checks and renew affected verdicts; retain only evidence and acceptance unaffected by changes to the candidate, inputs, or relevant environment. 6. Return `PASS` only when every required criterion has proof, required perspectives accept their scopes, and no required finding remains. Otherwise return `REVISE` with fixes for the caller to implement and resubmit, or `BLOCKED` with the unmet criterion, cause, options, recommendation, and consequence. On unchanged evidence, change approach rather than retrying or lowering criteria. ## Pitfalls diff --git a/plugins/claude/skills/manage-vision/references/vstack/protocols/quality-validation.md b/plugins/claude/skills/manage-vision/references/vstack/protocols/quality-validation.md index e038fe9..9a0d797 100644 --- a/plugins/claude/skills/manage-vision/references/vstack/protocols/quality-validation.md +++ b/plugins/claude/skills/manage-vision/references/vstack/protocols/quality-validation.md @@ -15,9 +15,9 @@ 1. Reuse the caller's validation contract. Record candidate, mode, required criteria, evidence or checks, unacceptable outcomes, and useful review perspectives from the request, applicable instructions, principles, and owning workflow. 2. Have the producer self-assess each criterion as pass, fail, or unverified with evidence. Return known defects to the caller before independent review. A score may summarize a defined rubric but cannot replace required proof. -3. For substantive work, use distinct subagents for review of correctness, completeness, and preserved behavior, and critique of assumptions, necessity, simplicity, and alternatives. Give each the same contract, candidate, evidence, and bounded scope. Use direct checks for mechanical work; without subagents, assess sequentially and report unavailable independence. If independent review is required but unavailable, return `BLOCKED`. +3. For substantive work, obtain review of correctness, completeness, and preserved behavior, and critique of assumptions, necessity, simplicity, and alternatives from reviewers independent of the producer. One reviewer may cover both; add reviewers only for required separation or non-overlapping parallel scopes. Supply scoped criteria, the candidate or diff, and current evidence. Assign checks within each reviewer's tools and authority; return missing required evidence to the caller. Use direct checks for mechanical work. Without subagents, assess sequentially and report missing independence; return `BLOCKED` if required independent review is unavailable. 4. Collect verdicts and findings with criterion, location or scenario, evidence, impact, smallest remedy, and acceptance check. Deduplicate them into required fixes, selected improvements, optional suggestions, and justified rejections. Resolve disagreements with evidence; a disputed required criterion remains open. -5. Return actionable fixes to the caller. After every authorized revision, rerun invalidated checks and request fresh verdicts from affected reviewers and critics. Reuse only evidence and acceptance unaffected by the current candidate. +5. Return fixes to the caller. After authorized revisions, send affected reviewers the reason, revised material, and invalidated evidence. Rerun invalidated checks and renew affected verdicts; retain only evidence and acceptance unaffected by changes to the candidate, inputs, or relevant environment. 6. Return `PASS` only when every required criterion has proof, required perspectives accept their scopes, and no required finding remains. Otherwise return `REVISE` with fixes for the caller to implement and resubmit, or `BLOCKED` with the unmet criterion, cause, options, recommendation, and consequence. On unchanged evidence, change approach rather than retrying or lowering criteria. ## Pitfalls diff --git a/plugins/claude/skills/plan-issues/references/vstack/protocols/quality-validation.md b/plugins/claude/skills/plan-issues/references/vstack/protocols/quality-validation.md index e038fe9..9a0d797 100644 --- a/plugins/claude/skills/plan-issues/references/vstack/protocols/quality-validation.md +++ b/plugins/claude/skills/plan-issues/references/vstack/protocols/quality-validation.md @@ -15,9 +15,9 @@ 1. Reuse the caller's validation contract. Record candidate, mode, required criteria, evidence or checks, unacceptable outcomes, and useful review perspectives from the request, applicable instructions, principles, and owning workflow. 2. Have the producer self-assess each criterion as pass, fail, or unverified with evidence. Return known defects to the caller before independent review. A score may summarize a defined rubric but cannot replace required proof. -3. For substantive work, use distinct subagents for review of correctness, completeness, and preserved behavior, and critique of assumptions, necessity, simplicity, and alternatives. Give each the same contract, candidate, evidence, and bounded scope. Use direct checks for mechanical work; without subagents, assess sequentially and report unavailable independence. If independent review is required but unavailable, return `BLOCKED`. +3. For substantive work, obtain review of correctness, completeness, and preserved behavior, and critique of assumptions, necessity, simplicity, and alternatives from reviewers independent of the producer. One reviewer may cover both; add reviewers only for required separation or non-overlapping parallel scopes. Supply scoped criteria, the candidate or diff, and current evidence. Assign checks within each reviewer's tools and authority; return missing required evidence to the caller. Use direct checks for mechanical work. Without subagents, assess sequentially and report missing independence; return `BLOCKED` if required independent review is unavailable. 4. Collect verdicts and findings with criterion, location or scenario, evidence, impact, smallest remedy, and acceptance check. Deduplicate them into required fixes, selected improvements, optional suggestions, and justified rejections. Resolve disagreements with evidence; a disputed required criterion remains open. -5. Return actionable fixes to the caller. After every authorized revision, rerun invalidated checks and request fresh verdicts from affected reviewers and critics. Reuse only evidence and acceptance unaffected by the current candidate. +5. Return fixes to the caller. After authorized revisions, send affected reviewers the reason, revised material, and invalidated evidence. Rerun invalidated checks and renew affected verdicts; retain only evidence and acceptance unaffected by changes to the candidate, inputs, or relevant environment. 6. Return `PASS` only when every required criterion has proof, required perspectives accept their scopes, and no required finding remains. Otherwise return `REVISE` with fixes for the caller to implement and resubmit, or `BLOCKED` with the unmet criterion, cause, options, recommendation, and consequence. On unchanged evidence, change approach rather than retrying or lowering criteria. ## Pitfalls diff --git a/plugins/claude/skills/plan-work/references/vstack/protocols/quality-validation.md b/plugins/claude/skills/plan-work/references/vstack/protocols/quality-validation.md index e038fe9..9a0d797 100644 --- a/plugins/claude/skills/plan-work/references/vstack/protocols/quality-validation.md +++ b/plugins/claude/skills/plan-work/references/vstack/protocols/quality-validation.md @@ -15,9 +15,9 @@ 1. Reuse the caller's validation contract. Record candidate, mode, required criteria, evidence or checks, unacceptable outcomes, and useful review perspectives from the request, applicable instructions, principles, and owning workflow. 2. Have the producer self-assess each criterion as pass, fail, or unverified with evidence. Return known defects to the caller before independent review. A score may summarize a defined rubric but cannot replace required proof. -3. For substantive work, use distinct subagents for review of correctness, completeness, and preserved behavior, and critique of assumptions, necessity, simplicity, and alternatives. Give each the same contract, candidate, evidence, and bounded scope. Use direct checks for mechanical work; without subagents, assess sequentially and report unavailable independence. If independent review is required but unavailable, return `BLOCKED`. +3. For substantive work, obtain review of correctness, completeness, and preserved behavior, and critique of assumptions, necessity, simplicity, and alternatives from reviewers independent of the producer. One reviewer may cover both; add reviewers only for required separation or non-overlapping parallel scopes. Supply scoped criteria, the candidate or diff, and current evidence. Assign checks within each reviewer's tools and authority; return missing required evidence to the caller. Use direct checks for mechanical work. Without subagents, assess sequentially and report missing independence; return `BLOCKED` if required independent review is unavailable. 4. Collect verdicts and findings with criterion, location or scenario, evidence, impact, smallest remedy, and acceptance check. Deduplicate them into required fixes, selected improvements, optional suggestions, and justified rejections. Resolve disagreements with evidence; a disputed required criterion remains open. -5. Return actionable fixes to the caller. After every authorized revision, rerun invalidated checks and request fresh verdicts from affected reviewers and critics. Reuse only evidence and acceptance unaffected by the current candidate. +5. Return fixes to the caller. After authorized revisions, send affected reviewers the reason, revised material, and invalidated evidence. Rerun invalidated checks and renew affected verdicts; retain only evidence and acceptance unaffected by changes to the candidate, inputs, or relevant environment. 6. Return `PASS` only when every required criterion has proof, required perspectives accept their scopes, and no required finding remains. Otherwise return `REVISE` with fixes for the caller to implement and resubmit, or `BLOCKED` with the unmet criterion, cause, options, recommendation, and consequence. On unchanged evidence, change approach rather than retrying or lowering criteria. ## Pitfalls diff --git a/plugins/claude/skills/review-ui/references/vstack/protocols/quality-validation.md b/plugins/claude/skills/review-ui/references/vstack/protocols/quality-validation.md index e038fe9..9a0d797 100644 --- a/plugins/claude/skills/review-ui/references/vstack/protocols/quality-validation.md +++ b/plugins/claude/skills/review-ui/references/vstack/protocols/quality-validation.md @@ -15,9 +15,9 @@ 1. Reuse the caller's validation contract. Record candidate, mode, required criteria, evidence or checks, unacceptable outcomes, and useful review perspectives from the request, applicable instructions, principles, and owning workflow. 2. Have the producer self-assess each criterion as pass, fail, or unverified with evidence. Return known defects to the caller before independent review. A score may summarize a defined rubric but cannot replace required proof. -3. For substantive work, use distinct subagents for review of correctness, completeness, and preserved behavior, and critique of assumptions, necessity, simplicity, and alternatives. Give each the same contract, candidate, evidence, and bounded scope. Use direct checks for mechanical work; without subagents, assess sequentially and report unavailable independence. If independent review is required but unavailable, return `BLOCKED`. +3. For substantive work, obtain review of correctness, completeness, and preserved behavior, and critique of assumptions, necessity, simplicity, and alternatives from reviewers independent of the producer. One reviewer may cover both; add reviewers only for required separation or non-overlapping parallel scopes. Supply scoped criteria, the candidate or diff, and current evidence. Assign checks within each reviewer's tools and authority; return missing required evidence to the caller. Use direct checks for mechanical work. Without subagents, assess sequentially and report missing independence; return `BLOCKED` if required independent review is unavailable. 4. Collect verdicts and findings with criterion, location or scenario, evidence, impact, smallest remedy, and acceptance check. Deduplicate them into required fixes, selected improvements, optional suggestions, and justified rejections. Resolve disagreements with evidence; a disputed required criterion remains open. -5. Return actionable fixes to the caller. After every authorized revision, rerun invalidated checks and request fresh verdicts from affected reviewers and critics. Reuse only evidence and acceptance unaffected by the current candidate. +5. Return fixes to the caller. After authorized revisions, send affected reviewers the reason, revised material, and invalidated evidence. Rerun invalidated checks and renew affected verdicts; retain only evidence and acceptance unaffected by changes to the candidate, inputs, or relevant environment. 6. Return `PASS` only when every required criterion has proof, required perspectives accept their scopes, and no required finding remains. Otherwise return `REVISE` with fixes for the caller to implement and resubmit, or `BLOCKED` with the unmet criterion, cause, options, recommendation, and consequence. On unchanged evidence, change approach rather than retrying or lowering criteria. ## Pitfalls diff --git a/plugins/claude/skills/vllnt-collaboration-principles/SKILL.md b/plugins/claude/skills/vllnt-collaboration-principles/SKILL.md index 603afda..989c51b 100644 --- a/plugins/claude/skills/vllnt-collaboration-principles/SKILL.md +++ b/plugins/claude/skills/vllnt-collaboration-principles/SKILL.md @@ -7,7 +7,6 @@ description: Load at each session start to keep human collaboration proactive, c - Advance within the request and established authority. Infer routine reversible details; missing prohibitions do not authorize unrelated actions. - Complete necessary authorized work without routine permission requests. Continue useful independent work while a decision is pending. -- Reply simply: state the result or current status, then the next action. Include detail only when it changes a decision, risk, or verification. +- End with a brief outcome and any unfinished or unverified requested work. Distinguish completed actions from proposals and attempts. - Ask only for missing authority, access, or a consequential choice. First identify the cause, try safe alternatives, and prepare the concrete result. -- For a genuine blocker, give the smallest viable options, a recommendation, and the consequence. Use a targeted yes/no question when sufficient. -- Return useful partial work and the unmet condition when completion is impossible; never present proposed or attempted work as completed. +- If blocked, state the cause—or that it is unknown—and concrete options with key tradeoffs. Recommend the next action, name who must act, and specify any required input or approval. Do not ask the user to do work you can complete within existing authority. diff --git a/plugins/codex/SOURCE.json b/plugins/codex/SOURCE.json index a8112d2..2eb00aa 100644 --- a/plugins/codex/SOURCE.json +++ b/plugins/codex/SOURCE.json @@ -1,13 +1,13 @@ { "files": { "LICENSE": "24ba061a4603738ddd5105ef4abc198eeded5ac7efce23b360561816f4dd6559", - "plugin.json": "2c4de6dbfd44f784f2af7a65d1fa186c4c32c95a96c3afe011d3bc724b4e40cb", + "plugin.json": "dbda3fe5dbdb27421df463703f999096a733ab47bf73109df4fda62bd4902d59", "skills/build-landing-page/README.md": "46a280eadac8962180cf3f0c42eb0e845a3b0156a644569182d932881e1d51f8", "skills/build-landing-page/SKILL.md": "b08e4963d6149f3647b28a0d9dccdc8793812abab95a1d081d93699e142de0f0", "skills/build-landing-page/references/copywriting-formulas.md": "6d19f6166e1badcfdda0af4f8b303160e94ee6e6149321157e12849654cc013e", "skills/build-landing-page/references/review-rubric.md": "6c06f95eea847f63e2327b34c89fb167fec0f52360cd50bcfa257f9f96f33b0e", "skills/build-landing-page/references/structure-blueprints.md": "1f0a52ecb8d4d78f3f9eea6d89db8f471188986e1a9ad39b19587e52001e99e3", - "skills/build-landing-page/references/vstack/protocols/quality-validation.md": "522c097cb146a9fd016fd91facadb3faa13b0d6f7f14707d7bdf23aca3143b19", + "skills/build-landing-page/references/vstack/protocols/quality-validation.md": "e53fca023d31b907d60019c68a5d823e0d89ae83d09e49e68c71bc9ec5a1303a", "skills/build-project/SKILL.md": "719bff37da357fb73062ff302a86650e4d1611f5b7d8712155a94a6802a985d0", "skills/build-project/references/vstack/capabilities/convex-components/REFERENCE.md": "ebd776c115b578aff19f6bfceee61cb694afe63546a882de50cb020f6ba996e5", "skills/build-project/references/vstack/capabilities/eslint-configuration/REFERENCE.md": "5a2e090a253b89b6dee9c474a7044cd10be81427792c51b7a3322c0f163ae44b", @@ -16,9 +16,9 @@ "skills/build-project/references/vstack/capabilities/stack-packages/references/github-npm.md": "c1731affd8f0be4c62b988e45659b754948513e9b6ef8c61b96cab10bc0ffef2", "skills/build-project/references/vstack/capabilities/typescript-configuration/REFERENCE.md": "baccc320777d2050be44ccd2219e38f0dbf199127da11598642d53e71c594bba", "skills/build-project/references/vstack/capabilities/workspace-turborepo/REFERENCE.md": "af854042419d04d4f6af4454bcee41f3275fb70c466fd6efefa1bff273e295ab", - "skills/build-project/references/vstack/protocols/quality-validation.md": "522c097cb146a9fd016fd91facadb3faa13b0d6f7f14707d7bdf23aca3143b19", + "skills/build-project/references/vstack/protocols/quality-validation.md": "e53fca023d31b907d60019c68a5d823e0d89ae83d09e49e68c71bc9ec5a1303a", "skills/build-prototype/SKILL.md": "7a27f04b673c733ab6aa0e4f3eed68f8fa1ce82884e22eda6ec24cbba5ab162e", - "skills/build-prototype/references/vstack/protocols/quality-validation.md": "522c097cb146a9fd016fd91facadb3faa13b0d6f7f14707d7bdf23aca3143b19", + "skills/build-prototype/references/vstack/protocols/quality-validation.md": "e53fca023d31b907d60019c68a5d823e0d89ae83d09e49e68c71bc9ec5a1303a", "skills/deliver-issue/SKILL.md": "a81532ec0e731f80092f4be969d73f923b84fdc240b58781b86e3b8095b288bc", "skills/deliver-issue/references/vstack/capabilities/code-architecture/DEEPENING.md": "9850a1364402229df25d0fd686b6905bbcbdaa52fccaf7d5344307fd900fed2e", "skills/deliver-issue/references/vstack/capabilities/code-architecture/INTERFACE-DESIGN.md": "60d6651b5cd0de5479f60b7840b6e156cb41f2f80ae4a91c661f67874c5dbee8", @@ -28,7 +28,7 @@ "skills/deliver-issue/references/vstack/capabilities/convex-components/REFERENCE.md": "ebd776c115b578aff19f6bfceee61cb694afe63546a882de50cb020f6ba996e5", "skills/deliver-issue/references/vstack/capabilities/nextjs-tests/REFERENCE.md": "3447bd768cbf50efd1a12a60c72060f5a2ec1335fa56d45da091e376858780a9", "skills/deliver-issue/references/vstack/capabilities/ui-accessibility/REFERENCE.md": "f265d321d975a0319ab5455b7fefd74e4852de63b7bd14d1f9d044c78371c25b", - "skills/deliver-issue/references/vstack/protocols/quality-validation.md": "522c097cb146a9fd016fd91facadb3faa13b0d6f7f14707d7bdf23aca3143b19", + "skills/deliver-issue/references/vstack/protocols/quality-validation.md": "e53fca023d31b907d60019c68a5d823e0d89ae83d09e49e68c71bc9ec5a1303a", "skills/deliver-pull-request/SKILL.md": "afdf9ef8ae23fd899e5cbd246440efd6c2e10be2016599d85034bf89304df96c", "skills/deliver-pull-request/references/vstack/capabilities/ci-optimization/REFERENCE.md": "b376d64c2297e6ba535b581474bddb6c777c8a847d3424cdcc77fef7cd0d99a9", "skills/deliver-pull-request/references/vstack/capabilities/ci-optimization/references/scenarios.md": "731de32df4a92fcb78047b7f9c8b71ab9697ea1daebdc101295fdbc26a5c9320", @@ -47,12 +47,12 @@ "skills/deliver-pull-request/references/vstack/capabilities/release-readiness/references/release-messaging.md": "4f5cc13e7fd30cd84ccf84dbd02f0d5696ccb52a3b27c8f448a29c983e28a4c1", "skills/deliver-pull-request/references/vstack/capabilities/release-readiness/references/version-sync.md": "3e9ecae39a8e5f5a33914a4097ea5728c24ce9292618bd295761297fb1d7cb78", "skills/deliver-pull-request/references/vstack/capabilities/runtime-performance/REFERENCE.md": "6692e8fdd6a736d06b8adec108e07b6b19f8bcf0d62051cacc0d24f73a3ebcd9", - "skills/deliver-pull-request/references/vstack/protocols/quality-validation.md": "522c097cb146a9fd016fd91facadb3faa13b0d6f7f14707d7bdf23aca3143b19", + "skills/deliver-pull-request/references/vstack/protocols/quality-validation.md": "e53fca023d31b907d60019c68a5d823e0d89ae83d09e49e68c71bc9ec5a1303a", "skills/explain-subject/SKILL.md": "909b948a392bf37264d5747626fd8e75541d0b6a528c70bd2176a5ff0e9e8b85", "skills/explain-subject/references/vstack/capabilities/reasoning-assumptions/REFERENCE.md": "edf4b1bf183541c7198f8ec6a00e25db790c8510fe4fcf6c1060d9b2b4f9e50d", - "skills/explain-subject/references/vstack/protocols/quality-validation.md": "522c097cb146a9fd016fd91facadb3faa13b0d6f7f14707d7bdf23aca3143b19", + "skills/explain-subject/references/vstack/protocols/quality-validation.md": "e53fca023d31b907d60019c68a5d823e0d89ae83d09e49e68c71bc9ec5a1303a", "skills/explore-decisions/SKILL.md": "07a1f5daa4543de924cd3b5bc8dfd2b482aeb0e94da8338d328402fb5505d11b", - "skills/explore-decisions/references/vstack/protocols/quality-validation.md": "522c097cb146a9fd016fd91facadb3faa13b0d6f7f14707d7bdf23aca3143b19", + "skills/explore-decisions/references/vstack/protocols/quality-validation.md": "e53fca023d31b907d60019c68a5d823e0d89ae83d09e49e68c71bc9ec5a1303a", "skills/improve-code/SKILL.md": "98cf3810fcb70580dbbb915d6bd7aee5f664b4c3e3b64dc4743253574a452d46", "skills/improve-code/references/vstack/capabilities/code-architecture/DEEPENING.md": "9850a1364402229df25d0fd686b6905bbcbdaa52fccaf7d5344307fd900fed2e", "skills/improve-code/references/vstack/capabilities/code-architecture/INTERFACE-DESIGN.md": "60d6651b5cd0de5479f60b7840b6e156cb41f2f80ae4a91c661f67874c5dbee8", @@ -64,7 +64,7 @@ "skills/improve-code/references/vstack/capabilities/code-test-management/references/test-doubles.md": "c3006a6f6fef0039b8c8e879bfcf728bd553c85ce80f512521a08161c3c40a28", "skills/improve-code/references/vstack/capabilities/runtime-performance/REFERENCE.md": "6692e8fdd6a736d06b8adec108e07b6b19f8bcf0d62051cacc0d24f73a3ebcd9", "skills/improve-code/references/vstack/capabilities/workspace-turborepo/REFERENCE.md": "af854042419d04d4f6af4454bcee41f3275fb70c466fd6efefa1bff273e295ab", - "skills/improve-code/references/vstack/protocols/quality-validation.md": "522c097cb146a9fd016fd91facadb3faa13b0d6f7f14707d7bdf23aca3143b19", + "skills/improve-code/references/vstack/protocols/quality-validation.md": "e53fca023d31b907d60019c68a5d823e0d89ae83d09e49e68c71bc9ec5a1303a", "skills/improve-project/SKILL.md": "7d7a175d64e3180341c59d0d9b7cc4d1a2d20df37452673937701ac171b73e86", "skills/improve-project/references/vstack/capabilities/ci-optimization/REFERENCE.md": "b376d64c2297e6ba535b581474bddb6c777c8a847d3424cdcc77fef7cd0d99a9", "skills/improve-project/references/vstack/capabilities/ci-optimization/references/scenarios.md": "731de32df4a92fcb78047b7f9c8b71ab9697ea1daebdc101295fdbc26a5c9320", @@ -76,13 +76,13 @@ "skills/improve-project/references/vstack/capabilities/stack-packages/references/github-npm.md": "c1731affd8f0be4c62b988e45659b754948513e9b6ef8c61b96cab10bc0ffef2", "skills/improve-project/references/vstack/capabilities/typescript-configuration/REFERENCE.md": "baccc320777d2050be44ccd2219e38f0dbf199127da11598642d53e71c594bba", "skills/improve-project/references/vstack/capabilities/workspace-turborepo/REFERENCE.md": "af854042419d04d4f6af4454bcee41f3275fb70c466fd6efefa1bff273e295ab", - "skills/improve-project/references/vstack/protocols/quality-validation.md": "522c097cb146a9fd016fd91facadb3faa13b0d6f7f14707d7bdf23aca3143b19", + "skills/improve-project/references/vstack/protocols/quality-validation.md": "e53fca023d31b907d60019c68a5d823e0d89ae83d09e49e68c71bc9ec5a1303a", "skills/improve-ui/SKILL.md": "91989dc9cad28ee29e8f899132bf4e2de9dfe152aec653e03038287ab2b452d1", "skills/improve-ui/references/vstack/capabilities/ui-accessibility/REFERENCE.md": "f265d321d975a0319ab5455b7fefd74e4852de63b7bd14d1f9d044c78371c25b", "skills/improve-ui/references/vstack/capabilities/web-performance/REFERENCE.md": "52fb4ebb9e024fa6184da9187f3311d17a53c40691a63f5b2b6c471729f760ff", "skills/improve-ui/references/vstack/capabilities/web-performance/references/eval-audits.md": "d94253fb08c7059329022026843088c46c23a8615d134ace36eea4cb61fa9a6c", "skills/improve-ui/references/vstack/capabilities/web-performance/references/optimization-playbook.md": "0acdedcb0496f4926bee2d23a2294a152a8107c88c5e9f934afa8334e74fde13", - "skills/improve-ui/references/vstack/protocols/quality-validation.md": "522c097cb146a9fd016fd91facadb3faa13b0d6f7f14707d7bdf23aca3143b19", + "skills/improve-ui/references/vstack/protocols/quality-validation.md": "e53fca023d31b907d60019c68a5d823e0d89ae83d09e49e68c71bc9ec5a1303a", "skills/manage-defects/SKILL.md": "04d0501484ab5c507ace3ec204aae38b29b0cafd6f80747955c9118f8b0d97ba", "skills/manage-defects/references/vstack/capabilities/code-architecture/DEEPENING.md": "9850a1364402229df25d0fd686b6905bbcbdaa52fccaf7d5344307fd900fed2e", "skills/manage-defects/references/vstack/capabilities/code-architecture/INTERFACE-DESIGN.md": "60d6651b5cd0de5479f60b7840b6e156cb41f2f80ae4a91c661f67874c5dbee8", @@ -93,7 +93,7 @@ "skills/manage-defects/references/vstack/capabilities/nextjs-tests/REFERENCE.md": "3447bd768cbf50efd1a12a60c72060f5a2ec1335fa56d45da091e376858780a9", "skills/manage-defects/references/vstack/capabilities/runtime-performance/REFERENCE.md": "6692e8fdd6a736d06b8adec108e07b6b19f8bcf0d62051cacc0d24f73a3ebcd9", "skills/manage-defects/references/vstack/capabilities/ui-accessibility/REFERENCE.md": "f265d321d975a0319ab5455b7fefd74e4852de63b7bd14d1f9d044c78371c25b", - "skills/manage-defects/references/vstack/protocols/quality-validation.md": "522c097cb146a9fd016fd91facadb3faa13b0d6f7f14707d7bdf23aca3143b19", + "skills/manage-defects/references/vstack/protocols/quality-validation.md": "e53fca023d31b907d60019c68a5d823e0d89ae83d09e49e68c71bc9ec5a1303a", "skills/manage-issues/README.md": "867654dad179b039a3c058844f089939bfcf947096ba3ac1ce92a6015d9ac63a", "skills/manage-issues/SKILL.md": "36174c90206a6c3cf58a0b15ee32c07a4a4609aeb3563c939f34bb6b7b88d861", "skills/manage-issues/references/docs-alignment.md": "cd6c59a9488fa7f0353eb6b4726a243974f4019e7e0272d60015f46cdeeac210", @@ -101,19 +101,19 @@ "skills/manage-issues/references/parallelize.md": "16455c43dde811e86682cfd206192479bacfefd45e827da993a13fae3fcec1de", "skills/manage-issues/references/quality-gate.md": "43d3ca7e14041c4b49ca676d51be1ce5b7c9a13f6cfdf497aa1ab762d6988c37", "skills/manage-issues/references/stale.md": "f190ad3c0f3292418de9d86a5811d3c4de3c8feff6189267bbc126cd8a612004", - "skills/manage-issues/references/vstack/protocols/quality-validation.md": "522c097cb146a9fd016fd91facadb3faa13b0d6f7f14707d7bdf23aca3143b19", + "skills/manage-issues/references/vstack/protocols/quality-validation.md": "e53fca023d31b907d60019c68a5d823e0d89ae83d09e49e68c71bc9ec5a1303a", "skills/manage-issues/templates/issue-template.md": "ba25b30b6c1991b88f72146e9770f89a81959a1c92305bf2fe080880b9b245b0", "skills/manage-roadmap/SKILL.md": "759565e546f800a6126ce97a6afee94d7685219fd946ee86ddda5ab6027b1ae6", "skills/manage-roadmap/references/format.md": "67e052640c1bb6b6ff933de6ce7a9d386e460ec193226e29c7b561314d0f8d4e", "skills/manage-roadmap/references/parallel.md": "c38bd2a8c3228552852f15255a64113ad95ef1ec44214991cc71bb0508b48105", - "skills/manage-roadmap/references/vstack/protocols/quality-validation.md": "522c097cb146a9fd016fd91facadb3faa13b0d6f7f14707d7bdf23aca3143b19", + "skills/manage-roadmap/references/vstack/protocols/quality-validation.md": "e53fca023d31b907d60019c68a5d823e0d89ae83d09e49e68c71bc9ec5a1303a", "skills/manage-rules/SKILL.md": "8b68d3dc576ba3cc31efda6ce7e99ab3fbba2e9406bc91c1dc93a35faa390c6f", - "skills/manage-rules/references/vstack/protocols/quality-validation.md": "522c097cb146a9fd016fd91facadb3faa13b0d6f7f14707d7bdf23aca3143b19", + "skills/manage-rules/references/vstack/protocols/quality-validation.md": "e53fca023d31b907d60019c68a5d823e0d89ae83d09e49e68c71bc9ec5a1303a", "skills/manage-skills/SKILL.md": "05bf1e174bd54cd4561d7dfd3c2278c48278a044fd755c27e12612064e255c3a", - "skills/manage-skills/references/vstack/protocols/quality-validation.md": "522c097cb146a9fd016fd91facadb3faa13b0d6f7f14707d7bdf23aca3143b19", + "skills/manage-skills/references/vstack/protocols/quality-validation.md": "e53fca023d31b907d60019c68a5d823e0d89ae83d09e49e68c71bc9ec5a1303a", "skills/manage-vision/SKILL.md": "d1c3fa2e276dd7939b91b25fc840986a07aa9184ddf51645aa2f71549f7cc647", "skills/manage-vision/references/format.md": "d9a2ca5b92f8194f7cab5ad4fdd8722d72888e0eeb4875503fec9d3d5d1ff3c4", - "skills/manage-vision/references/vstack/protocols/quality-validation.md": "522c097cb146a9fd016fd91facadb3faa13b0d6f7f14707d7bdf23aca3143b19", + "skills/manage-vision/references/vstack/protocols/quality-validation.md": "e53fca023d31b907d60019c68a5d823e0d89ae83d09e49e68c71bc9ec5a1303a", "skills/plan-issues/SKILL.md": "dedf1efea18b847278e5c6530ec14d5396d150780d6c81f059e7c3fd81853f35", "skills/plan-issues/references/vstack/capabilities/agent-tooling-review/REFERENCE.md": "7b727fbe19c53878de4ba729e1bacea2d0a953444050232d35db2ad7b673fcc3", "skills/plan-issues/references/vstack/capabilities/compliance-review/REFERENCE.md": "3532a9686e5d52da0a82850d15b284b6acd82b0da8506c3679e17c8924f68694", @@ -123,21 +123,21 @@ "skills/plan-issues/references/vstack/capabilities/compliance-review/references/privacy.md": "8a1aa4a96b0cf786c0099e76f4b46d255ee5135dcf1caf53b123fec7e4e11a8d", "skills/plan-issues/references/vstack/capabilities/infrastructure-costs/REFERENCE.md": "407b208fd7f2d9c1a611197154d9594a23d0506d637e298aa543a24bcb9fafd0", "skills/plan-issues/references/vstack/capabilities/infrastructure-review/REFERENCE.md": "17bd7a5b3d341d5b6ad08f917efbca69f3901b1fba545b75d2b4909cf831e4f8", - "skills/plan-issues/references/vstack/protocols/quality-validation.md": "522c097cb146a9fd016fd91facadb3faa13b0d6f7f14707d7bdf23aca3143b19", + "skills/plan-issues/references/vstack/protocols/quality-validation.md": "e53fca023d31b907d60019c68a5d823e0d89ae83d09e49e68c71bc9ec5a1303a", "skills/plan-work/SKILL.md": "4cc59fa808209d47d636ad1c65890d46e7b45729d7a211a8bc83ff5df3314886", - "skills/plan-work/references/vstack/protocols/quality-validation.md": "522c097cb146a9fd016fd91facadb3faa13b0d6f7f14707d7bdf23aca3143b19", + "skills/plan-work/references/vstack/protocols/quality-validation.md": "e53fca023d31b907d60019c68a5d823e0d89ae83d09e49e68c71bc9ec5a1303a", "skills/review-ui/SKILL.md": "b9e18bd0a294238486119a1d302a0d5ab06f4f77d5f5d37b77980ec68e6a580c", "skills/review-ui/references/vstack/capabilities/ui-accessibility/REFERENCE.md": "f265d321d975a0319ab5455b7fefd74e4852de63b7bd14d1f9d044c78371c25b", "skills/review-ui/references/vstack/capabilities/web-performance/REFERENCE.md": "52fb4ebb9e024fa6184da9187f3311d17a53c40691a63f5b2b6c471729f760ff", "skills/review-ui/references/vstack/capabilities/web-performance/references/eval-audits.md": "d94253fb08c7059329022026843088c46c23a8615d134ace36eea4cb61fa9a6c", "skills/review-ui/references/vstack/capabilities/web-performance/references/optimization-playbook.md": "0acdedcb0496f4926bee2d23a2294a152a8107c88c5e9f934afa8334e74fde13", - "skills/review-ui/references/vstack/protocols/quality-validation.md": "522c097cb146a9fd016fd91facadb3faa13b0d6f7f14707d7bdf23aca3143b19", - "skills/vllnt-collaboration-principles/SKILL.md": "a2540f13682fbe29defdaafc8c14221ea05f4cba60b0e6c2c2fd595fb55489f1", + "skills/review-ui/references/vstack/protocols/quality-validation.md": "e53fca023d31b907d60019c68a5d823e0d89ae83d09e49e68c71bc9ec5a1303a", + "skills/vllnt-collaboration-principles/SKILL.md": "d706dd9d89a602c9f70803e6b37714b1b68b8f3105f6f6b8cc3ad91cf7b3a478", "skills/vllnt-orchestration-principles/SKILL.md": "16d0df9b250499fa1f5f45e616bb5d126d0ae5fe5901548a476f07e5e94cb3a1", "skills/vllnt-thinking-principles/SKILL.md": "3d1229f311f9d58ec3335a35e9019afda8cf59dff5c20730a42593c17b40b0b9" }, "upstream": { - "commit": "14b8ad3dbba8ea820478d3ea2d379c2863de56d9", + "commit": "472c216f2f043f0add1f83540cc46ea53d20a7cd", "repository": "https://github.com/vllnt/skills.git" } } diff --git a/plugins/codex/plugin.json b/plugins/codex/plugin.json index 4fd89f6..b039975 100644 --- a/plugins/codex/plugin.json +++ b/plugins/codex/plugin.json @@ -6,5 +6,5 @@ "description": "Vstack portable workflows and engineering principles.", "license": "MIT", "name": "vstack", - "version": "0.1.0-dev.4" + "version": "0.1.0-dev.5" } diff --git a/plugins/codex/skills/build-landing-page/references/vstack/protocols/quality-validation.md b/plugins/codex/skills/build-landing-page/references/vstack/protocols/quality-validation.md index e038fe9..9a0d797 100644 --- a/plugins/codex/skills/build-landing-page/references/vstack/protocols/quality-validation.md +++ b/plugins/codex/skills/build-landing-page/references/vstack/protocols/quality-validation.md @@ -15,9 +15,9 @@ 1. Reuse the caller's validation contract. Record candidate, mode, required criteria, evidence or checks, unacceptable outcomes, and useful review perspectives from the request, applicable instructions, principles, and owning workflow. 2. Have the producer self-assess each criterion as pass, fail, or unverified with evidence. Return known defects to the caller before independent review. A score may summarize a defined rubric but cannot replace required proof. -3. For substantive work, use distinct subagents for review of correctness, completeness, and preserved behavior, and critique of assumptions, necessity, simplicity, and alternatives. Give each the same contract, candidate, evidence, and bounded scope. Use direct checks for mechanical work; without subagents, assess sequentially and report unavailable independence. If independent review is required but unavailable, return `BLOCKED`. +3. For substantive work, obtain review of correctness, completeness, and preserved behavior, and critique of assumptions, necessity, simplicity, and alternatives from reviewers independent of the producer. One reviewer may cover both; add reviewers only for required separation or non-overlapping parallel scopes. Supply scoped criteria, the candidate or diff, and current evidence. Assign checks within each reviewer's tools and authority; return missing required evidence to the caller. Use direct checks for mechanical work. Without subagents, assess sequentially and report missing independence; return `BLOCKED` if required independent review is unavailable. 4. Collect verdicts and findings with criterion, location or scenario, evidence, impact, smallest remedy, and acceptance check. Deduplicate them into required fixes, selected improvements, optional suggestions, and justified rejections. Resolve disagreements with evidence; a disputed required criterion remains open. -5. Return actionable fixes to the caller. After every authorized revision, rerun invalidated checks and request fresh verdicts from affected reviewers and critics. Reuse only evidence and acceptance unaffected by the current candidate. +5. Return fixes to the caller. After authorized revisions, send affected reviewers the reason, revised material, and invalidated evidence. Rerun invalidated checks and renew affected verdicts; retain only evidence and acceptance unaffected by changes to the candidate, inputs, or relevant environment. 6. Return `PASS` only when every required criterion has proof, required perspectives accept their scopes, and no required finding remains. Otherwise return `REVISE` with fixes for the caller to implement and resubmit, or `BLOCKED` with the unmet criterion, cause, options, recommendation, and consequence. On unchanged evidence, change approach rather than retrying or lowering criteria. ## Pitfalls diff --git a/plugins/codex/skills/build-project/references/vstack/protocols/quality-validation.md b/plugins/codex/skills/build-project/references/vstack/protocols/quality-validation.md index e038fe9..9a0d797 100644 --- a/plugins/codex/skills/build-project/references/vstack/protocols/quality-validation.md +++ b/plugins/codex/skills/build-project/references/vstack/protocols/quality-validation.md @@ -15,9 +15,9 @@ 1. Reuse the caller's validation contract. Record candidate, mode, required criteria, evidence or checks, unacceptable outcomes, and useful review perspectives from the request, applicable instructions, principles, and owning workflow. 2. Have the producer self-assess each criterion as pass, fail, or unverified with evidence. Return known defects to the caller before independent review. A score may summarize a defined rubric but cannot replace required proof. -3. For substantive work, use distinct subagents for review of correctness, completeness, and preserved behavior, and critique of assumptions, necessity, simplicity, and alternatives. Give each the same contract, candidate, evidence, and bounded scope. Use direct checks for mechanical work; without subagents, assess sequentially and report unavailable independence. If independent review is required but unavailable, return `BLOCKED`. +3. For substantive work, obtain review of correctness, completeness, and preserved behavior, and critique of assumptions, necessity, simplicity, and alternatives from reviewers independent of the producer. One reviewer may cover both; add reviewers only for required separation or non-overlapping parallel scopes. Supply scoped criteria, the candidate or diff, and current evidence. Assign checks within each reviewer's tools and authority; return missing required evidence to the caller. Use direct checks for mechanical work. Without subagents, assess sequentially and report missing independence; return `BLOCKED` if required independent review is unavailable. 4. Collect verdicts and findings with criterion, location or scenario, evidence, impact, smallest remedy, and acceptance check. Deduplicate them into required fixes, selected improvements, optional suggestions, and justified rejections. Resolve disagreements with evidence; a disputed required criterion remains open. -5. Return actionable fixes to the caller. After every authorized revision, rerun invalidated checks and request fresh verdicts from affected reviewers and critics. Reuse only evidence and acceptance unaffected by the current candidate. +5. Return fixes to the caller. After authorized revisions, send affected reviewers the reason, revised material, and invalidated evidence. Rerun invalidated checks and renew affected verdicts; retain only evidence and acceptance unaffected by changes to the candidate, inputs, or relevant environment. 6. Return `PASS` only when every required criterion has proof, required perspectives accept their scopes, and no required finding remains. Otherwise return `REVISE` with fixes for the caller to implement and resubmit, or `BLOCKED` with the unmet criterion, cause, options, recommendation, and consequence. On unchanged evidence, change approach rather than retrying or lowering criteria. ## Pitfalls diff --git a/plugins/codex/skills/build-prototype/references/vstack/protocols/quality-validation.md b/plugins/codex/skills/build-prototype/references/vstack/protocols/quality-validation.md index e038fe9..9a0d797 100644 --- a/plugins/codex/skills/build-prototype/references/vstack/protocols/quality-validation.md +++ b/plugins/codex/skills/build-prototype/references/vstack/protocols/quality-validation.md @@ -15,9 +15,9 @@ 1. Reuse the caller's validation contract. Record candidate, mode, required criteria, evidence or checks, unacceptable outcomes, and useful review perspectives from the request, applicable instructions, principles, and owning workflow. 2. Have the producer self-assess each criterion as pass, fail, or unverified with evidence. Return known defects to the caller before independent review. A score may summarize a defined rubric but cannot replace required proof. -3. For substantive work, use distinct subagents for review of correctness, completeness, and preserved behavior, and critique of assumptions, necessity, simplicity, and alternatives. Give each the same contract, candidate, evidence, and bounded scope. Use direct checks for mechanical work; without subagents, assess sequentially and report unavailable independence. If independent review is required but unavailable, return `BLOCKED`. +3. For substantive work, obtain review of correctness, completeness, and preserved behavior, and critique of assumptions, necessity, simplicity, and alternatives from reviewers independent of the producer. One reviewer may cover both; add reviewers only for required separation or non-overlapping parallel scopes. Supply scoped criteria, the candidate or diff, and current evidence. Assign checks within each reviewer's tools and authority; return missing required evidence to the caller. Use direct checks for mechanical work. Without subagents, assess sequentially and report missing independence; return `BLOCKED` if required independent review is unavailable. 4. Collect verdicts and findings with criterion, location or scenario, evidence, impact, smallest remedy, and acceptance check. Deduplicate them into required fixes, selected improvements, optional suggestions, and justified rejections. Resolve disagreements with evidence; a disputed required criterion remains open. -5. Return actionable fixes to the caller. After every authorized revision, rerun invalidated checks and request fresh verdicts from affected reviewers and critics. Reuse only evidence and acceptance unaffected by the current candidate. +5. Return fixes to the caller. After authorized revisions, send affected reviewers the reason, revised material, and invalidated evidence. Rerun invalidated checks and renew affected verdicts; retain only evidence and acceptance unaffected by changes to the candidate, inputs, or relevant environment. 6. Return `PASS` only when every required criterion has proof, required perspectives accept their scopes, and no required finding remains. Otherwise return `REVISE` with fixes for the caller to implement and resubmit, or `BLOCKED` with the unmet criterion, cause, options, recommendation, and consequence. On unchanged evidence, change approach rather than retrying or lowering criteria. ## Pitfalls diff --git a/plugins/codex/skills/deliver-issue/references/vstack/protocols/quality-validation.md b/plugins/codex/skills/deliver-issue/references/vstack/protocols/quality-validation.md index e038fe9..9a0d797 100644 --- a/plugins/codex/skills/deliver-issue/references/vstack/protocols/quality-validation.md +++ b/plugins/codex/skills/deliver-issue/references/vstack/protocols/quality-validation.md @@ -15,9 +15,9 @@ 1. Reuse the caller's validation contract. Record candidate, mode, required criteria, evidence or checks, unacceptable outcomes, and useful review perspectives from the request, applicable instructions, principles, and owning workflow. 2. Have the producer self-assess each criterion as pass, fail, or unverified with evidence. Return known defects to the caller before independent review. A score may summarize a defined rubric but cannot replace required proof. -3. For substantive work, use distinct subagents for review of correctness, completeness, and preserved behavior, and critique of assumptions, necessity, simplicity, and alternatives. Give each the same contract, candidate, evidence, and bounded scope. Use direct checks for mechanical work; without subagents, assess sequentially and report unavailable independence. If independent review is required but unavailable, return `BLOCKED`. +3. For substantive work, obtain review of correctness, completeness, and preserved behavior, and critique of assumptions, necessity, simplicity, and alternatives from reviewers independent of the producer. One reviewer may cover both; add reviewers only for required separation or non-overlapping parallel scopes. Supply scoped criteria, the candidate or diff, and current evidence. Assign checks within each reviewer's tools and authority; return missing required evidence to the caller. Use direct checks for mechanical work. Without subagents, assess sequentially and report missing independence; return `BLOCKED` if required independent review is unavailable. 4. Collect verdicts and findings with criterion, location or scenario, evidence, impact, smallest remedy, and acceptance check. Deduplicate them into required fixes, selected improvements, optional suggestions, and justified rejections. Resolve disagreements with evidence; a disputed required criterion remains open. -5. Return actionable fixes to the caller. After every authorized revision, rerun invalidated checks and request fresh verdicts from affected reviewers and critics. Reuse only evidence and acceptance unaffected by the current candidate. +5. Return fixes to the caller. After authorized revisions, send affected reviewers the reason, revised material, and invalidated evidence. Rerun invalidated checks and renew affected verdicts; retain only evidence and acceptance unaffected by changes to the candidate, inputs, or relevant environment. 6. Return `PASS` only when every required criterion has proof, required perspectives accept their scopes, and no required finding remains. Otherwise return `REVISE` with fixes for the caller to implement and resubmit, or `BLOCKED` with the unmet criterion, cause, options, recommendation, and consequence. On unchanged evidence, change approach rather than retrying or lowering criteria. ## Pitfalls diff --git a/plugins/codex/skills/deliver-pull-request/references/vstack/protocols/quality-validation.md b/plugins/codex/skills/deliver-pull-request/references/vstack/protocols/quality-validation.md index e038fe9..9a0d797 100644 --- a/plugins/codex/skills/deliver-pull-request/references/vstack/protocols/quality-validation.md +++ b/plugins/codex/skills/deliver-pull-request/references/vstack/protocols/quality-validation.md @@ -15,9 +15,9 @@ 1. Reuse the caller's validation contract. Record candidate, mode, required criteria, evidence or checks, unacceptable outcomes, and useful review perspectives from the request, applicable instructions, principles, and owning workflow. 2. Have the producer self-assess each criterion as pass, fail, or unverified with evidence. Return known defects to the caller before independent review. A score may summarize a defined rubric but cannot replace required proof. -3. For substantive work, use distinct subagents for review of correctness, completeness, and preserved behavior, and critique of assumptions, necessity, simplicity, and alternatives. Give each the same contract, candidate, evidence, and bounded scope. Use direct checks for mechanical work; without subagents, assess sequentially and report unavailable independence. If independent review is required but unavailable, return `BLOCKED`. +3. For substantive work, obtain review of correctness, completeness, and preserved behavior, and critique of assumptions, necessity, simplicity, and alternatives from reviewers independent of the producer. One reviewer may cover both; add reviewers only for required separation or non-overlapping parallel scopes. Supply scoped criteria, the candidate or diff, and current evidence. Assign checks within each reviewer's tools and authority; return missing required evidence to the caller. Use direct checks for mechanical work. Without subagents, assess sequentially and report missing independence; return `BLOCKED` if required independent review is unavailable. 4. Collect verdicts and findings with criterion, location or scenario, evidence, impact, smallest remedy, and acceptance check. Deduplicate them into required fixes, selected improvements, optional suggestions, and justified rejections. Resolve disagreements with evidence; a disputed required criterion remains open. -5. Return actionable fixes to the caller. After every authorized revision, rerun invalidated checks and request fresh verdicts from affected reviewers and critics. Reuse only evidence and acceptance unaffected by the current candidate. +5. Return fixes to the caller. After authorized revisions, send affected reviewers the reason, revised material, and invalidated evidence. Rerun invalidated checks and renew affected verdicts; retain only evidence and acceptance unaffected by changes to the candidate, inputs, or relevant environment. 6. Return `PASS` only when every required criterion has proof, required perspectives accept their scopes, and no required finding remains. Otherwise return `REVISE` with fixes for the caller to implement and resubmit, or `BLOCKED` with the unmet criterion, cause, options, recommendation, and consequence. On unchanged evidence, change approach rather than retrying or lowering criteria. ## Pitfalls diff --git a/plugins/codex/skills/explain-subject/references/vstack/protocols/quality-validation.md b/plugins/codex/skills/explain-subject/references/vstack/protocols/quality-validation.md index e038fe9..9a0d797 100644 --- a/plugins/codex/skills/explain-subject/references/vstack/protocols/quality-validation.md +++ b/plugins/codex/skills/explain-subject/references/vstack/protocols/quality-validation.md @@ -15,9 +15,9 @@ 1. Reuse the caller's validation contract. Record candidate, mode, required criteria, evidence or checks, unacceptable outcomes, and useful review perspectives from the request, applicable instructions, principles, and owning workflow. 2. Have the producer self-assess each criterion as pass, fail, or unverified with evidence. Return known defects to the caller before independent review. A score may summarize a defined rubric but cannot replace required proof. -3. For substantive work, use distinct subagents for review of correctness, completeness, and preserved behavior, and critique of assumptions, necessity, simplicity, and alternatives. Give each the same contract, candidate, evidence, and bounded scope. Use direct checks for mechanical work; without subagents, assess sequentially and report unavailable independence. If independent review is required but unavailable, return `BLOCKED`. +3. For substantive work, obtain review of correctness, completeness, and preserved behavior, and critique of assumptions, necessity, simplicity, and alternatives from reviewers independent of the producer. One reviewer may cover both; add reviewers only for required separation or non-overlapping parallel scopes. Supply scoped criteria, the candidate or diff, and current evidence. Assign checks within each reviewer's tools and authority; return missing required evidence to the caller. Use direct checks for mechanical work. Without subagents, assess sequentially and report missing independence; return `BLOCKED` if required independent review is unavailable. 4. Collect verdicts and findings with criterion, location or scenario, evidence, impact, smallest remedy, and acceptance check. Deduplicate them into required fixes, selected improvements, optional suggestions, and justified rejections. Resolve disagreements with evidence; a disputed required criterion remains open. -5. Return actionable fixes to the caller. After every authorized revision, rerun invalidated checks and request fresh verdicts from affected reviewers and critics. Reuse only evidence and acceptance unaffected by the current candidate. +5. Return fixes to the caller. After authorized revisions, send affected reviewers the reason, revised material, and invalidated evidence. Rerun invalidated checks and renew affected verdicts; retain only evidence and acceptance unaffected by changes to the candidate, inputs, or relevant environment. 6. Return `PASS` only when every required criterion has proof, required perspectives accept their scopes, and no required finding remains. Otherwise return `REVISE` with fixes for the caller to implement and resubmit, or `BLOCKED` with the unmet criterion, cause, options, recommendation, and consequence. On unchanged evidence, change approach rather than retrying or lowering criteria. ## Pitfalls diff --git a/plugins/codex/skills/explore-decisions/references/vstack/protocols/quality-validation.md b/plugins/codex/skills/explore-decisions/references/vstack/protocols/quality-validation.md index e038fe9..9a0d797 100644 --- a/plugins/codex/skills/explore-decisions/references/vstack/protocols/quality-validation.md +++ b/plugins/codex/skills/explore-decisions/references/vstack/protocols/quality-validation.md @@ -15,9 +15,9 @@ 1. Reuse the caller's validation contract. Record candidate, mode, required criteria, evidence or checks, unacceptable outcomes, and useful review perspectives from the request, applicable instructions, principles, and owning workflow. 2. Have the producer self-assess each criterion as pass, fail, or unverified with evidence. Return known defects to the caller before independent review. A score may summarize a defined rubric but cannot replace required proof. -3. For substantive work, use distinct subagents for review of correctness, completeness, and preserved behavior, and critique of assumptions, necessity, simplicity, and alternatives. Give each the same contract, candidate, evidence, and bounded scope. Use direct checks for mechanical work; without subagents, assess sequentially and report unavailable independence. If independent review is required but unavailable, return `BLOCKED`. +3. For substantive work, obtain review of correctness, completeness, and preserved behavior, and critique of assumptions, necessity, simplicity, and alternatives from reviewers independent of the producer. One reviewer may cover both; add reviewers only for required separation or non-overlapping parallel scopes. Supply scoped criteria, the candidate or diff, and current evidence. Assign checks within each reviewer's tools and authority; return missing required evidence to the caller. Use direct checks for mechanical work. Without subagents, assess sequentially and report missing independence; return `BLOCKED` if required independent review is unavailable. 4. Collect verdicts and findings with criterion, location or scenario, evidence, impact, smallest remedy, and acceptance check. Deduplicate them into required fixes, selected improvements, optional suggestions, and justified rejections. Resolve disagreements with evidence; a disputed required criterion remains open. -5. Return actionable fixes to the caller. After every authorized revision, rerun invalidated checks and request fresh verdicts from affected reviewers and critics. Reuse only evidence and acceptance unaffected by the current candidate. +5. Return fixes to the caller. After authorized revisions, send affected reviewers the reason, revised material, and invalidated evidence. Rerun invalidated checks and renew affected verdicts; retain only evidence and acceptance unaffected by changes to the candidate, inputs, or relevant environment. 6. Return `PASS` only when every required criterion has proof, required perspectives accept their scopes, and no required finding remains. Otherwise return `REVISE` with fixes for the caller to implement and resubmit, or `BLOCKED` with the unmet criterion, cause, options, recommendation, and consequence. On unchanged evidence, change approach rather than retrying or lowering criteria. ## Pitfalls diff --git a/plugins/codex/skills/improve-code/references/vstack/protocols/quality-validation.md b/plugins/codex/skills/improve-code/references/vstack/protocols/quality-validation.md index e038fe9..9a0d797 100644 --- a/plugins/codex/skills/improve-code/references/vstack/protocols/quality-validation.md +++ b/plugins/codex/skills/improve-code/references/vstack/protocols/quality-validation.md @@ -15,9 +15,9 @@ 1. Reuse the caller's validation contract. Record candidate, mode, required criteria, evidence or checks, unacceptable outcomes, and useful review perspectives from the request, applicable instructions, principles, and owning workflow. 2. Have the producer self-assess each criterion as pass, fail, or unverified with evidence. Return known defects to the caller before independent review. A score may summarize a defined rubric but cannot replace required proof. -3. For substantive work, use distinct subagents for review of correctness, completeness, and preserved behavior, and critique of assumptions, necessity, simplicity, and alternatives. Give each the same contract, candidate, evidence, and bounded scope. Use direct checks for mechanical work; without subagents, assess sequentially and report unavailable independence. If independent review is required but unavailable, return `BLOCKED`. +3. For substantive work, obtain review of correctness, completeness, and preserved behavior, and critique of assumptions, necessity, simplicity, and alternatives from reviewers independent of the producer. One reviewer may cover both; add reviewers only for required separation or non-overlapping parallel scopes. Supply scoped criteria, the candidate or diff, and current evidence. Assign checks within each reviewer's tools and authority; return missing required evidence to the caller. Use direct checks for mechanical work. Without subagents, assess sequentially and report missing independence; return `BLOCKED` if required independent review is unavailable. 4. Collect verdicts and findings with criterion, location or scenario, evidence, impact, smallest remedy, and acceptance check. Deduplicate them into required fixes, selected improvements, optional suggestions, and justified rejections. Resolve disagreements with evidence; a disputed required criterion remains open. -5. Return actionable fixes to the caller. After every authorized revision, rerun invalidated checks and request fresh verdicts from affected reviewers and critics. Reuse only evidence and acceptance unaffected by the current candidate. +5. Return fixes to the caller. After authorized revisions, send affected reviewers the reason, revised material, and invalidated evidence. Rerun invalidated checks and renew affected verdicts; retain only evidence and acceptance unaffected by changes to the candidate, inputs, or relevant environment. 6. Return `PASS` only when every required criterion has proof, required perspectives accept their scopes, and no required finding remains. Otherwise return `REVISE` with fixes for the caller to implement and resubmit, or `BLOCKED` with the unmet criterion, cause, options, recommendation, and consequence. On unchanged evidence, change approach rather than retrying or lowering criteria. ## Pitfalls diff --git a/plugins/codex/skills/improve-project/references/vstack/protocols/quality-validation.md b/plugins/codex/skills/improve-project/references/vstack/protocols/quality-validation.md index e038fe9..9a0d797 100644 --- a/plugins/codex/skills/improve-project/references/vstack/protocols/quality-validation.md +++ b/plugins/codex/skills/improve-project/references/vstack/protocols/quality-validation.md @@ -15,9 +15,9 @@ 1. Reuse the caller's validation contract. Record candidate, mode, required criteria, evidence or checks, unacceptable outcomes, and useful review perspectives from the request, applicable instructions, principles, and owning workflow. 2. Have the producer self-assess each criterion as pass, fail, or unverified with evidence. Return known defects to the caller before independent review. A score may summarize a defined rubric but cannot replace required proof. -3. For substantive work, use distinct subagents for review of correctness, completeness, and preserved behavior, and critique of assumptions, necessity, simplicity, and alternatives. Give each the same contract, candidate, evidence, and bounded scope. Use direct checks for mechanical work; without subagents, assess sequentially and report unavailable independence. If independent review is required but unavailable, return `BLOCKED`. +3. For substantive work, obtain review of correctness, completeness, and preserved behavior, and critique of assumptions, necessity, simplicity, and alternatives from reviewers independent of the producer. One reviewer may cover both; add reviewers only for required separation or non-overlapping parallel scopes. Supply scoped criteria, the candidate or diff, and current evidence. Assign checks within each reviewer's tools and authority; return missing required evidence to the caller. Use direct checks for mechanical work. Without subagents, assess sequentially and report missing independence; return `BLOCKED` if required independent review is unavailable. 4. Collect verdicts and findings with criterion, location or scenario, evidence, impact, smallest remedy, and acceptance check. Deduplicate them into required fixes, selected improvements, optional suggestions, and justified rejections. Resolve disagreements with evidence; a disputed required criterion remains open. -5. Return actionable fixes to the caller. After every authorized revision, rerun invalidated checks and request fresh verdicts from affected reviewers and critics. Reuse only evidence and acceptance unaffected by the current candidate. +5. Return fixes to the caller. After authorized revisions, send affected reviewers the reason, revised material, and invalidated evidence. Rerun invalidated checks and renew affected verdicts; retain only evidence and acceptance unaffected by changes to the candidate, inputs, or relevant environment. 6. Return `PASS` only when every required criterion has proof, required perspectives accept their scopes, and no required finding remains. Otherwise return `REVISE` with fixes for the caller to implement and resubmit, or `BLOCKED` with the unmet criterion, cause, options, recommendation, and consequence. On unchanged evidence, change approach rather than retrying or lowering criteria. ## Pitfalls diff --git a/plugins/codex/skills/improve-ui/references/vstack/protocols/quality-validation.md b/plugins/codex/skills/improve-ui/references/vstack/protocols/quality-validation.md index e038fe9..9a0d797 100644 --- a/plugins/codex/skills/improve-ui/references/vstack/protocols/quality-validation.md +++ b/plugins/codex/skills/improve-ui/references/vstack/protocols/quality-validation.md @@ -15,9 +15,9 @@ 1. Reuse the caller's validation contract. Record candidate, mode, required criteria, evidence or checks, unacceptable outcomes, and useful review perspectives from the request, applicable instructions, principles, and owning workflow. 2. Have the producer self-assess each criterion as pass, fail, or unverified with evidence. Return known defects to the caller before independent review. A score may summarize a defined rubric but cannot replace required proof. -3. For substantive work, use distinct subagents for review of correctness, completeness, and preserved behavior, and critique of assumptions, necessity, simplicity, and alternatives. Give each the same contract, candidate, evidence, and bounded scope. Use direct checks for mechanical work; without subagents, assess sequentially and report unavailable independence. If independent review is required but unavailable, return `BLOCKED`. +3. For substantive work, obtain review of correctness, completeness, and preserved behavior, and critique of assumptions, necessity, simplicity, and alternatives from reviewers independent of the producer. One reviewer may cover both; add reviewers only for required separation or non-overlapping parallel scopes. Supply scoped criteria, the candidate or diff, and current evidence. Assign checks within each reviewer's tools and authority; return missing required evidence to the caller. Use direct checks for mechanical work. Without subagents, assess sequentially and report missing independence; return `BLOCKED` if required independent review is unavailable. 4. Collect verdicts and findings with criterion, location or scenario, evidence, impact, smallest remedy, and acceptance check. Deduplicate them into required fixes, selected improvements, optional suggestions, and justified rejections. Resolve disagreements with evidence; a disputed required criterion remains open. -5. Return actionable fixes to the caller. After every authorized revision, rerun invalidated checks and request fresh verdicts from affected reviewers and critics. Reuse only evidence and acceptance unaffected by the current candidate. +5. Return fixes to the caller. After authorized revisions, send affected reviewers the reason, revised material, and invalidated evidence. Rerun invalidated checks and renew affected verdicts; retain only evidence and acceptance unaffected by changes to the candidate, inputs, or relevant environment. 6. Return `PASS` only when every required criterion has proof, required perspectives accept their scopes, and no required finding remains. Otherwise return `REVISE` with fixes for the caller to implement and resubmit, or `BLOCKED` with the unmet criterion, cause, options, recommendation, and consequence. On unchanged evidence, change approach rather than retrying or lowering criteria. ## Pitfalls diff --git a/plugins/codex/skills/manage-defects/references/vstack/protocols/quality-validation.md b/plugins/codex/skills/manage-defects/references/vstack/protocols/quality-validation.md index e038fe9..9a0d797 100644 --- a/plugins/codex/skills/manage-defects/references/vstack/protocols/quality-validation.md +++ b/plugins/codex/skills/manage-defects/references/vstack/protocols/quality-validation.md @@ -15,9 +15,9 @@ 1. Reuse the caller's validation contract. Record candidate, mode, required criteria, evidence or checks, unacceptable outcomes, and useful review perspectives from the request, applicable instructions, principles, and owning workflow. 2. Have the producer self-assess each criterion as pass, fail, or unverified with evidence. Return known defects to the caller before independent review. A score may summarize a defined rubric but cannot replace required proof. -3. For substantive work, use distinct subagents for review of correctness, completeness, and preserved behavior, and critique of assumptions, necessity, simplicity, and alternatives. Give each the same contract, candidate, evidence, and bounded scope. Use direct checks for mechanical work; without subagents, assess sequentially and report unavailable independence. If independent review is required but unavailable, return `BLOCKED`. +3. For substantive work, obtain review of correctness, completeness, and preserved behavior, and critique of assumptions, necessity, simplicity, and alternatives from reviewers independent of the producer. One reviewer may cover both; add reviewers only for required separation or non-overlapping parallel scopes. Supply scoped criteria, the candidate or diff, and current evidence. Assign checks within each reviewer's tools and authority; return missing required evidence to the caller. Use direct checks for mechanical work. Without subagents, assess sequentially and report missing independence; return `BLOCKED` if required independent review is unavailable. 4. Collect verdicts and findings with criterion, location or scenario, evidence, impact, smallest remedy, and acceptance check. Deduplicate them into required fixes, selected improvements, optional suggestions, and justified rejections. Resolve disagreements with evidence; a disputed required criterion remains open. -5. Return actionable fixes to the caller. After every authorized revision, rerun invalidated checks and request fresh verdicts from affected reviewers and critics. Reuse only evidence and acceptance unaffected by the current candidate. +5. Return fixes to the caller. After authorized revisions, send affected reviewers the reason, revised material, and invalidated evidence. Rerun invalidated checks and renew affected verdicts; retain only evidence and acceptance unaffected by changes to the candidate, inputs, or relevant environment. 6. Return `PASS` only when every required criterion has proof, required perspectives accept their scopes, and no required finding remains. Otherwise return `REVISE` with fixes for the caller to implement and resubmit, or `BLOCKED` with the unmet criterion, cause, options, recommendation, and consequence. On unchanged evidence, change approach rather than retrying or lowering criteria. ## Pitfalls diff --git a/plugins/codex/skills/manage-issues/references/vstack/protocols/quality-validation.md b/plugins/codex/skills/manage-issues/references/vstack/protocols/quality-validation.md index e038fe9..9a0d797 100644 --- a/plugins/codex/skills/manage-issues/references/vstack/protocols/quality-validation.md +++ b/plugins/codex/skills/manage-issues/references/vstack/protocols/quality-validation.md @@ -15,9 +15,9 @@ 1. Reuse the caller's validation contract. Record candidate, mode, required criteria, evidence or checks, unacceptable outcomes, and useful review perspectives from the request, applicable instructions, principles, and owning workflow. 2. Have the producer self-assess each criterion as pass, fail, or unverified with evidence. Return known defects to the caller before independent review. A score may summarize a defined rubric but cannot replace required proof. -3. For substantive work, use distinct subagents for review of correctness, completeness, and preserved behavior, and critique of assumptions, necessity, simplicity, and alternatives. Give each the same contract, candidate, evidence, and bounded scope. Use direct checks for mechanical work; without subagents, assess sequentially and report unavailable independence. If independent review is required but unavailable, return `BLOCKED`. +3. For substantive work, obtain review of correctness, completeness, and preserved behavior, and critique of assumptions, necessity, simplicity, and alternatives from reviewers independent of the producer. One reviewer may cover both; add reviewers only for required separation or non-overlapping parallel scopes. Supply scoped criteria, the candidate or diff, and current evidence. Assign checks within each reviewer's tools and authority; return missing required evidence to the caller. Use direct checks for mechanical work. Without subagents, assess sequentially and report missing independence; return `BLOCKED` if required independent review is unavailable. 4. Collect verdicts and findings with criterion, location or scenario, evidence, impact, smallest remedy, and acceptance check. Deduplicate them into required fixes, selected improvements, optional suggestions, and justified rejections. Resolve disagreements with evidence; a disputed required criterion remains open. -5. Return actionable fixes to the caller. After every authorized revision, rerun invalidated checks and request fresh verdicts from affected reviewers and critics. Reuse only evidence and acceptance unaffected by the current candidate. +5. Return fixes to the caller. After authorized revisions, send affected reviewers the reason, revised material, and invalidated evidence. Rerun invalidated checks and renew affected verdicts; retain only evidence and acceptance unaffected by changes to the candidate, inputs, or relevant environment. 6. Return `PASS` only when every required criterion has proof, required perspectives accept their scopes, and no required finding remains. Otherwise return `REVISE` with fixes for the caller to implement and resubmit, or `BLOCKED` with the unmet criterion, cause, options, recommendation, and consequence. On unchanged evidence, change approach rather than retrying or lowering criteria. ## Pitfalls diff --git a/plugins/codex/skills/manage-roadmap/references/vstack/protocols/quality-validation.md b/plugins/codex/skills/manage-roadmap/references/vstack/protocols/quality-validation.md index e038fe9..9a0d797 100644 --- a/plugins/codex/skills/manage-roadmap/references/vstack/protocols/quality-validation.md +++ b/plugins/codex/skills/manage-roadmap/references/vstack/protocols/quality-validation.md @@ -15,9 +15,9 @@ 1. Reuse the caller's validation contract. Record candidate, mode, required criteria, evidence or checks, unacceptable outcomes, and useful review perspectives from the request, applicable instructions, principles, and owning workflow. 2. Have the producer self-assess each criterion as pass, fail, or unverified with evidence. Return known defects to the caller before independent review. A score may summarize a defined rubric but cannot replace required proof. -3. For substantive work, use distinct subagents for review of correctness, completeness, and preserved behavior, and critique of assumptions, necessity, simplicity, and alternatives. Give each the same contract, candidate, evidence, and bounded scope. Use direct checks for mechanical work; without subagents, assess sequentially and report unavailable independence. If independent review is required but unavailable, return `BLOCKED`. +3. For substantive work, obtain review of correctness, completeness, and preserved behavior, and critique of assumptions, necessity, simplicity, and alternatives from reviewers independent of the producer. One reviewer may cover both; add reviewers only for required separation or non-overlapping parallel scopes. Supply scoped criteria, the candidate or diff, and current evidence. Assign checks within each reviewer's tools and authority; return missing required evidence to the caller. Use direct checks for mechanical work. Without subagents, assess sequentially and report missing independence; return `BLOCKED` if required independent review is unavailable. 4. Collect verdicts and findings with criterion, location or scenario, evidence, impact, smallest remedy, and acceptance check. Deduplicate them into required fixes, selected improvements, optional suggestions, and justified rejections. Resolve disagreements with evidence; a disputed required criterion remains open. -5. Return actionable fixes to the caller. After every authorized revision, rerun invalidated checks and request fresh verdicts from affected reviewers and critics. Reuse only evidence and acceptance unaffected by the current candidate. +5. Return fixes to the caller. After authorized revisions, send affected reviewers the reason, revised material, and invalidated evidence. Rerun invalidated checks and renew affected verdicts; retain only evidence and acceptance unaffected by changes to the candidate, inputs, or relevant environment. 6. Return `PASS` only when every required criterion has proof, required perspectives accept their scopes, and no required finding remains. Otherwise return `REVISE` with fixes for the caller to implement and resubmit, or `BLOCKED` with the unmet criterion, cause, options, recommendation, and consequence. On unchanged evidence, change approach rather than retrying or lowering criteria. ## Pitfalls diff --git a/plugins/codex/skills/manage-rules/references/vstack/protocols/quality-validation.md b/plugins/codex/skills/manage-rules/references/vstack/protocols/quality-validation.md index e038fe9..9a0d797 100644 --- a/plugins/codex/skills/manage-rules/references/vstack/protocols/quality-validation.md +++ b/plugins/codex/skills/manage-rules/references/vstack/protocols/quality-validation.md @@ -15,9 +15,9 @@ 1. Reuse the caller's validation contract. Record candidate, mode, required criteria, evidence or checks, unacceptable outcomes, and useful review perspectives from the request, applicable instructions, principles, and owning workflow. 2. Have the producer self-assess each criterion as pass, fail, or unverified with evidence. Return known defects to the caller before independent review. A score may summarize a defined rubric but cannot replace required proof. -3. For substantive work, use distinct subagents for review of correctness, completeness, and preserved behavior, and critique of assumptions, necessity, simplicity, and alternatives. Give each the same contract, candidate, evidence, and bounded scope. Use direct checks for mechanical work; without subagents, assess sequentially and report unavailable independence. If independent review is required but unavailable, return `BLOCKED`. +3. For substantive work, obtain review of correctness, completeness, and preserved behavior, and critique of assumptions, necessity, simplicity, and alternatives from reviewers independent of the producer. One reviewer may cover both; add reviewers only for required separation or non-overlapping parallel scopes. Supply scoped criteria, the candidate or diff, and current evidence. Assign checks within each reviewer's tools and authority; return missing required evidence to the caller. Use direct checks for mechanical work. Without subagents, assess sequentially and report missing independence; return `BLOCKED` if required independent review is unavailable. 4. Collect verdicts and findings with criterion, location or scenario, evidence, impact, smallest remedy, and acceptance check. Deduplicate them into required fixes, selected improvements, optional suggestions, and justified rejections. Resolve disagreements with evidence; a disputed required criterion remains open. -5. Return actionable fixes to the caller. After every authorized revision, rerun invalidated checks and request fresh verdicts from affected reviewers and critics. Reuse only evidence and acceptance unaffected by the current candidate. +5. Return fixes to the caller. After authorized revisions, send affected reviewers the reason, revised material, and invalidated evidence. Rerun invalidated checks and renew affected verdicts; retain only evidence and acceptance unaffected by changes to the candidate, inputs, or relevant environment. 6. Return `PASS` only when every required criterion has proof, required perspectives accept their scopes, and no required finding remains. Otherwise return `REVISE` with fixes for the caller to implement and resubmit, or `BLOCKED` with the unmet criterion, cause, options, recommendation, and consequence. On unchanged evidence, change approach rather than retrying or lowering criteria. ## Pitfalls diff --git a/plugins/codex/skills/manage-skills/references/vstack/protocols/quality-validation.md b/plugins/codex/skills/manage-skills/references/vstack/protocols/quality-validation.md index e038fe9..9a0d797 100644 --- a/plugins/codex/skills/manage-skills/references/vstack/protocols/quality-validation.md +++ b/plugins/codex/skills/manage-skills/references/vstack/protocols/quality-validation.md @@ -15,9 +15,9 @@ 1. Reuse the caller's validation contract. Record candidate, mode, required criteria, evidence or checks, unacceptable outcomes, and useful review perspectives from the request, applicable instructions, principles, and owning workflow. 2. Have the producer self-assess each criterion as pass, fail, or unverified with evidence. Return known defects to the caller before independent review. A score may summarize a defined rubric but cannot replace required proof. -3. For substantive work, use distinct subagents for review of correctness, completeness, and preserved behavior, and critique of assumptions, necessity, simplicity, and alternatives. Give each the same contract, candidate, evidence, and bounded scope. Use direct checks for mechanical work; without subagents, assess sequentially and report unavailable independence. If independent review is required but unavailable, return `BLOCKED`. +3. For substantive work, obtain review of correctness, completeness, and preserved behavior, and critique of assumptions, necessity, simplicity, and alternatives from reviewers independent of the producer. One reviewer may cover both; add reviewers only for required separation or non-overlapping parallel scopes. Supply scoped criteria, the candidate or diff, and current evidence. Assign checks within each reviewer's tools and authority; return missing required evidence to the caller. Use direct checks for mechanical work. Without subagents, assess sequentially and report missing independence; return `BLOCKED` if required independent review is unavailable. 4. Collect verdicts and findings with criterion, location or scenario, evidence, impact, smallest remedy, and acceptance check. Deduplicate them into required fixes, selected improvements, optional suggestions, and justified rejections. Resolve disagreements with evidence; a disputed required criterion remains open. -5. Return actionable fixes to the caller. After every authorized revision, rerun invalidated checks and request fresh verdicts from affected reviewers and critics. Reuse only evidence and acceptance unaffected by the current candidate. +5. Return fixes to the caller. After authorized revisions, send affected reviewers the reason, revised material, and invalidated evidence. Rerun invalidated checks and renew affected verdicts; retain only evidence and acceptance unaffected by changes to the candidate, inputs, or relevant environment. 6. Return `PASS` only when every required criterion has proof, required perspectives accept their scopes, and no required finding remains. Otherwise return `REVISE` with fixes for the caller to implement and resubmit, or `BLOCKED` with the unmet criterion, cause, options, recommendation, and consequence. On unchanged evidence, change approach rather than retrying or lowering criteria. ## Pitfalls diff --git a/plugins/codex/skills/manage-vision/references/vstack/protocols/quality-validation.md b/plugins/codex/skills/manage-vision/references/vstack/protocols/quality-validation.md index e038fe9..9a0d797 100644 --- a/plugins/codex/skills/manage-vision/references/vstack/protocols/quality-validation.md +++ b/plugins/codex/skills/manage-vision/references/vstack/protocols/quality-validation.md @@ -15,9 +15,9 @@ 1. Reuse the caller's validation contract. Record candidate, mode, required criteria, evidence or checks, unacceptable outcomes, and useful review perspectives from the request, applicable instructions, principles, and owning workflow. 2. Have the producer self-assess each criterion as pass, fail, or unverified with evidence. Return known defects to the caller before independent review. A score may summarize a defined rubric but cannot replace required proof. -3. For substantive work, use distinct subagents for review of correctness, completeness, and preserved behavior, and critique of assumptions, necessity, simplicity, and alternatives. Give each the same contract, candidate, evidence, and bounded scope. Use direct checks for mechanical work; without subagents, assess sequentially and report unavailable independence. If independent review is required but unavailable, return `BLOCKED`. +3. For substantive work, obtain review of correctness, completeness, and preserved behavior, and critique of assumptions, necessity, simplicity, and alternatives from reviewers independent of the producer. One reviewer may cover both; add reviewers only for required separation or non-overlapping parallel scopes. Supply scoped criteria, the candidate or diff, and current evidence. Assign checks within each reviewer's tools and authority; return missing required evidence to the caller. Use direct checks for mechanical work. Without subagents, assess sequentially and report missing independence; return `BLOCKED` if required independent review is unavailable. 4. Collect verdicts and findings with criterion, location or scenario, evidence, impact, smallest remedy, and acceptance check. Deduplicate them into required fixes, selected improvements, optional suggestions, and justified rejections. Resolve disagreements with evidence; a disputed required criterion remains open. -5. Return actionable fixes to the caller. After every authorized revision, rerun invalidated checks and request fresh verdicts from affected reviewers and critics. Reuse only evidence and acceptance unaffected by the current candidate. +5. Return fixes to the caller. After authorized revisions, send affected reviewers the reason, revised material, and invalidated evidence. Rerun invalidated checks and renew affected verdicts; retain only evidence and acceptance unaffected by changes to the candidate, inputs, or relevant environment. 6. Return `PASS` only when every required criterion has proof, required perspectives accept their scopes, and no required finding remains. Otherwise return `REVISE` with fixes for the caller to implement and resubmit, or `BLOCKED` with the unmet criterion, cause, options, recommendation, and consequence. On unchanged evidence, change approach rather than retrying or lowering criteria. ## Pitfalls diff --git a/plugins/codex/skills/plan-issues/references/vstack/protocols/quality-validation.md b/plugins/codex/skills/plan-issues/references/vstack/protocols/quality-validation.md index e038fe9..9a0d797 100644 --- a/plugins/codex/skills/plan-issues/references/vstack/protocols/quality-validation.md +++ b/plugins/codex/skills/plan-issues/references/vstack/protocols/quality-validation.md @@ -15,9 +15,9 @@ 1. Reuse the caller's validation contract. Record candidate, mode, required criteria, evidence or checks, unacceptable outcomes, and useful review perspectives from the request, applicable instructions, principles, and owning workflow. 2. Have the producer self-assess each criterion as pass, fail, or unverified with evidence. Return known defects to the caller before independent review. A score may summarize a defined rubric but cannot replace required proof. -3. For substantive work, use distinct subagents for review of correctness, completeness, and preserved behavior, and critique of assumptions, necessity, simplicity, and alternatives. Give each the same contract, candidate, evidence, and bounded scope. Use direct checks for mechanical work; without subagents, assess sequentially and report unavailable independence. If independent review is required but unavailable, return `BLOCKED`. +3. For substantive work, obtain review of correctness, completeness, and preserved behavior, and critique of assumptions, necessity, simplicity, and alternatives from reviewers independent of the producer. One reviewer may cover both; add reviewers only for required separation or non-overlapping parallel scopes. Supply scoped criteria, the candidate or diff, and current evidence. Assign checks within each reviewer's tools and authority; return missing required evidence to the caller. Use direct checks for mechanical work. Without subagents, assess sequentially and report missing independence; return `BLOCKED` if required independent review is unavailable. 4. Collect verdicts and findings with criterion, location or scenario, evidence, impact, smallest remedy, and acceptance check. Deduplicate them into required fixes, selected improvements, optional suggestions, and justified rejections. Resolve disagreements with evidence; a disputed required criterion remains open. -5. Return actionable fixes to the caller. After every authorized revision, rerun invalidated checks and request fresh verdicts from affected reviewers and critics. Reuse only evidence and acceptance unaffected by the current candidate. +5. Return fixes to the caller. After authorized revisions, send affected reviewers the reason, revised material, and invalidated evidence. Rerun invalidated checks and renew affected verdicts; retain only evidence and acceptance unaffected by changes to the candidate, inputs, or relevant environment. 6. Return `PASS` only when every required criterion has proof, required perspectives accept their scopes, and no required finding remains. Otherwise return `REVISE` with fixes for the caller to implement and resubmit, or `BLOCKED` with the unmet criterion, cause, options, recommendation, and consequence. On unchanged evidence, change approach rather than retrying or lowering criteria. ## Pitfalls diff --git a/plugins/codex/skills/plan-work/references/vstack/protocols/quality-validation.md b/plugins/codex/skills/plan-work/references/vstack/protocols/quality-validation.md index e038fe9..9a0d797 100644 --- a/plugins/codex/skills/plan-work/references/vstack/protocols/quality-validation.md +++ b/plugins/codex/skills/plan-work/references/vstack/protocols/quality-validation.md @@ -15,9 +15,9 @@ 1. Reuse the caller's validation contract. Record candidate, mode, required criteria, evidence or checks, unacceptable outcomes, and useful review perspectives from the request, applicable instructions, principles, and owning workflow. 2. Have the producer self-assess each criterion as pass, fail, or unverified with evidence. Return known defects to the caller before independent review. A score may summarize a defined rubric but cannot replace required proof. -3. For substantive work, use distinct subagents for review of correctness, completeness, and preserved behavior, and critique of assumptions, necessity, simplicity, and alternatives. Give each the same contract, candidate, evidence, and bounded scope. Use direct checks for mechanical work; without subagents, assess sequentially and report unavailable independence. If independent review is required but unavailable, return `BLOCKED`. +3. For substantive work, obtain review of correctness, completeness, and preserved behavior, and critique of assumptions, necessity, simplicity, and alternatives from reviewers independent of the producer. One reviewer may cover both; add reviewers only for required separation or non-overlapping parallel scopes. Supply scoped criteria, the candidate or diff, and current evidence. Assign checks within each reviewer's tools and authority; return missing required evidence to the caller. Use direct checks for mechanical work. Without subagents, assess sequentially and report missing independence; return `BLOCKED` if required independent review is unavailable. 4. Collect verdicts and findings with criterion, location or scenario, evidence, impact, smallest remedy, and acceptance check. Deduplicate them into required fixes, selected improvements, optional suggestions, and justified rejections. Resolve disagreements with evidence; a disputed required criterion remains open. -5. Return actionable fixes to the caller. After every authorized revision, rerun invalidated checks and request fresh verdicts from affected reviewers and critics. Reuse only evidence and acceptance unaffected by the current candidate. +5. Return fixes to the caller. After authorized revisions, send affected reviewers the reason, revised material, and invalidated evidence. Rerun invalidated checks and renew affected verdicts; retain only evidence and acceptance unaffected by changes to the candidate, inputs, or relevant environment. 6. Return `PASS` only when every required criterion has proof, required perspectives accept their scopes, and no required finding remains. Otherwise return `REVISE` with fixes for the caller to implement and resubmit, or `BLOCKED` with the unmet criterion, cause, options, recommendation, and consequence. On unchanged evidence, change approach rather than retrying or lowering criteria. ## Pitfalls diff --git a/plugins/codex/skills/review-ui/references/vstack/protocols/quality-validation.md b/plugins/codex/skills/review-ui/references/vstack/protocols/quality-validation.md index e038fe9..9a0d797 100644 --- a/plugins/codex/skills/review-ui/references/vstack/protocols/quality-validation.md +++ b/plugins/codex/skills/review-ui/references/vstack/protocols/quality-validation.md @@ -15,9 +15,9 @@ 1. Reuse the caller's validation contract. Record candidate, mode, required criteria, evidence or checks, unacceptable outcomes, and useful review perspectives from the request, applicable instructions, principles, and owning workflow. 2. Have the producer self-assess each criterion as pass, fail, or unverified with evidence. Return known defects to the caller before independent review. A score may summarize a defined rubric but cannot replace required proof. -3. For substantive work, use distinct subagents for review of correctness, completeness, and preserved behavior, and critique of assumptions, necessity, simplicity, and alternatives. Give each the same contract, candidate, evidence, and bounded scope. Use direct checks for mechanical work; without subagents, assess sequentially and report unavailable independence. If independent review is required but unavailable, return `BLOCKED`. +3. For substantive work, obtain review of correctness, completeness, and preserved behavior, and critique of assumptions, necessity, simplicity, and alternatives from reviewers independent of the producer. One reviewer may cover both; add reviewers only for required separation or non-overlapping parallel scopes. Supply scoped criteria, the candidate or diff, and current evidence. Assign checks within each reviewer's tools and authority; return missing required evidence to the caller. Use direct checks for mechanical work. Without subagents, assess sequentially and report missing independence; return `BLOCKED` if required independent review is unavailable. 4. Collect verdicts and findings with criterion, location or scenario, evidence, impact, smallest remedy, and acceptance check. Deduplicate them into required fixes, selected improvements, optional suggestions, and justified rejections. Resolve disagreements with evidence; a disputed required criterion remains open. -5. Return actionable fixes to the caller. After every authorized revision, rerun invalidated checks and request fresh verdicts from affected reviewers and critics. Reuse only evidence and acceptance unaffected by the current candidate. +5. Return fixes to the caller. After authorized revisions, send affected reviewers the reason, revised material, and invalidated evidence. Rerun invalidated checks and renew affected verdicts; retain only evidence and acceptance unaffected by changes to the candidate, inputs, or relevant environment. 6. Return `PASS` only when every required criterion has proof, required perspectives accept their scopes, and no required finding remains. Otherwise return `REVISE` with fixes for the caller to implement and resubmit, or `BLOCKED` with the unmet criterion, cause, options, recommendation, and consequence. On unchanged evidence, change approach rather than retrying or lowering criteria. ## Pitfalls diff --git a/plugins/codex/skills/vllnt-collaboration-principles/SKILL.md b/plugins/codex/skills/vllnt-collaboration-principles/SKILL.md index 603afda..989c51b 100644 --- a/plugins/codex/skills/vllnt-collaboration-principles/SKILL.md +++ b/plugins/codex/skills/vllnt-collaboration-principles/SKILL.md @@ -7,7 +7,6 @@ description: Load at each session start to keep human collaboration proactive, c - Advance within the request and established authority. Infer routine reversible details; missing prohibitions do not authorize unrelated actions. - Complete necessary authorized work without routine permission requests. Continue useful independent work while a decision is pending. -- Reply simply: state the result or current status, then the next action. Include detail only when it changes a decision, risk, or verification. +- End with a brief outcome and any unfinished or unverified requested work. Distinguish completed actions from proposals and attempts. - Ask only for missing authority, access, or a consequential choice. First identify the cause, try safe alternatives, and prepare the concrete result. -- For a genuine blocker, give the smallest viable options, a recommendation, and the consequence. Use a targeted yes/no question when sufficient. -- Return useful partial work and the unmet condition when completion is impossible; never present proposed or attempted work as completed. +- If blocked, state the cause—or that it is unknown—and concrete options with key tradeoffs. Recommend the next action, name who must act, and specify any required input or approval. Do not ask the user to do work you can complete within existing authority. diff --git a/plugins/cursor/.cursor-plugin/plugin.json b/plugins/cursor/.cursor-plugin/plugin.json index 10a57f8..ccf67b4 100644 --- a/plugins/cursor/.cursor-plugin/plugin.json +++ b/plugins/cursor/.cursor-plugin/plugin.json @@ -5,5 +5,5 @@ "description": "Vstack portable workflows and engineering principles.", "license": "MIT", "name": "vstack", - "version": "0.1.0-dev.4" + "version": "0.1.0-dev.5" } diff --git a/plugins/cursor/SOURCE.json b/plugins/cursor/SOURCE.json index 55e181e..f4c2493 100644 --- a/plugins/cursor/SOURCE.json +++ b/plugins/cursor/SOURCE.json @@ -1,14 +1,14 @@ { "files": { - ".cursor-plugin/plugin.json": "ae919c00243ca616f002953a6310cdf7da451788152ea722f1f7ccae1b1912c0", + ".cursor-plugin/plugin.json": "6451f853284b73851d66d22b81907f8c99153221c0420b93ab549d83df4864bc", "LICENSE": "24ba061a4603738ddd5105ef4abc198eeded5ac7efce23b360561816f4dd6559", - "rules/vstack-principles.mdc": "779b06b785c89b7b74c076c020fedbc91857e90ec0ef0ccf185ca23fc1313427", + "rules/vstack-principles.mdc": "5234bc0506e0a328d6163cd83785d2f37dd1fc23ef84287d71e03b92459e064a", "skills/build-landing-page/README.md": "46a280eadac8962180cf3f0c42eb0e845a3b0156a644569182d932881e1d51f8", "skills/build-landing-page/SKILL.md": "b08e4963d6149f3647b28a0d9dccdc8793812abab95a1d081d93699e142de0f0", "skills/build-landing-page/references/copywriting-formulas.md": "6d19f6166e1badcfdda0af4f8b303160e94ee6e6149321157e12849654cc013e", "skills/build-landing-page/references/review-rubric.md": "6c06f95eea847f63e2327b34c89fb167fec0f52360cd50bcfa257f9f96f33b0e", "skills/build-landing-page/references/structure-blueprints.md": "1f0a52ecb8d4d78f3f9eea6d89db8f471188986e1a9ad39b19587e52001e99e3", - "skills/build-landing-page/references/vstack/protocols/quality-validation.md": "522c097cb146a9fd016fd91facadb3faa13b0d6f7f14707d7bdf23aca3143b19", + "skills/build-landing-page/references/vstack/protocols/quality-validation.md": "e53fca023d31b907d60019c68a5d823e0d89ae83d09e49e68c71bc9ec5a1303a", "skills/build-project/SKILL.md": "719bff37da357fb73062ff302a86650e4d1611f5b7d8712155a94a6802a985d0", "skills/build-project/references/vstack/capabilities/convex-components/REFERENCE.md": "ebd776c115b578aff19f6bfceee61cb694afe63546a882de50cb020f6ba996e5", "skills/build-project/references/vstack/capabilities/eslint-configuration/REFERENCE.md": "5a2e090a253b89b6dee9c474a7044cd10be81427792c51b7a3322c0f163ae44b", @@ -17,9 +17,9 @@ "skills/build-project/references/vstack/capabilities/stack-packages/references/github-npm.md": "c1731affd8f0be4c62b988e45659b754948513e9b6ef8c61b96cab10bc0ffef2", "skills/build-project/references/vstack/capabilities/typescript-configuration/REFERENCE.md": "baccc320777d2050be44ccd2219e38f0dbf199127da11598642d53e71c594bba", "skills/build-project/references/vstack/capabilities/workspace-turborepo/REFERENCE.md": "af854042419d04d4f6af4454bcee41f3275fb70c466fd6efefa1bff273e295ab", - "skills/build-project/references/vstack/protocols/quality-validation.md": "522c097cb146a9fd016fd91facadb3faa13b0d6f7f14707d7bdf23aca3143b19", + "skills/build-project/references/vstack/protocols/quality-validation.md": "e53fca023d31b907d60019c68a5d823e0d89ae83d09e49e68c71bc9ec5a1303a", "skills/build-prototype/SKILL.md": "7a27f04b673c733ab6aa0e4f3eed68f8fa1ce82884e22eda6ec24cbba5ab162e", - "skills/build-prototype/references/vstack/protocols/quality-validation.md": "522c097cb146a9fd016fd91facadb3faa13b0d6f7f14707d7bdf23aca3143b19", + "skills/build-prototype/references/vstack/protocols/quality-validation.md": "e53fca023d31b907d60019c68a5d823e0d89ae83d09e49e68c71bc9ec5a1303a", "skills/deliver-issue/SKILL.md": "a81532ec0e731f80092f4be969d73f923b84fdc240b58781b86e3b8095b288bc", "skills/deliver-issue/references/vstack/capabilities/code-architecture/DEEPENING.md": "9850a1364402229df25d0fd686b6905bbcbdaa52fccaf7d5344307fd900fed2e", "skills/deliver-issue/references/vstack/capabilities/code-architecture/INTERFACE-DESIGN.md": "60d6651b5cd0de5479f60b7840b6e156cb41f2f80ae4a91c661f67874c5dbee8", @@ -29,7 +29,7 @@ "skills/deliver-issue/references/vstack/capabilities/convex-components/REFERENCE.md": "ebd776c115b578aff19f6bfceee61cb694afe63546a882de50cb020f6ba996e5", "skills/deliver-issue/references/vstack/capabilities/nextjs-tests/REFERENCE.md": "3447bd768cbf50efd1a12a60c72060f5a2ec1335fa56d45da091e376858780a9", "skills/deliver-issue/references/vstack/capabilities/ui-accessibility/REFERENCE.md": "f265d321d975a0319ab5455b7fefd74e4852de63b7bd14d1f9d044c78371c25b", - "skills/deliver-issue/references/vstack/protocols/quality-validation.md": "522c097cb146a9fd016fd91facadb3faa13b0d6f7f14707d7bdf23aca3143b19", + "skills/deliver-issue/references/vstack/protocols/quality-validation.md": "e53fca023d31b907d60019c68a5d823e0d89ae83d09e49e68c71bc9ec5a1303a", "skills/deliver-pull-request/SKILL.md": "afdf9ef8ae23fd899e5cbd246440efd6c2e10be2016599d85034bf89304df96c", "skills/deliver-pull-request/references/vstack/capabilities/ci-optimization/REFERENCE.md": "b376d64c2297e6ba535b581474bddb6c777c8a847d3424cdcc77fef7cd0d99a9", "skills/deliver-pull-request/references/vstack/capabilities/ci-optimization/references/scenarios.md": "731de32df4a92fcb78047b7f9c8b71ab9697ea1daebdc101295fdbc26a5c9320", @@ -48,12 +48,12 @@ "skills/deliver-pull-request/references/vstack/capabilities/release-readiness/references/release-messaging.md": "4f5cc13e7fd30cd84ccf84dbd02f0d5696ccb52a3b27c8f448a29c983e28a4c1", "skills/deliver-pull-request/references/vstack/capabilities/release-readiness/references/version-sync.md": "3e9ecae39a8e5f5a33914a4097ea5728c24ce9292618bd295761297fb1d7cb78", "skills/deliver-pull-request/references/vstack/capabilities/runtime-performance/REFERENCE.md": "6692e8fdd6a736d06b8adec108e07b6b19f8bcf0d62051cacc0d24f73a3ebcd9", - "skills/deliver-pull-request/references/vstack/protocols/quality-validation.md": "522c097cb146a9fd016fd91facadb3faa13b0d6f7f14707d7bdf23aca3143b19", + "skills/deliver-pull-request/references/vstack/protocols/quality-validation.md": "e53fca023d31b907d60019c68a5d823e0d89ae83d09e49e68c71bc9ec5a1303a", "skills/explain-subject/SKILL.md": "909b948a392bf37264d5747626fd8e75541d0b6a528c70bd2176a5ff0e9e8b85", "skills/explain-subject/references/vstack/capabilities/reasoning-assumptions/REFERENCE.md": "edf4b1bf183541c7198f8ec6a00e25db790c8510fe4fcf6c1060d9b2b4f9e50d", - "skills/explain-subject/references/vstack/protocols/quality-validation.md": "522c097cb146a9fd016fd91facadb3faa13b0d6f7f14707d7bdf23aca3143b19", + "skills/explain-subject/references/vstack/protocols/quality-validation.md": "e53fca023d31b907d60019c68a5d823e0d89ae83d09e49e68c71bc9ec5a1303a", "skills/explore-decisions/SKILL.md": "07a1f5daa4543de924cd3b5bc8dfd2b482aeb0e94da8338d328402fb5505d11b", - "skills/explore-decisions/references/vstack/protocols/quality-validation.md": "522c097cb146a9fd016fd91facadb3faa13b0d6f7f14707d7bdf23aca3143b19", + "skills/explore-decisions/references/vstack/protocols/quality-validation.md": "e53fca023d31b907d60019c68a5d823e0d89ae83d09e49e68c71bc9ec5a1303a", "skills/improve-code/SKILL.md": "98cf3810fcb70580dbbb915d6bd7aee5f664b4c3e3b64dc4743253574a452d46", "skills/improve-code/references/vstack/capabilities/code-architecture/DEEPENING.md": "9850a1364402229df25d0fd686b6905bbcbdaa52fccaf7d5344307fd900fed2e", "skills/improve-code/references/vstack/capabilities/code-architecture/INTERFACE-DESIGN.md": "60d6651b5cd0de5479f60b7840b6e156cb41f2f80ae4a91c661f67874c5dbee8", @@ -65,7 +65,7 @@ "skills/improve-code/references/vstack/capabilities/code-test-management/references/test-doubles.md": "c3006a6f6fef0039b8c8e879bfcf728bd553c85ce80f512521a08161c3c40a28", "skills/improve-code/references/vstack/capabilities/runtime-performance/REFERENCE.md": "6692e8fdd6a736d06b8adec108e07b6b19f8bcf0d62051cacc0d24f73a3ebcd9", "skills/improve-code/references/vstack/capabilities/workspace-turborepo/REFERENCE.md": "af854042419d04d4f6af4454bcee41f3275fb70c466fd6efefa1bff273e295ab", - "skills/improve-code/references/vstack/protocols/quality-validation.md": "522c097cb146a9fd016fd91facadb3faa13b0d6f7f14707d7bdf23aca3143b19", + "skills/improve-code/references/vstack/protocols/quality-validation.md": "e53fca023d31b907d60019c68a5d823e0d89ae83d09e49e68c71bc9ec5a1303a", "skills/improve-project/SKILL.md": "7d7a175d64e3180341c59d0d9b7cc4d1a2d20df37452673937701ac171b73e86", "skills/improve-project/references/vstack/capabilities/ci-optimization/REFERENCE.md": "b376d64c2297e6ba535b581474bddb6c777c8a847d3424cdcc77fef7cd0d99a9", "skills/improve-project/references/vstack/capabilities/ci-optimization/references/scenarios.md": "731de32df4a92fcb78047b7f9c8b71ab9697ea1daebdc101295fdbc26a5c9320", @@ -77,13 +77,13 @@ "skills/improve-project/references/vstack/capabilities/stack-packages/references/github-npm.md": "c1731affd8f0be4c62b988e45659b754948513e9b6ef8c61b96cab10bc0ffef2", "skills/improve-project/references/vstack/capabilities/typescript-configuration/REFERENCE.md": "baccc320777d2050be44ccd2219e38f0dbf199127da11598642d53e71c594bba", "skills/improve-project/references/vstack/capabilities/workspace-turborepo/REFERENCE.md": "af854042419d04d4f6af4454bcee41f3275fb70c466fd6efefa1bff273e295ab", - "skills/improve-project/references/vstack/protocols/quality-validation.md": "522c097cb146a9fd016fd91facadb3faa13b0d6f7f14707d7bdf23aca3143b19", + "skills/improve-project/references/vstack/protocols/quality-validation.md": "e53fca023d31b907d60019c68a5d823e0d89ae83d09e49e68c71bc9ec5a1303a", "skills/improve-ui/SKILL.md": "91989dc9cad28ee29e8f899132bf4e2de9dfe152aec653e03038287ab2b452d1", "skills/improve-ui/references/vstack/capabilities/ui-accessibility/REFERENCE.md": "f265d321d975a0319ab5455b7fefd74e4852de63b7bd14d1f9d044c78371c25b", "skills/improve-ui/references/vstack/capabilities/web-performance/REFERENCE.md": "52fb4ebb9e024fa6184da9187f3311d17a53c40691a63f5b2b6c471729f760ff", "skills/improve-ui/references/vstack/capabilities/web-performance/references/eval-audits.md": "d94253fb08c7059329022026843088c46c23a8615d134ace36eea4cb61fa9a6c", "skills/improve-ui/references/vstack/capabilities/web-performance/references/optimization-playbook.md": "0acdedcb0496f4926bee2d23a2294a152a8107c88c5e9f934afa8334e74fde13", - "skills/improve-ui/references/vstack/protocols/quality-validation.md": "522c097cb146a9fd016fd91facadb3faa13b0d6f7f14707d7bdf23aca3143b19", + "skills/improve-ui/references/vstack/protocols/quality-validation.md": "e53fca023d31b907d60019c68a5d823e0d89ae83d09e49e68c71bc9ec5a1303a", "skills/manage-defects/SKILL.md": "04d0501484ab5c507ace3ec204aae38b29b0cafd6f80747955c9118f8b0d97ba", "skills/manage-defects/references/vstack/capabilities/code-architecture/DEEPENING.md": "9850a1364402229df25d0fd686b6905bbcbdaa52fccaf7d5344307fd900fed2e", "skills/manage-defects/references/vstack/capabilities/code-architecture/INTERFACE-DESIGN.md": "60d6651b5cd0de5479f60b7840b6e156cb41f2f80ae4a91c661f67874c5dbee8", @@ -94,7 +94,7 @@ "skills/manage-defects/references/vstack/capabilities/nextjs-tests/REFERENCE.md": "3447bd768cbf50efd1a12a60c72060f5a2ec1335fa56d45da091e376858780a9", "skills/manage-defects/references/vstack/capabilities/runtime-performance/REFERENCE.md": "6692e8fdd6a736d06b8adec108e07b6b19f8bcf0d62051cacc0d24f73a3ebcd9", "skills/manage-defects/references/vstack/capabilities/ui-accessibility/REFERENCE.md": "f265d321d975a0319ab5455b7fefd74e4852de63b7bd14d1f9d044c78371c25b", - "skills/manage-defects/references/vstack/protocols/quality-validation.md": "522c097cb146a9fd016fd91facadb3faa13b0d6f7f14707d7bdf23aca3143b19", + "skills/manage-defects/references/vstack/protocols/quality-validation.md": "e53fca023d31b907d60019c68a5d823e0d89ae83d09e49e68c71bc9ec5a1303a", "skills/manage-issues/README.md": "867654dad179b039a3c058844f089939bfcf947096ba3ac1ce92a6015d9ac63a", "skills/manage-issues/SKILL.md": "36174c90206a6c3cf58a0b15ee32c07a4a4609aeb3563c939f34bb6b7b88d861", "skills/manage-issues/references/docs-alignment.md": "cd6c59a9488fa7f0353eb6b4726a243974f4019e7e0272d60015f46cdeeac210", @@ -102,19 +102,19 @@ "skills/manage-issues/references/parallelize.md": "16455c43dde811e86682cfd206192479bacfefd45e827da993a13fae3fcec1de", "skills/manage-issues/references/quality-gate.md": "43d3ca7e14041c4b49ca676d51be1ce5b7c9a13f6cfdf497aa1ab762d6988c37", "skills/manage-issues/references/stale.md": "f190ad3c0f3292418de9d86a5811d3c4de3c8feff6189267bbc126cd8a612004", - "skills/manage-issues/references/vstack/protocols/quality-validation.md": "522c097cb146a9fd016fd91facadb3faa13b0d6f7f14707d7bdf23aca3143b19", + "skills/manage-issues/references/vstack/protocols/quality-validation.md": "e53fca023d31b907d60019c68a5d823e0d89ae83d09e49e68c71bc9ec5a1303a", "skills/manage-issues/templates/issue-template.md": "ba25b30b6c1991b88f72146e9770f89a81959a1c92305bf2fe080880b9b245b0", "skills/manage-roadmap/SKILL.md": "759565e546f800a6126ce97a6afee94d7685219fd946ee86ddda5ab6027b1ae6", "skills/manage-roadmap/references/format.md": "67e052640c1bb6b6ff933de6ce7a9d386e460ec193226e29c7b561314d0f8d4e", "skills/manage-roadmap/references/parallel.md": "c38bd2a8c3228552852f15255a64113ad95ef1ec44214991cc71bb0508b48105", - "skills/manage-roadmap/references/vstack/protocols/quality-validation.md": "522c097cb146a9fd016fd91facadb3faa13b0d6f7f14707d7bdf23aca3143b19", + "skills/manage-roadmap/references/vstack/protocols/quality-validation.md": "e53fca023d31b907d60019c68a5d823e0d89ae83d09e49e68c71bc9ec5a1303a", "skills/manage-rules/SKILL.md": "8b68d3dc576ba3cc31efda6ce7e99ab3fbba2e9406bc91c1dc93a35faa390c6f", - "skills/manage-rules/references/vstack/protocols/quality-validation.md": "522c097cb146a9fd016fd91facadb3faa13b0d6f7f14707d7bdf23aca3143b19", + "skills/manage-rules/references/vstack/protocols/quality-validation.md": "e53fca023d31b907d60019c68a5d823e0d89ae83d09e49e68c71bc9ec5a1303a", "skills/manage-skills/SKILL.md": "05bf1e174bd54cd4561d7dfd3c2278c48278a044fd755c27e12612064e255c3a", - "skills/manage-skills/references/vstack/protocols/quality-validation.md": "522c097cb146a9fd016fd91facadb3faa13b0d6f7f14707d7bdf23aca3143b19", + "skills/manage-skills/references/vstack/protocols/quality-validation.md": "e53fca023d31b907d60019c68a5d823e0d89ae83d09e49e68c71bc9ec5a1303a", "skills/manage-vision/SKILL.md": "d1c3fa2e276dd7939b91b25fc840986a07aa9184ddf51645aa2f71549f7cc647", "skills/manage-vision/references/format.md": "d9a2ca5b92f8194f7cab5ad4fdd8722d72888e0eeb4875503fec9d3d5d1ff3c4", - "skills/manage-vision/references/vstack/protocols/quality-validation.md": "522c097cb146a9fd016fd91facadb3faa13b0d6f7f14707d7bdf23aca3143b19", + "skills/manage-vision/references/vstack/protocols/quality-validation.md": "e53fca023d31b907d60019c68a5d823e0d89ae83d09e49e68c71bc9ec5a1303a", "skills/plan-issues/SKILL.md": "dedf1efea18b847278e5c6530ec14d5396d150780d6c81f059e7c3fd81853f35", "skills/plan-issues/references/vstack/capabilities/agent-tooling-review/REFERENCE.md": "7b727fbe19c53878de4ba729e1bacea2d0a953444050232d35db2ad7b673fcc3", "skills/plan-issues/references/vstack/capabilities/compliance-review/REFERENCE.md": "3532a9686e5d52da0a82850d15b284b6acd82b0da8506c3679e17c8924f68694", @@ -124,21 +124,21 @@ "skills/plan-issues/references/vstack/capabilities/compliance-review/references/privacy.md": "8a1aa4a96b0cf786c0099e76f4b46d255ee5135dcf1caf53b123fec7e4e11a8d", "skills/plan-issues/references/vstack/capabilities/infrastructure-costs/REFERENCE.md": "407b208fd7f2d9c1a611197154d9594a23d0506d637e298aa543a24bcb9fafd0", "skills/plan-issues/references/vstack/capabilities/infrastructure-review/REFERENCE.md": "17bd7a5b3d341d5b6ad08f917efbca69f3901b1fba545b75d2b4909cf831e4f8", - "skills/plan-issues/references/vstack/protocols/quality-validation.md": "522c097cb146a9fd016fd91facadb3faa13b0d6f7f14707d7bdf23aca3143b19", + "skills/plan-issues/references/vstack/protocols/quality-validation.md": "e53fca023d31b907d60019c68a5d823e0d89ae83d09e49e68c71bc9ec5a1303a", "skills/plan-work/SKILL.md": "4cc59fa808209d47d636ad1c65890d46e7b45729d7a211a8bc83ff5df3314886", - "skills/plan-work/references/vstack/protocols/quality-validation.md": "522c097cb146a9fd016fd91facadb3faa13b0d6f7f14707d7bdf23aca3143b19", + "skills/plan-work/references/vstack/protocols/quality-validation.md": "e53fca023d31b907d60019c68a5d823e0d89ae83d09e49e68c71bc9ec5a1303a", "skills/review-ui/SKILL.md": "b9e18bd0a294238486119a1d302a0d5ab06f4f77d5f5d37b77980ec68e6a580c", "skills/review-ui/references/vstack/capabilities/ui-accessibility/REFERENCE.md": "f265d321d975a0319ab5455b7fefd74e4852de63b7bd14d1f9d044c78371c25b", "skills/review-ui/references/vstack/capabilities/web-performance/REFERENCE.md": "52fb4ebb9e024fa6184da9187f3311d17a53c40691a63f5b2b6c471729f760ff", "skills/review-ui/references/vstack/capabilities/web-performance/references/eval-audits.md": "d94253fb08c7059329022026843088c46c23a8615d134ace36eea4cb61fa9a6c", "skills/review-ui/references/vstack/capabilities/web-performance/references/optimization-playbook.md": "0acdedcb0496f4926bee2d23a2294a152a8107c88c5e9f934afa8334e74fde13", - "skills/review-ui/references/vstack/protocols/quality-validation.md": "522c097cb146a9fd016fd91facadb3faa13b0d6f7f14707d7bdf23aca3143b19", - "skills/vllnt-collaboration-principles/SKILL.md": "a2540f13682fbe29defdaafc8c14221ea05f4cba60b0e6c2c2fd595fb55489f1", + "skills/review-ui/references/vstack/protocols/quality-validation.md": "e53fca023d31b907d60019c68a5d823e0d89ae83d09e49e68c71bc9ec5a1303a", + "skills/vllnt-collaboration-principles/SKILL.md": "d706dd9d89a602c9f70803e6b37714b1b68b8f3105f6f6b8cc3ad91cf7b3a478", "skills/vllnt-orchestration-principles/SKILL.md": "16d0df9b250499fa1f5f45e616bb5d126d0ae5fe5901548a476f07e5e94cb3a1", "skills/vllnt-thinking-principles/SKILL.md": "3d1229f311f9d58ec3335a35e9019afda8cf59dff5c20730a42593c17b40b0b9" }, "upstream": { - "commit": "14b8ad3dbba8ea820478d3ea2d379c2863de56d9", + "commit": "472c216f2f043f0add1f83540cc46ea53d20a7cd", "repository": "https://github.com/vllnt/skills.git" } } diff --git a/plugins/cursor/rules/vstack-principles.mdc b/plugins/cursor/rules/vstack-principles.mdc index cac8b85..f69ac11 100644 --- a/plugins/cursor/rules/vstack-principles.mdc +++ b/plugins/cursor/rules/vstack-principles.mdc @@ -32,7 +32,6 @@ alwaysApply: true - Advance within the request and established authority. Infer routine reversible details; missing prohibitions do not authorize unrelated actions. - Complete necessary authorized work without routine permission requests. Continue useful independent work while a decision is pending. -- Reply simply: state the result or current status, then the next action. Include detail only when it changes a decision, risk, or verification. +- End with a brief outcome and any unfinished or unverified requested work. Distinguish completed actions from proposals and attempts. - Ask only for missing authority, access, or a consequential choice. First identify the cause, try safe alternatives, and prepare the concrete result. -- For a genuine blocker, give the smallest viable options, a recommendation, and the consequence. Use a targeted yes/no question when sufficient. -- Return useful partial work and the unmet condition when completion is impossible; never present proposed or attempted work as completed. +- If blocked, state the cause—or that it is unknown—and concrete options with key tradeoffs. Recommend the next action, name who must act, and specify any required input or approval. Do not ask the user to do work you can complete within existing authority. diff --git a/plugins/cursor/skills/build-landing-page/references/vstack/protocols/quality-validation.md b/plugins/cursor/skills/build-landing-page/references/vstack/protocols/quality-validation.md index e038fe9..9a0d797 100644 --- a/plugins/cursor/skills/build-landing-page/references/vstack/protocols/quality-validation.md +++ b/plugins/cursor/skills/build-landing-page/references/vstack/protocols/quality-validation.md @@ -15,9 +15,9 @@ 1. Reuse the caller's validation contract. Record candidate, mode, required criteria, evidence or checks, unacceptable outcomes, and useful review perspectives from the request, applicable instructions, principles, and owning workflow. 2. Have the producer self-assess each criterion as pass, fail, or unverified with evidence. Return known defects to the caller before independent review. A score may summarize a defined rubric but cannot replace required proof. -3. For substantive work, use distinct subagents for review of correctness, completeness, and preserved behavior, and critique of assumptions, necessity, simplicity, and alternatives. Give each the same contract, candidate, evidence, and bounded scope. Use direct checks for mechanical work; without subagents, assess sequentially and report unavailable independence. If independent review is required but unavailable, return `BLOCKED`. +3. For substantive work, obtain review of correctness, completeness, and preserved behavior, and critique of assumptions, necessity, simplicity, and alternatives from reviewers independent of the producer. One reviewer may cover both; add reviewers only for required separation or non-overlapping parallel scopes. Supply scoped criteria, the candidate or diff, and current evidence. Assign checks within each reviewer's tools and authority; return missing required evidence to the caller. Use direct checks for mechanical work. Without subagents, assess sequentially and report missing independence; return `BLOCKED` if required independent review is unavailable. 4. Collect verdicts and findings with criterion, location or scenario, evidence, impact, smallest remedy, and acceptance check. Deduplicate them into required fixes, selected improvements, optional suggestions, and justified rejections. Resolve disagreements with evidence; a disputed required criterion remains open. -5. Return actionable fixes to the caller. After every authorized revision, rerun invalidated checks and request fresh verdicts from affected reviewers and critics. Reuse only evidence and acceptance unaffected by the current candidate. +5. Return fixes to the caller. After authorized revisions, send affected reviewers the reason, revised material, and invalidated evidence. Rerun invalidated checks and renew affected verdicts; retain only evidence and acceptance unaffected by changes to the candidate, inputs, or relevant environment. 6. Return `PASS` only when every required criterion has proof, required perspectives accept their scopes, and no required finding remains. Otherwise return `REVISE` with fixes for the caller to implement and resubmit, or `BLOCKED` with the unmet criterion, cause, options, recommendation, and consequence. On unchanged evidence, change approach rather than retrying or lowering criteria. ## Pitfalls diff --git a/plugins/cursor/skills/build-project/references/vstack/protocols/quality-validation.md b/plugins/cursor/skills/build-project/references/vstack/protocols/quality-validation.md index e038fe9..9a0d797 100644 --- a/plugins/cursor/skills/build-project/references/vstack/protocols/quality-validation.md +++ b/plugins/cursor/skills/build-project/references/vstack/protocols/quality-validation.md @@ -15,9 +15,9 @@ 1. Reuse the caller's validation contract. Record candidate, mode, required criteria, evidence or checks, unacceptable outcomes, and useful review perspectives from the request, applicable instructions, principles, and owning workflow. 2. Have the producer self-assess each criterion as pass, fail, or unverified with evidence. Return known defects to the caller before independent review. A score may summarize a defined rubric but cannot replace required proof. -3. For substantive work, use distinct subagents for review of correctness, completeness, and preserved behavior, and critique of assumptions, necessity, simplicity, and alternatives. Give each the same contract, candidate, evidence, and bounded scope. Use direct checks for mechanical work; without subagents, assess sequentially and report unavailable independence. If independent review is required but unavailable, return `BLOCKED`. +3. For substantive work, obtain review of correctness, completeness, and preserved behavior, and critique of assumptions, necessity, simplicity, and alternatives from reviewers independent of the producer. One reviewer may cover both; add reviewers only for required separation or non-overlapping parallel scopes. Supply scoped criteria, the candidate or diff, and current evidence. Assign checks within each reviewer's tools and authority; return missing required evidence to the caller. Use direct checks for mechanical work. Without subagents, assess sequentially and report missing independence; return `BLOCKED` if required independent review is unavailable. 4. Collect verdicts and findings with criterion, location or scenario, evidence, impact, smallest remedy, and acceptance check. Deduplicate them into required fixes, selected improvements, optional suggestions, and justified rejections. Resolve disagreements with evidence; a disputed required criterion remains open. -5. Return actionable fixes to the caller. After every authorized revision, rerun invalidated checks and request fresh verdicts from affected reviewers and critics. Reuse only evidence and acceptance unaffected by the current candidate. +5. Return fixes to the caller. After authorized revisions, send affected reviewers the reason, revised material, and invalidated evidence. Rerun invalidated checks and renew affected verdicts; retain only evidence and acceptance unaffected by changes to the candidate, inputs, or relevant environment. 6. Return `PASS` only when every required criterion has proof, required perspectives accept their scopes, and no required finding remains. Otherwise return `REVISE` with fixes for the caller to implement and resubmit, or `BLOCKED` with the unmet criterion, cause, options, recommendation, and consequence. On unchanged evidence, change approach rather than retrying or lowering criteria. ## Pitfalls diff --git a/plugins/cursor/skills/build-prototype/references/vstack/protocols/quality-validation.md b/plugins/cursor/skills/build-prototype/references/vstack/protocols/quality-validation.md index e038fe9..9a0d797 100644 --- a/plugins/cursor/skills/build-prototype/references/vstack/protocols/quality-validation.md +++ b/plugins/cursor/skills/build-prototype/references/vstack/protocols/quality-validation.md @@ -15,9 +15,9 @@ 1. Reuse the caller's validation contract. Record candidate, mode, required criteria, evidence or checks, unacceptable outcomes, and useful review perspectives from the request, applicable instructions, principles, and owning workflow. 2. Have the producer self-assess each criterion as pass, fail, or unverified with evidence. Return known defects to the caller before independent review. A score may summarize a defined rubric but cannot replace required proof. -3. For substantive work, use distinct subagents for review of correctness, completeness, and preserved behavior, and critique of assumptions, necessity, simplicity, and alternatives. Give each the same contract, candidate, evidence, and bounded scope. Use direct checks for mechanical work; without subagents, assess sequentially and report unavailable independence. If independent review is required but unavailable, return `BLOCKED`. +3. For substantive work, obtain review of correctness, completeness, and preserved behavior, and critique of assumptions, necessity, simplicity, and alternatives from reviewers independent of the producer. One reviewer may cover both; add reviewers only for required separation or non-overlapping parallel scopes. Supply scoped criteria, the candidate or diff, and current evidence. Assign checks within each reviewer's tools and authority; return missing required evidence to the caller. Use direct checks for mechanical work. Without subagents, assess sequentially and report missing independence; return `BLOCKED` if required independent review is unavailable. 4. Collect verdicts and findings with criterion, location or scenario, evidence, impact, smallest remedy, and acceptance check. Deduplicate them into required fixes, selected improvements, optional suggestions, and justified rejections. Resolve disagreements with evidence; a disputed required criterion remains open. -5. Return actionable fixes to the caller. After every authorized revision, rerun invalidated checks and request fresh verdicts from affected reviewers and critics. Reuse only evidence and acceptance unaffected by the current candidate. +5. Return fixes to the caller. After authorized revisions, send affected reviewers the reason, revised material, and invalidated evidence. Rerun invalidated checks and renew affected verdicts; retain only evidence and acceptance unaffected by changes to the candidate, inputs, or relevant environment. 6. Return `PASS` only when every required criterion has proof, required perspectives accept their scopes, and no required finding remains. Otherwise return `REVISE` with fixes for the caller to implement and resubmit, or `BLOCKED` with the unmet criterion, cause, options, recommendation, and consequence. On unchanged evidence, change approach rather than retrying or lowering criteria. ## Pitfalls diff --git a/plugins/cursor/skills/deliver-issue/references/vstack/protocols/quality-validation.md b/plugins/cursor/skills/deliver-issue/references/vstack/protocols/quality-validation.md index e038fe9..9a0d797 100644 --- a/plugins/cursor/skills/deliver-issue/references/vstack/protocols/quality-validation.md +++ b/plugins/cursor/skills/deliver-issue/references/vstack/protocols/quality-validation.md @@ -15,9 +15,9 @@ 1. Reuse the caller's validation contract. Record candidate, mode, required criteria, evidence or checks, unacceptable outcomes, and useful review perspectives from the request, applicable instructions, principles, and owning workflow. 2. Have the producer self-assess each criterion as pass, fail, or unverified with evidence. Return known defects to the caller before independent review. A score may summarize a defined rubric but cannot replace required proof. -3. For substantive work, use distinct subagents for review of correctness, completeness, and preserved behavior, and critique of assumptions, necessity, simplicity, and alternatives. Give each the same contract, candidate, evidence, and bounded scope. Use direct checks for mechanical work; without subagents, assess sequentially and report unavailable independence. If independent review is required but unavailable, return `BLOCKED`. +3. For substantive work, obtain review of correctness, completeness, and preserved behavior, and critique of assumptions, necessity, simplicity, and alternatives from reviewers independent of the producer. One reviewer may cover both; add reviewers only for required separation or non-overlapping parallel scopes. Supply scoped criteria, the candidate or diff, and current evidence. Assign checks within each reviewer's tools and authority; return missing required evidence to the caller. Use direct checks for mechanical work. Without subagents, assess sequentially and report missing independence; return `BLOCKED` if required independent review is unavailable. 4. Collect verdicts and findings with criterion, location or scenario, evidence, impact, smallest remedy, and acceptance check. Deduplicate them into required fixes, selected improvements, optional suggestions, and justified rejections. Resolve disagreements with evidence; a disputed required criterion remains open. -5. Return actionable fixes to the caller. After every authorized revision, rerun invalidated checks and request fresh verdicts from affected reviewers and critics. Reuse only evidence and acceptance unaffected by the current candidate. +5. Return fixes to the caller. After authorized revisions, send affected reviewers the reason, revised material, and invalidated evidence. Rerun invalidated checks and renew affected verdicts; retain only evidence and acceptance unaffected by changes to the candidate, inputs, or relevant environment. 6. Return `PASS` only when every required criterion has proof, required perspectives accept their scopes, and no required finding remains. Otherwise return `REVISE` with fixes for the caller to implement and resubmit, or `BLOCKED` with the unmet criterion, cause, options, recommendation, and consequence. On unchanged evidence, change approach rather than retrying or lowering criteria. ## Pitfalls diff --git a/plugins/cursor/skills/deliver-pull-request/references/vstack/protocols/quality-validation.md b/plugins/cursor/skills/deliver-pull-request/references/vstack/protocols/quality-validation.md index e038fe9..9a0d797 100644 --- a/plugins/cursor/skills/deliver-pull-request/references/vstack/protocols/quality-validation.md +++ b/plugins/cursor/skills/deliver-pull-request/references/vstack/protocols/quality-validation.md @@ -15,9 +15,9 @@ 1. Reuse the caller's validation contract. Record candidate, mode, required criteria, evidence or checks, unacceptable outcomes, and useful review perspectives from the request, applicable instructions, principles, and owning workflow. 2. Have the producer self-assess each criterion as pass, fail, or unverified with evidence. Return known defects to the caller before independent review. A score may summarize a defined rubric but cannot replace required proof. -3. For substantive work, use distinct subagents for review of correctness, completeness, and preserved behavior, and critique of assumptions, necessity, simplicity, and alternatives. Give each the same contract, candidate, evidence, and bounded scope. Use direct checks for mechanical work; without subagents, assess sequentially and report unavailable independence. If independent review is required but unavailable, return `BLOCKED`. +3. For substantive work, obtain review of correctness, completeness, and preserved behavior, and critique of assumptions, necessity, simplicity, and alternatives from reviewers independent of the producer. One reviewer may cover both; add reviewers only for required separation or non-overlapping parallel scopes. Supply scoped criteria, the candidate or diff, and current evidence. Assign checks within each reviewer's tools and authority; return missing required evidence to the caller. Use direct checks for mechanical work. Without subagents, assess sequentially and report missing independence; return `BLOCKED` if required independent review is unavailable. 4. Collect verdicts and findings with criterion, location or scenario, evidence, impact, smallest remedy, and acceptance check. Deduplicate them into required fixes, selected improvements, optional suggestions, and justified rejections. Resolve disagreements with evidence; a disputed required criterion remains open. -5. Return actionable fixes to the caller. After every authorized revision, rerun invalidated checks and request fresh verdicts from affected reviewers and critics. Reuse only evidence and acceptance unaffected by the current candidate. +5. Return fixes to the caller. After authorized revisions, send affected reviewers the reason, revised material, and invalidated evidence. Rerun invalidated checks and renew affected verdicts; retain only evidence and acceptance unaffected by changes to the candidate, inputs, or relevant environment. 6. Return `PASS` only when every required criterion has proof, required perspectives accept their scopes, and no required finding remains. Otherwise return `REVISE` with fixes for the caller to implement and resubmit, or `BLOCKED` with the unmet criterion, cause, options, recommendation, and consequence. On unchanged evidence, change approach rather than retrying or lowering criteria. ## Pitfalls diff --git a/plugins/cursor/skills/explain-subject/references/vstack/protocols/quality-validation.md b/plugins/cursor/skills/explain-subject/references/vstack/protocols/quality-validation.md index e038fe9..9a0d797 100644 --- a/plugins/cursor/skills/explain-subject/references/vstack/protocols/quality-validation.md +++ b/plugins/cursor/skills/explain-subject/references/vstack/protocols/quality-validation.md @@ -15,9 +15,9 @@ 1. Reuse the caller's validation contract. Record candidate, mode, required criteria, evidence or checks, unacceptable outcomes, and useful review perspectives from the request, applicable instructions, principles, and owning workflow. 2. Have the producer self-assess each criterion as pass, fail, or unverified with evidence. Return known defects to the caller before independent review. A score may summarize a defined rubric but cannot replace required proof. -3. For substantive work, use distinct subagents for review of correctness, completeness, and preserved behavior, and critique of assumptions, necessity, simplicity, and alternatives. Give each the same contract, candidate, evidence, and bounded scope. Use direct checks for mechanical work; without subagents, assess sequentially and report unavailable independence. If independent review is required but unavailable, return `BLOCKED`. +3. For substantive work, obtain review of correctness, completeness, and preserved behavior, and critique of assumptions, necessity, simplicity, and alternatives from reviewers independent of the producer. One reviewer may cover both; add reviewers only for required separation or non-overlapping parallel scopes. Supply scoped criteria, the candidate or diff, and current evidence. Assign checks within each reviewer's tools and authority; return missing required evidence to the caller. Use direct checks for mechanical work. Without subagents, assess sequentially and report missing independence; return `BLOCKED` if required independent review is unavailable. 4. Collect verdicts and findings with criterion, location or scenario, evidence, impact, smallest remedy, and acceptance check. Deduplicate them into required fixes, selected improvements, optional suggestions, and justified rejections. Resolve disagreements with evidence; a disputed required criterion remains open. -5. Return actionable fixes to the caller. After every authorized revision, rerun invalidated checks and request fresh verdicts from affected reviewers and critics. Reuse only evidence and acceptance unaffected by the current candidate. +5. Return fixes to the caller. After authorized revisions, send affected reviewers the reason, revised material, and invalidated evidence. Rerun invalidated checks and renew affected verdicts; retain only evidence and acceptance unaffected by changes to the candidate, inputs, or relevant environment. 6. Return `PASS` only when every required criterion has proof, required perspectives accept their scopes, and no required finding remains. Otherwise return `REVISE` with fixes for the caller to implement and resubmit, or `BLOCKED` with the unmet criterion, cause, options, recommendation, and consequence. On unchanged evidence, change approach rather than retrying or lowering criteria. ## Pitfalls diff --git a/plugins/cursor/skills/explore-decisions/references/vstack/protocols/quality-validation.md b/plugins/cursor/skills/explore-decisions/references/vstack/protocols/quality-validation.md index e038fe9..9a0d797 100644 --- a/plugins/cursor/skills/explore-decisions/references/vstack/protocols/quality-validation.md +++ b/plugins/cursor/skills/explore-decisions/references/vstack/protocols/quality-validation.md @@ -15,9 +15,9 @@ 1. Reuse the caller's validation contract. Record candidate, mode, required criteria, evidence or checks, unacceptable outcomes, and useful review perspectives from the request, applicable instructions, principles, and owning workflow. 2. Have the producer self-assess each criterion as pass, fail, or unverified with evidence. Return known defects to the caller before independent review. A score may summarize a defined rubric but cannot replace required proof. -3. For substantive work, use distinct subagents for review of correctness, completeness, and preserved behavior, and critique of assumptions, necessity, simplicity, and alternatives. Give each the same contract, candidate, evidence, and bounded scope. Use direct checks for mechanical work; without subagents, assess sequentially and report unavailable independence. If independent review is required but unavailable, return `BLOCKED`. +3. For substantive work, obtain review of correctness, completeness, and preserved behavior, and critique of assumptions, necessity, simplicity, and alternatives from reviewers independent of the producer. One reviewer may cover both; add reviewers only for required separation or non-overlapping parallel scopes. Supply scoped criteria, the candidate or diff, and current evidence. Assign checks within each reviewer's tools and authority; return missing required evidence to the caller. Use direct checks for mechanical work. Without subagents, assess sequentially and report missing independence; return `BLOCKED` if required independent review is unavailable. 4. Collect verdicts and findings with criterion, location or scenario, evidence, impact, smallest remedy, and acceptance check. Deduplicate them into required fixes, selected improvements, optional suggestions, and justified rejections. Resolve disagreements with evidence; a disputed required criterion remains open. -5. Return actionable fixes to the caller. After every authorized revision, rerun invalidated checks and request fresh verdicts from affected reviewers and critics. Reuse only evidence and acceptance unaffected by the current candidate. +5. Return fixes to the caller. After authorized revisions, send affected reviewers the reason, revised material, and invalidated evidence. Rerun invalidated checks and renew affected verdicts; retain only evidence and acceptance unaffected by changes to the candidate, inputs, or relevant environment. 6. Return `PASS` only when every required criterion has proof, required perspectives accept their scopes, and no required finding remains. Otherwise return `REVISE` with fixes for the caller to implement and resubmit, or `BLOCKED` with the unmet criterion, cause, options, recommendation, and consequence. On unchanged evidence, change approach rather than retrying or lowering criteria. ## Pitfalls diff --git a/plugins/cursor/skills/improve-code/references/vstack/protocols/quality-validation.md b/plugins/cursor/skills/improve-code/references/vstack/protocols/quality-validation.md index e038fe9..9a0d797 100644 --- a/plugins/cursor/skills/improve-code/references/vstack/protocols/quality-validation.md +++ b/plugins/cursor/skills/improve-code/references/vstack/protocols/quality-validation.md @@ -15,9 +15,9 @@ 1. Reuse the caller's validation contract. Record candidate, mode, required criteria, evidence or checks, unacceptable outcomes, and useful review perspectives from the request, applicable instructions, principles, and owning workflow. 2. Have the producer self-assess each criterion as pass, fail, or unverified with evidence. Return known defects to the caller before independent review. A score may summarize a defined rubric but cannot replace required proof. -3. For substantive work, use distinct subagents for review of correctness, completeness, and preserved behavior, and critique of assumptions, necessity, simplicity, and alternatives. Give each the same contract, candidate, evidence, and bounded scope. Use direct checks for mechanical work; without subagents, assess sequentially and report unavailable independence. If independent review is required but unavailable, return `BLOCKED`. +3. For substantive work, obtain review of correctness, completeness, and preserved behavior, and critique of assumptions, necessity, simplicity, and alternatives from reviewers independent of the producer. One reviewer may cover both; add reviewers only for required separation or non-overlapping parallel scopes. Supply scoped criteria, the candidate or diff, and current evidence. Assign checks within each reviewer's tools and authority; return missing required evidence to the caller. Use direct checks for mechanical work. Without subagents, assess sequentially and report missing independence; return `BLOCKED` if required independent review is unavailable. 4. Collect verdicts and findings with criterion, location or scenario, evidence, impact, smallest remedy, and acceptance check. Deduplicate them into required fixes, selected improvements, optional suggestions, and justified rejections. Resolve disagreements with evidence; a disputed required criterion remains open. -5. Return actionable fixes to the caller. After every authorized revision, rerun invalidated checks and request fresh verdicts from affected reviewers and critics. Reuse only evidence and acceptance unaffected by the current candidate. +5. Return fixes to the caller. After authorized revisions, send affected reviewers the reason, revised material, and invalidated evidence. Rerun invalidated checks and renew affected verdicts; retain only evidence and acceptance unaffected by changes to the candidate, inputs, or relevant environment. 6. Return `PASS` only when every required criterion has proof, required perspectives accept their scopes, and no required finding remains. Otherwise return `REVISE` with fixes for the caller to implement and resubmit, or `BLOCKED` with the unmet criterion, cause, options, recommendation, and consequence. On unchanged evidence, change approach rather than retrying or lowering criteria. ## Pitfalls diff --git a/plugins/cursor/skills/improve-project/references/vstack/protocols/quality-validation.md b/plugins/cursor/skills/improve-project/references/vstack/protocols/quality-validation.md index e038fe9..9a0d797 100644 --- a/plugins/cursor/skills/improve-project/references/vstack/protocols/quality-validation.md +++ b/plugins/cursor/skills/improve-project/references/vstack/protocols/quality-validation.md @@ -15,9 +15,9 @@ 1. Reuse the caller's validation contract. Record candidate, mode, required criteria, evidence or checks, unacceptable outcomes, and useful review perspectives from the request, applicable instructions, principles, and owning workflow. 2. Have the producer self-assess each criterion as pass, fail, or unverified with evidence. Return known defects to the caller before independent review. A score may summarize a defined rubric but cannot replace required proof. -3. For substantive work, use distinct subagents for review of correctness, completeness, and preserved behavior, and critique of assumptions, necessity, simplicity, and alternatives. Give each the same contract, candidate, evidence, and bounded scope. Use direct checks for mechanical work; without subagents, assess sequentially and report unavailable independence. If independent review is required but unavailable, return `BLOCKED`. +3. For substantive work, obtain review of correctness, completeness, and preserved behavior, and critique of assumptions, necessity, simplicity, and alternatives from reviewers independent of the producer. One reviewer may cover both; add reviewers only for required separation or non-overlapping parallel scopes. Supply scoped criteria, the candidate or diff, and current evidence. Assign checks within each reviewer's tools and authority; return missing required evidence to the caller. Use direct checks for mechanical work. Without subagents, assess sequentially and report missing independence; return `BLOCKED` if required independent review is unavailable. 4. Collect verdicts and findings with criterion, location or scenario, evidence, impact, smallest remedy, and acceptance check. Deduplicate them into required fixes, selected improvements, optional suggestions, and justified rejections. Resolve disagreements with evidence; a disputed required criterion remains open. -5. Return actionable fixes to the caller. After every authorized revision, rerun invalidated checks and request fresh verdicts from affected reviewers and critics. Reuse only evidence and acceptance unaffected by the current candidate. +5. Return fixes to the caller. After authorized revisions, send affected reviewers the reason, revised material, and invalidated evidence. Rerun invalidated checks and renew affected verdicts; retain only evidence and acceptance unaffected by changes to the candidate, inputs, or relevant environment. 6. Return `PASS` only when every required criterion has proof, required perspectives accept their scopes, and no required finding remains. Otherwise return `REVISE` with fixes for the caller to implement and resubmit, or `BLOCKED` with the unmet criterion, cause, options, recommendation, and consequence. On unchanged evidence, change approach rather than retrying or lowering criteria. ## Pitfalls diff --git a/plugins/cursor/skills/improve-ui/references/vstack/protocols/quality-validation.md b/plugins/cursor/skills/improve-ui/references/vstack/protocols/quality-validation.md index e038fe9..9a0d797 100644 --- a/plugins/cursor/skills/improve-ui/references/vstack/protocols/quality-validation.md +++ b/plugins/cursor/skills/improve-ui/references/vstack/protocols/quality-validation.md @@ -15,9 +15,9 @@ 1. Reuse the caller's validation contract. Record candidate, mode, required criteria, evidence or checks, unacceptable outcomes, and useful review perspectives from the request, applicable instructions, principles, and owning workflow. 2. Have the producer self-assess each criterion as pass, fail, or unverified with evidence. Return known defects to the caller before independent review. A score may summarize a defined rubric but cannot replace required proof. -3. For substantive work, use distinct subagents for review of correctness, completeness, and preserved behavior, and critique of assumptions, necessity, simplicity, and alternatives. Give each the same contract, candidate, evidence, and bounded scope. Use direct checks for mechanical work; without subagents, assess sequentially and report unavailable independence. If independent review is required but unavailable, return `BLOCKED`. +3. For substantive work, obtain review of correctness, completeness, and preserved behavior, and critique of assumptions, necessity, simplicity, and alternatives from reviewers independent of the producer. One reviewer may cover both; add reviewers only for required separation or non-overlapping parallel scopes. Supply scoped criteria, the candidate or diff, and current evidence. Assign checks within each reviewer's tools and authority; return missing required evidence to the caller. Use direct checks for mechanical work. Without subagents, assess sequentially and report missing independence; return `BLOCKED` if required independent review is unavailable. 4. Collect verdicts and findings with criterion, location or scenario, evidence, impact, smallest remedy, and acceptance check. Deduplicate them into required fixes, selected improvements, optional suggestions, and justified rejections. Resolve disagreements with evidence; a disputed required criterion remains open. -5. Return actionable fixes to the caller. After every authorized revision, rerun invalidated checks and request fresh verdicts from affected reviewers and critics. Reuse only evidence and acceptance unaffected by the current candidate. +5. Return fixes to the caller. After authorized revisions, send affected reviewers the reason, revised material, and invalidated evidence. Rerun invalidated checks and renew affected verdicts; retain only evidence and acceptance unaffected by changes to the candidate, inputs, or relevant environment. 6. Return `PASS` only when every required criterion has proof, required perspectives accept their scopes, and no required finding remains. Otherwise return `REVISE` with fixes for the caller to implement and resubmit, or `BLOCKED` with the unmet criterion, cause, options, recommendation, and consequence. On unchanged evidence, change approach rather than retrying or lowering criteria. ## Pitfalls diff --git a/plugins/cursor/skills/manage-defects/references/vstack/protocols/quality-validation.md b/plugins/cursor/skills/manage-defects/references/vstack/protocols/quality-validation.md index e038fe9..9a0d797 100644 --- a/plugins/cursor/skills/manage-defects/references/vstack/protocols/quality-validation.md +++ b/plugins/cursor/skills/manage-defects/references/vstack/protocols/quality-validation.md @@ -15,9 +15,9 @@ 1. Reuse the caller's validation contract. Record candidate, mode, required criteria, evidence or checks, unacceptable outcomes, and useful review perspectives from the request, applicable instructions, principles, and owning workflow. 2. Have the producer self-assess each criterion as pass, fail, or unverified with evidence. Return known defects to the caller before independent review. A score may summarize a defined rubric but cannot replace required proof. -3. For substantive work, use distinct subagents for review of correctness, completeness, and preserved behavior, and critique of assumptions, necessity, simplicity, and alternatives. Give each the same contract, candidate, evidence, and bounded scope. Use direct checks for mechanical work; without subagents, assess sequentially and report unavailable independence. If independent review is required but unavailable, return `BLOCKED`. +3. For substantive work, obtain review of correctness, completeness, and preserved behavior, and critique of assumptions, necessity, simplicity, and alternatives from reviewers independent of the producer. One reviewer may cover both; add reviewers only for required separation or non-overlapping parallel scopes. Supply scoped criteria, the candidate or diff, and current evidence. Assign checks within each reviewer's tools and authority; return missing required evidence to the caller. Use direct checks for mechanical work. Without subagents, assess sequentially and report missing independence; return `BLOCKED` if required independent review is unavailable. 4. Collect verdicts and findings with criterion, location or scenario, evidence, impact, smallest remedy, and acceptance check. Deduplicate them into required fixes, selected improvements, optional suggestions, and justified rejections. Resolve disagreements with evidence; a disputed required criterion remains open. -5. Return actionable fixes to the caller. After every authorized revision, rerun invalidated checks and request fresh verdicts from affected reviewers and critics. Reuse only evidence and acceptance unaffected by the current candidate. +5. Return fixes to the caller. After authorized revisions, send affected reviewers the reason, revised material, and invalidated evidence. Rerun invalidated checks and renew affected verdicts; retain only evidence and acceptance unaffected by changes to the candidate, inputs, or relevant environment. 6. Return `PASS` only when every required criterion has proof, required perspectives accept their scopes, and no required finding remains. Otherwise return `REVISE` with fixes for the caller to implement and resubmit, or `BLOCKED` with the unmet criterion, cause, options, recommendation, and consequence. On unchanged evidence, change approach rather than retrying or lowering criteria. ## Pitfalls diff --git a/plugins/cursor/skills/manage-issues/references/vstack/protocols/quality-validation.md b/plugins/cursor/skills/manage-issues/references/vstack/protocols/quality-validation.md index e038fe9..9a0d797 100644 --- a/plugins/cursor/skills/manage-issues/references/vstack/protocols/quality-validation.md +++ b/plugins/cursor/skills/manage-issues/references/vstack/protocols/quality-validation.md @@ -15,9 +15,9 @@ 1. Reuse the caller's validation contract. Record candidate, mode, required criteria, evidence or checks, unacceptable outcomes, and useful review perspectives from the request, applicable instructions, principles, and owning workflow. 2. Have the producer self-assess each criterion as pass, fail, or unverified with evidence. Return known defects to the caller before independent review. A score may summarize a defined rubric but cannot replace required proof. -3. For substantive work, use distinct subagents for review of correctness, completeness, and preserved behavior, and critique of assumptions, necessity, simplicity, and alternatives. Give each the same contract, candidate, evidence, and bounded scope. Use direct checks for mechanical work; without subagents, assess sequentially and report unavailable independence. If independent review is required but unavailable, return `BLOCKED`. +3. For substantive work, obtain review of correctness, completeness, and preserved behavior, and critique of assumptions, necessity, simplicity, and alternatives from reviewers independent of the producer. One reviewer may cover both; add reviewers only for required separation or non-overlapping parallel scopes. Supply scoped criteria, the candidate or diff, and current evidence. Assign checks within each reviewer's tools and authority; return missing required evidence to the caller. Use direct checks for mechanical work. Without subagents, assess sequentially and report missing independence; return `BLOCKED` if required independent review is unavailable. 4. Collect verdicts and findings with criterion, location or scenario, evidence, impact, smallest remedy, and acceptance check. Deduplicate them into required fixes, selected improvements, optional suggestions, and justified rejections. Resolve disagreements with evidence; a disputed required criterion remains open. -5. Return actionable fixes to the caller. After every authorized revision, rerun invalidated checks and request fresh verdicts from affected reviewers and critics. Reuse only evidence and acceptance unaffected by the current candidate. +5. Return fixes to the caller. After authorized revisions, send affected reviewers the reason, revised material, and invalidated evidence. Rerun invalidated checks and renew affected verdicts; retain only evidence and acceptance unaffected by changes to the candidate, inputs, or relevant environment. 6. Return `PASS` only when every required criterion has proof, required perspectives accept their scopes, and no required finding remains. Otherwise return `REVISE` with fixes for the caller to implement and resubmit, or `BLOCKED` with the unmet criterion, cause, options, recommendation, and consequence. On unchanged evidence, change approach rather than retrying or lowering criteria. ## Pitfalls diff --git a/plugins/cursor/skills/manage-roadmap/references/vstack/protocols/quality-validation.md b/plugins/cursor/skills/manage-roadmap/references/vstack/protocols/quality-validation.md index e038fe9..9a0d797 100644 --- a/plugins/cursor/skills/manage-roadmap/references/vstack/protocols/quality-validation.md +++ b/plugins/cursor/skills/manage-roadmap/references/vstack/protocols/quality-validation.md @@ -15,9 +15,9 @@ 1. Reuse the caller's validation contract. Record candidate, mode, required criteria, evidence or checks, unacceptable outcomes, and useful review perspectives from the request, applicable instructions, principles, and owning workflow. 2. Have the producer self-assess each criterion as pass, fail, or unverified with evidence. Return known defects to the caller before independent review. A score may summarize a defined rubric but cannot replace required proof. -3. For substantive work, use distinct subagents for review of correctness, completeness, and preserved behavior, and critique of assumptions, necessity, simplicity, and alternatives. Give each the same contract, candidate, evidence, and bounded scope. Use direct checks for mechanical work; without subagents, assess sequentially and report unavailable independence. If independent review is required but unavailable, return `BLOCKED`. +3. For substantive work, obtain review of correctness, completeness, and preserved behavior, and critique of assumptions, necessity, simplicity, and alternatives from reviewers independent of the producer. One reviewer may cover both; add reviewers only for required separation or non-overlapping parallel scopes. Supply scoped criteria, the candidate or diff, and current evidence. Assign checks within each reviewer's tools and authority; return missing required evidence to the caller. Use direct checks for mechanical work. Without subagents, assess sequentially and report missing independence; return `BLOCKED` if required independent review is unavailable. 4. Collect verdicts and findings with criterion, location or scenario, evidence, impact, smallest remedy, and acceptance check. Deduplicate them into required fixes, selected improvements, optional suggestions, and justified rejections. Resolve disagreements with evidence; a disputed required criterion remains open. -5. Return actionable fixes to the caller. After every authorized revision, rerun invalidated checks and request fresh verdicts from affected reviewers and critics. Reuse only evidence and acceptance unaffected by the current candidate. +5. Return fixes to the caller. After authorized revisions, send affected reviewers the reason, revised material, and invalidated evidence. Rerun invalidated checks and renew affected verdicts; retain only evidence and acceptance unaffected by changes to the candidate, inputs, or relevant environment. 6. Return `PASS` only when every required criterion has proof, required perspectives accept their scopes, and no required finding remains. Otherwise return `REVISE` with fixes for the caller to implement and resubmit, or `BLOCKED` with the unmet criterion, cause, options, recommendation, and consequence. On unchanged evidence, change approach rather than retrying or lowering criteria. ## Pitfalls diff --git a/plugins/cursor/skills/manage-rules/references/vstack/protocols/quality-validation.md b/plugins/cursor/skills/manage-rules/references/vstack/protocols/quality-validation.md index e038fe9..9a0d797 100644 --- a/plugins/cursor/skills/manage-rules/references/vstack/protocols/quality-validation.md +++ b/plugins/cursor/skills/manage-rules/references/vstack/protocols/quality-validation.md @@ -15,9 +15,9 @@ 1. Reuse the caller's validation contract. Record candidate, mode, required criteria, evidence or checks, unacceptable outcomes, and useful review perspectives from the request, applicable instructions, principles, and owning workflow. 2. Have the producer self-assess each criterion as pass, fail, or unverified with evidence. Return known defects to the caller before independent review. A score may summarize a defined rubric but cannot replace required proof. -3. For substantive work, use distinct subagents for review of correctness, completeness, and preserved behavior, and critique of assumptions, necessity, simplicity, and alternatives. Give each the same contract, candidate, evidence, and bounded scope. Use direct checks for mechanical work; without subagents, assess sequentially and report unavailable independence. If independent review is required but unavailable, return `BLOCKED`. +3. For substantive work, obtain review of correctness, completeness, and preserved behavior, and critique of assumptions, necessity, simplicity, and alternatives from reviewers independent of the producer. One reviewer may cover both; add reviewers only for required separation or non-overlapping parallel scopes. Supply scoped criteria, the candidate or diff, and current evidence. Assign checks within each reviewer's tools and authority; return missing required evidence to the caller. Use direct checks for mechanical work. Without subagents, assess sequentially and report missing independence; return `BLOCKED` if required independent review is unavailable. 4. Collect verdicts and findings with criterion, location or scenario, evidence, impact, smallest remedy, and acceptance check. Deduplicate them into required fixes, selected improvements, optional suggestions, and justified rejections. Resolve disagreements with evidence; a disputed required criterion remains open. -5. Return actionable fixes to the caller. After every authorized revision, rerun invalidated checks and request fresh verdicts from affected reviewers and critics. Reuse only evidence and acceptance unaffected by the current candidate. +5. Return fixes to the caller. After authorized revisions, send affected reviewers the reason, revised material, and invalidated evidence. Rerun invalidated checks and renew affected verdicts; retain only evidence and acceptance unaffected by changes to the candidate, inputs, or relevant environment. 6. Return `PASS` only when every required criterion has proof, required perspectives accept their scopes, and no required finding remains. Otherwise return `REVISE` with fixes for the caller to implement and resubmit, or `BLOCKED` with the unmet criterion, cause, options, recommendation, and consequence. On unchanged evidence, change approach rather than retrying or lowering criteria. ## Pitfalls diff --git a/plugins/cursor/skills/manage-skills/references/vstack/protocols/quality-validation.md b/plugins/cursor/skills/manage-skills/references/vstack/protocols/quality-validation.md index e038fe9..9a0d797 100644 --- a/plugins/cursor/skills/manage-skills/references/vstack/protocols/quality-validation.md +++ b/plugins/cursor/skills/manage-skills/references/vstack/protocols/quality-validation.md @@ -15,9 +15,9 @@ 1. Reuse the caller's validation contract. Record candidate, mode, required criteria, evidence or checks, unacceptable outcomes, and useful review perspectives from the request, applicable instructions, principles, and owning workflow. 2. Have the producer self-assess each criterion as pass, fail, or unverified with evidence. Return known defects to the caller before independent review. A score may summarize a defined rubric but cannot replace required proof. -3. For substantive work, use distinct subagents for review of correctness, completeness, and preserved behavior, and critique of assumptions, necessity, simplicity, and alternatives. Give each the same contract, candidate, evidence, and bounded scope. Use direct checks for mechanical work; without subagents, assess sequentially and report unavailable independence. If independent review is required but unavailable, return `BLOCKED`. +3. For substantive work, obtain review of correctness, completeness, and preserved behavior, and critique of assumptions, necessity, simplicity, and alternatives from reviewers independent of the producer. One reviewer may cover both; add reviewers only for required separation or non-overlapping parallel scopes. Supply scoped criteria, the candidate or diff, and current evidence. Assign checks within each reviewer's tools and authority; return missing required evidence to the caller. Use direct checks for mechanical work. Without subagents, assess sequentially and report missing independence; return `BLOCKED` if required independent review is unavailable. 4. Collect verdicts and findings with criterion, location or scenario, evidence, impact, smallest remedy, and acceptance check. Deduplicate them into required fixes, selected improvements, optional suggestions, and justified rejections. Resolve disagreements with evidence; a disputed required criterion remains open. -5. Return actionable fixes to the caller. After every authorized revision, rerun invalidated checks and request fresh verdicts from affected reviewers and critics. Reuse only evidence and acceptance unaffected by the current candidate. +5. Return fixes to the caller. After authorized revisions, send affected reviewers the reason, revised material, and invalidated evidence. Rerun invalidated checks and renew affected verdicts; retain only evidence and acceptance unaffected by changes to the candidate, inputs, or relevant environment. 6. Return `PASS` only when every required criterion has proof, required perspectives accept their scopes, and no required finding remains. Otherwise return `REVISE` with fixes for the caller to implement and resubmit, or `BLOCKED` with the unmet criterion, cause, options, recommendation, and consequence. On unchanged evidence, change approach rather than retrying or lowering criteria. ## Pitfalls diff --git a/plugins/cursor/skills/manage-vision/references/vstack/protocols/quality-validation.md b/plugins/cursor/skills/manage-vision/references/vstack/protocols/quality-validation.md index e038fe9..9a0d797 100644 --- a/plugins/cursor/skills/manage-vision/references/vstack/protocols/quality-validation.md +++ b/plugins/cursor/skills/manage-vision/references/vstack/protocols/quality-validation.md @@ -15,9 +15,9 @@ 1. Reuse the caller's validation contract. Record candidate, mode, required criteria, evidence or checks, unacceptable outcomes, and useful review perspectives from the request, applicable instructions, principles, and owning workflow. 2. Have the producer self-assess each criterion as pass, fail, or unverified with evidence. Return known defects to the caller before independent review. A score may summarize a defined rubric but cannot replace required proof. -3. For substantive work, use distinct subagents for review of correctness, completeness, and preserved behavior, and critique of assumptions, necessity, simplicity, and alternatives. Give each the same contract, candidate, evidence, and bounded scope. Use direct checks for mechanical work; without subagents, assess sequentially and report unavailable independence. If independent review is required but unavailable, return `BLOCKED`. +3. For substantive work, obtain review of correctness, completeness, and preserved behavior, and critique of assumptions, necessity, simplicity, and alternatives from reviewers independent of the producer. One reviewer may cover both; add reviewers only for required separation or non-overlapping parallel scopes. Supply scoped criteria, the candidate or diff, and current evidence. Assign checks within each reviewer's tools and authority; return missing required evidence to the caller. Use direct checks for mechanical work. Without subagents, assess sequentially and report missing independence; return `BLOCKED` if required independent review is unavailable. 4. Collect verdicts and findings with criterion, location or scenario, evidence, impact, smallest remedy, and acceptance check. Deduplicate them into required fixes, selected improvements, optional suggestions, and justified rejections. Resolve disagreements with evidence; a disputed required criterion remains open. -5. Return actionable fixes to the caller. After every authorized revision, rerun invalidated checks and request fresh verdicts from affected reviewers and critics. Reuse only evidence and acceptance unaffected by the current candidate. +5. Return fixes to the caller. After authorized revisions, send affected reviewers the reason, revised material, and invalidated evidence. Rerun invalidated checks and renew affected verdicts; retain only evidence and acceptance unaffected by changes to the candidate, inputs, or relevant environment. 6. Return `PASS` only when every required criterion has proof, required perspectives accept their scopes, and no required finding remains. Otherwise return `REVISE` with fixes for the caller to implement and resubmit, or `BLOCKED` with the unmet criterion, cause, options, recommendation, and consequence. On unchanged evidence, change approach rather than retrying or lowering criteria. ## Pitfalls diff --git a/plugins/cursor/skills/plan-issues/references/vstack/protocols/quality-validation.md b/plugins/cursor/skills/plan-issues/references/vstack/protocols/quality-validation.md index e038fe9..9a0d797 100644 --- a/plugins/cursor/skills/plan-issues/references/vstack/protocols/quality-validation.md +++ b/plugins/cursor/skills/plan-issues/references/vstack/protocols/quality-validation.md @@ -15,9 +15,9 @@ 1. Reuse the caller's validation contract. Record candidate, mode, required criteria, evidence or checks, unacceptable outcomes, and useful review perspectives from the request, applicable instructions, principles, and owning workflow. 2. Have the producer self-assess each criterion as pass, fail, or unverified with evidence. Return known defects to the caller before independent review. A score may summarize a defined rubric but cannot replace required proof. -3. For substantive work, use distinct subagents for review of correctness, completeness, and preserved behavior, and critique of assumptions, necessity, simplicity, and alternatives. Give each the same contract, candidate, evidence, and bounded scope. Use direct checks for mechanical work; without subagents, assess sequentially and report unavailable independence. If independent review is required but unavailable, return `BLOCKED`. +3. For substantive work, obtain review of correctness, completeness, and preserved behavior, and critique of assumptions, necessity, simplicity, and alternatives from reviewers independent of the producer. One reviewer may cover both; add reviewers only for required separation or non-overlapping parallel scopes. Supply scoped criteria, the candidate or diff, and current evidence. Assign checks within each reviewer's tools and authority; return missing required evidence to the caller. Use direct checks for mechanical work. Without subagents, assess sequentially and report missing independence; return `BLOCKED` if required independent review is unavailable. 4. Collect verdicts and findings with criterion, location or scenario, evidence, impact, smallest remedy, and acceptance check. Deduplicate them into required fixes, selected improvements, optional suggestions, and justified rejections. Resolve disagreements with evidence; a disputed required criterion remains open. -5. Return actionable fixes to the caller. After every authorized revision, rerun invalidated checks and request fresh verdicts from affected reviewers and critics. Reuse only evidence and acceptance unaffected by the current candidate. +5. Return fixes to the caller. After authorized revisions, send affected reviewers the reason, revised material, and invalidated evidence. Rerun invalidated checks and renew affected verdicts; retain only evidence and acceptance unaffected by changes to the candidate, inputs, or relevant environment. 6. Return `PASS` only when every required criterion has proof, required perspectives accept their scopes, and no required finding remains. Otherwise return `REVISE` with fixes for the caller to implement and resubmit, or `BLOCKED` with the unmet criterion, cause, options, recommendation, and consequence. On unchanged evidence, change approach rather than retrying or lowering criteria. ## Pitfalls diff --git a/plugins/cursor/skills/plan-work/references/vstack/protocols/quality-validation.md b/plugins/cursor/skills/plan-work/references/vstack/protocols/quality-validation.md index e038fe9..9a0d797 100644 --- a/plugins/cursor/skills/plan-work/references/vstack/protocols/quality-validation.md +++ b/plugins/cursor/skills/plan-work/references/vstack/protocols/quality-validation.md @@ -15,9 +15,9 @@ 1. Reuse the caller's validation contract. Record candidate, mode, required criteria, evidence or checks, unacceptable outcomes, and useful review perspectives from the request, applicable instructions, principles, and owning workflow. 2. Have the producer self-assess each criterion as pass, fail, or unverified with evidence. Return known defects to the caller before independent review. A score may summarize a defined rubric but cannot replace required proof. -3. For substantive work, use distinct subagents for review of correctness, completeness, and preserved behavior, and critique of assumptions, necessity, simplicity, and alternatives. Give each the same contract, candidate, evidence, and bounded scope. Use direct checks for mechanical work; without subagents, assess sequentially and report unavailable independence. If independent review is required but unavailable, return `BLOCKED`. +3. For substantive work, obtain review of correctness, completeness, and preserved behavior, and critique of assumptions, necessity, simplicity, and alternatives from reviewers independent of the producer. One reviewer may cover both; add reviewers only for required separation or non-overlapping parallel scopes. Supply scoped criteria, the candidate or diff, and current evidence. Assign checks within each reviewer's tools and authority; return missing required evidence to the caller. Use direct checks for mechanical work. Without subagents, assess sequentially and report missing independence; return `BLOCKED` if required independent review is unavailable. 4. Collect verdicts and findings with criterion, location or scenario, evidence, impact, smallest remedy, and acceptance check. Deduplicate them into required fixes, selected improvements, optional suggestions, and justified rejections. Resolve disagreements with evidence; a disputed required criterion remains open. -5. Return actionable fixes to the caller. After every authorized revision, rerun invalidated checks and request fresh verdicts from affected reviewers and critics. Reuse only evidence and acceptance unaffected by the current candidate. +5. Return fixes to the caller. After authorized revisions, send affected reviewers the reason, revised material, and invalidated evidence. Rerun invalidated checks and renew affected verdicts; retain only evidence and acceptance unaffected by changes to the candidate, inputs, or relevant environment. 6. Return `PASS` only when every required criterion has proof, required perspectives accept their scopes, and no required finding remains. Otherwise return `REVISE` with fixes for the caller to implement and resubmit, or `BLOCKED` with the unmet criterion, cause, options, recommendation, and consequence. On unchanged evidence, change approach rather than retrying or lowering criteria. ## Pitfalls diff --git a/plugins/cursor/skills/review-ui/references/vstack/protocols/quality-validation.md b/plugins/cursor/skills/review-ui/references/vstack/protocols/quality-validation.md index e038fe9..9a0d797 100644 --- a/plugins/cursor/skills/review-ui/references/vstack/protocols/quality-validation.md +++ b/plugins/cursor/skills/review-ui/references/vstack/protocols/quality-validation.md @@ -15,9 +15,9 @@ 1. Reuse the caller's validation contract. Record candidate, mode, required criteria, evidence or checks, unacceptable outcomes, and useful review perspectives from the request, applicable instructions, principles, and owning workflow. 2. Have the producer self-assess each criterion as pass, fail, or unverified with evidence. Return known defects to the caller before independent review. A score may summarize a defined rubric but cannot replace required proof. -3. For substantive work, use distinct subagents for review of correctness, completeness, and preserved behavior, and critique of assumptions, necessity, simplicity, and alternatives. Give each the same contract, candidate, evidence, and bounded scope. Use direct checks for mechanical work; without subagents, assess sequentially and report unavailable independence. If independent review is required but unavailable, return `BLOCKED`. +3. For substantive work, obtain review of correctness, completeness, and preserved behavior, and critique of assumptions, necessity, simplicity, and alternatives from reviewers independent of the producer. One reviewer may cover both; add reviewers only for required separation or non-overlapping parallel scopes. Supply scoped criteria, the candidate or diff, and current evidence. Assign checks within each reviewer's tools and authority; return missing required evidence to the caller. Use direct checks for mechanical work. Without subagents, assess sequentially and report missing independence; return `BLOCKED` if required independent review is unavailable. 4. Collect verdicts and findings with criterion, location or scenario, evidence, impact, smallest remedy, and acceptance check. Deduplicate them into required fixes, selected improvements, optional suggestions, and justified rejections. Resolve disagreements with evidence; a disputed required criterion remains open. -5. Return actionable fixes to the caller. After every authorized revision, rerun invalidated checks and request fresh verdicts from affected reviewers and critics. Reuse only evidence and acceptance unaffected by the current candidate. +5. Return fixes to the caller. After authorized revisions, send affected reviewers the reason, revised material, and invalidated evidence. Rerun invalidated checks and renew affected verdicts; retain only evidence and acceptance unaffected by changes to the candidate, inputs, or relevant environment. 6. Return `PASS` only when every required criterion has proof, required perspectives accept their scopes, and no required finding remains. Otherwise return `REVISE` with fixes for the caller to implement and resubmit, or `BLOCKED` with the unmet criterion, cause, options, recommendation, and consequence. On unchanged evidence, change approach rather than retrying or lowering criteria. ## Pitfalls diff --git a/plugins/cursor/skills/vllnt-collaboration-principles/SKILL.md b/plugins/cursor/skills/vllnt-collaboration-principles/SKILL.md index 603afda..989c51b 100644 --- a/plugins/cursor/skills/vllnt-collaboration-principles/SKILL.md +++ b/plugins/cursor/skills/vllnt-collaboration-principles/SKILL.md @@ -7,7 +7,6 @@ description: Load at each session start to keep human collaboration proactive, c - Advance within the request and established authority. Infer routine reversible details; missing prohibitions do not authorize unrelated actions. - Complete necessary authorized work without routine permission requests. Continue useful independent work while a decision is pending. -- Reply simply: state the result or current status, then the next action. Include detail only when it changes a decision, risk, or verification. +- End with a brief outcome and any unfinished or unverified requested work. Distinguish completed actions from proposals and attempts. - Ask only for missing authority, access, or a consequential choice. First identify the cause, try safe alternatives, and prepare the concrete result. -- For a genuine blocker, give the smallest viable options, a recommendation, and the consequence. Use a targeted yes/no question when sufficient. -- Return useful partial work and the unmet condition when completion is impossible; never present proposed or attempted work as completed. +- If blocked, state the cause—or that it is unknown—and concrete options with key tradeoffs. Recommend the next action, name who must act, and specify any required input or approval. Do not ask the user to do work you can complete within existing authority. diff --git a/upstream.lock.json b/upstream.lock.json index 6855ed3..0115788 100644 --- a/upstream.lock.json +++ b/upstream.lock.json @@ -1,4 +1,4 @@ { - "commit": "14b8ad3dbba8ea820478d3ea2d379c2863de56d9", + "commit": "472c216f2f043f0add1f83540cc46ea53d20a7cd", "repository": "https://github.com/vllnt/skills.git" }