diff --git a/.changes/prototype/fix-prototype-pressure-test-vendor-fit-trigger-9c463248.md b/.changes/prototype/fix-prototype-pressure-test-vendor-fit-trigger-9c463248.md new file mode 100644 index 00000000000..373e57c78a0 --- /dev/null +++ b/.changes/prototype/fix-prototype-pressure-test-vendor-fit-trigger-9c463248.md @@ -0,0 +1,10 @@ +--- +bump: patch +--- + +### Fixed + +- `/prototype:pressure-test` no longer claims a request to settle domain types and an internal + service contract: its vendor-fit trigger now reads 'does this third-party API do X for us', so + the generic word "service" no longer pulls design work into the prototype skill. Invocation + probes cover vendor-fit questions and a vendor price comparison that should not trigger. diff --git a/plugins/prototype/probes/pressure-test.json b/plugins/prototype/probes/pressure-test.json index 08b08ba57b0..39321ec70fc 100644 --- a/plugins/prototype/probes/pressure-test.json +++ b/plugins/prototype/probes/pressure-test.json @@ -38,6 +38,12 @@ "expect_trigger": true, "request": "Before we lock the public interface for the scheduler, I want to play with a draft of the calls, by job id or by name, in a scratch harness." }, + { + "id": "pos-train-06", + "split": "train", + "expect_trigger": true, + "request": "Can Stripe actually refund part of a captured payment and then tell us by webhook when it settles? I want to prove that in their test mode before we design around it." + }, { "id": "pos-val-01", "split": "validation", @@ -68,6 +74,12 @@ "expect_trigger": true, "request": "I want to try our draft refund policy against strange orderings of events interactively before anyone writes production code." }, + { + "id": "pos-val-06", + "split": "validation", + "expect_trigger": true, + "request": "We're counting on the shipping carrier's API to hand back a tracking number the moment a label is bought. Check that it really does, using their sandbox, before we commit to them." + }, { "id": "neg-train-01", "split": "train", @@ -98,6 +110,12 @@ "expect_trigger": false, "request": "Draw an ERD of our tables from the Prisma schema so I can see which entities relate to which." }, + { + "id": "neg-train-06", + "split": "train", + "expect_trigger": false, + "request": "Research the email delivery providers Postmark and SendGrid and recommend one for us based on their pricing tiers and support plans." + }, { "id": "neg-val-01", "split": "validation", @@ -127,6 +145,12 @@ "split": "validation", "expect_trigger": false, "request": "Settle the domain types for loyalty points (balances, accruals, expiries) and the contract the checkout service will call, so I can plan the work." + }, + { + "id": "neg-val-06", + "split": "validation", + "expect_trigger": false, + "request": "Compare Twilio and MessageBird on per-message price for US texts and tell us which SMS vendor is cheaper." } ] } diff --git a/plugins/prototype/skills/pressure-test/SKILL.md b/plugins/prototype/skills/pressure-test/SKILL.md index 5bcacc63af7..cd694ad3d40 100644 --- a/plugins/prototype/skills/pressure-test/SKILL.md +++ b/plugins/prototype/skills/pressure-test/SKILL.md @@ -1,5 +1,5 @@ --- -description: "Builds a throwaway interactive terminal app to pressure-test business logic, a state machine, a data model, or an API surface before committing to it. Use when nobody can say yet what the rules do with an awkward sequence of events or an odd record: 'what happens if a refund arrives after the order ships', 'is this transition allowed from that status', 'will this schema fit our odd records', 'which arguments should this call take', 'prototype this reducer', 'does this outside service do X for us' (vendor-fit: an adapter checks it against the vendor's sandbox). A pure logic module, liftable into production, sits behind a disposable shell: the terminal app, or a self-contained click-through HTML demo for someone outside engineering. Records the validated answer in a durable note. Visual or design questions: /prototype:explore-directions." +description: "Builds a throwaway interactive terminal app to pressure-test business logic, a state machine, a data model, or an API surface before committing to it. Use when nobody can say yet what the rules do with an awkward sequence of events or an odd record: 'what happens if a refund arrives after the order ships', 'is this transition allowed from that status', 'will this schema fit our odd records', 'which arguments should this call take', 'prototype this reducer', 'does this third-party API do X for us' (vendor-fit mode: an adapter checks it against a sandbox). A pure logic module, liftable into production, sits behind a disposable shell: the terminal app, or a self-contained click-through HTML demo for someone outside engineering. Records the validated answer in a durable note. Visual or design questions: /prototype:explore-directions." argument-hint: "[observe|vendor-fit] [--medium ] [scope]" user-invocable: true disable-model-invocation: false