Repository navigation
tasks skill: require an integration matrix for boundary-touching tasks - #72
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Review on ArchCode
Problem
Plans pass review with one canonical e2e that proves a single path through a boundary. Example: a relay accept socket routed correctly only on the pod that owned it. The single-VM test shared the registry, the post-deploy soak gated nothing, and the bug was found in production. The
tasksskill gave no way to state which entry-point/variation cells the e2e leaves unproven, or to make the task that proves them gate rollout.What changed
Source:
tasks/SKILL.md. Plugin copies regenerated withtools/plugin-gen(npm run build), not hand-edited.verificationcarriesIntegration matrix:(entry points x placement/concurrency/ordering/failure/version skew),Fidelity:(real vs fake, what fakes share, production code at the boundary), andNot proven here:(uncovered cell -> proving task, which must be adepends_onof rollout/enablement or the epic-closing node). One acceptance bullet per matrix cell that matters. One generic worked example (webhook consumer, 2 workers).human/post_deploynode holding deferred proof must be adepends_onof the rollout/enablement or epic-closing node.humantask gates rollout/epic close.Companion: firstlanding PR adds lints
integration-matrix-missingandungated-deferred-proofplus schema docs.Scope
Skill prose only (plus generated plugin copies for 8 harnesses). No CLI or code changes.
Risk
Low. Longer plans for boundary-touching tasks; the skill text is guidance, and nothing parses it.
User impact
Agents authoring plans add matrix/fidelity/not-proven entries and gating edges for boundary-touching tasks.
Testing
No executable e2e exists for skill prose. Checks run in
tools/plugin-gen:npm run typecheck,npm test(115 pass, including the skill description length test),npm run check(140 generated files match the catalog), the same as theHarness pluginsCI job.🤖 Generated with Claude Code