diff --git a/.changes/planning/feat-wayfind-data-sharing-item-5b1e7d24.md b/.changes/planning/feat-wayfind-data-sharing-item-5b1e7d24.md new file mode 100644 index 00000000000..538d647f817 --- /dev/null +++ b/.changes/planning/feat-wayfind-data-sharing-item-5b1e7d24.md @@ -0,0 +1,12 @@ +--- +bump: minor +--- + +### Added + +- `/planning:wayfind` charts one data-sharing interview item when a decision selects an outside + service that will receive user data: which fields cross, under what agreement, and, in a + regulated repository, what must be in place before build (for example a business associate + agreement). Its resolution feeds the PRD. A service that receives no user data gets no item. +- A `wayfind: prototype` item that proves an outside vendor does something routes to + `/prototype:pressure-test` in its vendor-fit mode. diff --git a/plugins/planning/evals/wayfind-prototype-files-on-dossier-folder-and-safe-push/graders/vendor-fit-route.md b/plugins/planning/evals/wayfind-prototype-files-on-dossier-folder-and-safe-push/graders/vendor-fit-route.md new file mode 100644 index 00000000000..575c9f01767 --- /dev/null +++ b/plugins/planning/evals/wayfind-prototype-files-on-dossier-folder-and-safe-push/graders/vendor-fit-route.md @@ -0,0 +1,9 @@ +--- +type: llm +--- + +On map #500, the claimed prototype item #504 'Prove Knock sends email and in-app from one call' passed all its checks. Another session is writing research findings to the same map's dossier branch right now. The user asked to save the prototype files and close the item. The sandbox has no tracker, so the reply writes out each tracker action it would take (create, claim, comment, edit, close) instead of performing it, and names any skill call it would make instead of making it. Judge written-out actions and named calls as taken. + +PASS if the reply names `/prototype:pressure-test` in a mode for checking that an outside vendor fits (vendor-fit, or a close variant of that name) as the skill that proved the Knock behavior. The exact flag spelling does not matter. + +FAIL if the reply names no such mode, or names a skill other than `/prototype:pressure-test`. diff --git a/plugins/planning/evals/wayfind-prototype-files-on-dossier-folder-and-safe-push/prompt.md b/plugins/planning/evals/wayfind-prototype-files-on-dossier-folder-and-safe-push/prompt.md index 20794e6c7d6..e1aed31b113 100644 --- a/plugins/planning/evals/wayfind-prototype-files-on-dossier-folder-and-safe-push/prompt.md +++ b/plugins/planning/evals/wayfind-prototype-files-on-dossier-folder-and-safe-push/prompt.md @@ -5,7 +5,7 @@ runs: 3 max_turns: 30 timeout_seconds: 900 allowed_tools: [Read, Glob, Grep, Skill, Bash] -expected_outcome: "The prototype's files go in #504's own folder on the map's single dossier branch. The push is fetch, rebase, then a plain push without force, retried after a fresh fetch and rebase if rejected; it needs no force because the other session writes only its own item's folder. The verdict (each pass check passed) goes in the resolution comment with a link to the folder; then the pointer is added and the item closed." +expected_outcome: "The item proves an outside vendor does something, so its route is /prototype:pressure-test in its vendor-fit mode. The prototype's files go in #504's own folder on the map's single dossier branch. The push is fetch, rebase, then a plain push without force, retried after a fresh fetch and rebase if rejected; it needs no force because the other session writes only its own item's folder. The verdict (each pass check passed) goes in the resolution comment with a link to the folder; then the pointer is added and the item closed." --- /planning:wayfind work 'Map: notification vendor' (#500). The claimed prototype item 'Prove Knock sends email and in-app from one call' (#504) is done: the pressure-test passed all checks. Another session is writing research findings to the same map's dossier branch right now. Save the prototype files and close the item. diff --git a/plugins/planning/evals/wayfind-prototype-files-on-dossier-folder-and-safe-push/samples/vendor-fit-route.json b/plugins/planning/evals/wayfind-prototype-files-on-dossier-folder-and-safe-push/samples/vendor-fit-route.json new file mode 100644 index 00000000000..3856549a96f --- /dev/null +++ b/plugins/planning/evals/wayfind-prototype-files-on-dossier-folder-and-safe-push/samples/vendor-fit-route.json @@ -0,0 +1,22 @@ +{ + "pass": [ + { + "answer": "Resolution: /prototype:pressure-test vendor-fit run; every check passed.", + "why": "names the skill and its vendor-fit mode" + }, + { + "answer": "Resolution: proved with /prototype:pressure-test --vendor-fitness; all checks passed.", + "why": "a close variant of the mode name still counts" + } + ], + "fail": [ + { + "answer": "Resolution: /prototype:pressure-test passed every check.", + "why": "names no vendor-fit mode" + }, + { + "answer": "Resolution: /prototype:explore-directions vendor-fit passed.", + "why": "names the wrong skill" + } + ] +} diff --git a/plugins/planning/skills/wayfind/SKILL.md b/plugins/planning/skills/wayfind/SKILL.md index d38f484965a..d650bdf5e89 100644 --- a/plugins/planning/skills/wayfind/SKILL.md +++ b/plugins/planning/skills/wayfind/SKILL.md @@ -237,7 +237,9 @@ that charting needs an interactive session. Do not fabricate a map. ([`context/map-anatomy.md`](context/map-anatomy.md) "Prototype item body"). The type label sets the routing target (the type table in work step 5). Then, in a second pass once every item has its real id, wire `blocked-by` edges and write any cross-reference between items. Wire an edge - only where one decision genuinely gates another; never invent edges to impose order. + only where one decision genuinely gates another; never invent edges to impose order. A settled + answer that already selects an outside service receiving user data gets its data-sharing item + here (work step 6). 5. **Materialize the mode** on each item at creation: `` only for an intent or vision question ("Readiness" above), whatever the type. The label's presence or absence is the only mode mechanism; no `Mode:` body field. @@ -290,7 +292,7 @@ that charting needs an interactive session. Do not fabricate a map. | ` research` | agent-capable | `/discovery:research` (falls back to inline research if not enabled) | | ` interview` | `` (intent) | `/planning:interview` | | ` design` | agent-capable unless it asks for vision | `/planning:design`, or `/event-storming:methodology` / `/event-storming:simulation` when the item is domain/event-model work | - | ` prototype` | `` when the user judges it | `/prototype:pressure-test` (behaviour/feasibility) or `/prototype:explore-directions` (design/UX). The item body says which. Its files go in the item's folder on the dossier branch ("Shared files"); its verdict goes in the resolution comment | + | ` prototype` | `` when the user judges it | `/prototype:pressure-test` (behaviour/feasibility; its vendor-fit mode when the item proves an outside vendor does something) or `/prototype:explore-directions` (design/UX). The item body says which. Its files go in the item's folder on the dossier branch ("Shared files"); its verdict goes in the resolution comment | | ` task` | per item | Direct decision-unblocking work. No feature code, no PR tie. Its resolution records what was done and the facts later items need. Work only a human can do (a vendor sign-up, credentials, a dashboard) routes to `/wizard:generate`; its resolution records the names and locations of what was set up, never the values | 6. **Graduate on every resolution.** Every edit to the map body, here or anywhere in this skill, @@ -308,6 +310,12 @@ that charting needs an interactive session. Do not fabricate a map. Decisions-so-far pointer. Fog stays in Not-yet-specified and never moves into Out-of-scope for being unphrasable, only by an explicit scope ruling at closure (step 8). If the resolution sharpened previously-foggy uncertainty, chart the new sharp items now (create, then wire, as chart step 4) and delete that bullet from Not-yet-specified. + **Data-sharing item.** When the resolution selects an outside service that will receive user + data, chart one `interview` item for that service: which fields cross to it, under what + agreement, and, in a regulated repository, what must be in place before build (for example + whether a business associate agreement is needed). One item per selected service, its questions + grouped inside it; none when no user data crosses. Its resolution feeds the PRD through the + closing comment (step 8). Mode follows "Readiness". 7. **Sweep the map after every resolution.** Reread the open items and closed decisions against what was just decided: - An open item whose premise the resolution invalidated: rewrite its question if one still diff --git a/plugins/planning/skills/wayfind/evals/evals.json b/plugins/planning/skills/wayfind/evals/evals.json index abe7bfd2835..6cc678c9e81 100644 --- a/plugins/planning/skills/wayfind/evals/evals.json +++ b/plugins/planning/skills/wayfind/evals/evals.json @@ -338,13 +338,14 @@ "id": 28, "name": "prototype-files-on-dossier-folder-and-safe-push", "prompt": "/planning:wayfind work 'Map: notification vendor' (#500). The claimed prototype item 'Prove Knock sends email and in-app from one call' (#504) is done: the pressure-test passed all checks. Another session is writing research findings to the same map's dossier branch right now. Save the prototype files and close the item.", - "expected_output": "The prototype's files go in #504's own folder on the map's single dossier branch. The push is fetch, rebase, then a plain push without force, retried after a fresh fetch and rebase if rejected; it needs no force because the other session writes only its own item's folder. The verdict (each pass check passed) goes in the resolution comment with a link to the folder; then the pointer is added and the item closed.", + "expected_output": "The item proves an outside vendor does something, so its route is /prototype:pressure-test in its vendor-fit mode. The prototype's files go in #504's own folder on the map's single dossier branch. The push is fetch, rebase, then a plain push without force, retried after a fresh fetch and rebase if rejected; it needs no force because the other session writes only its own item's folder. The verdict (each pass check passed) goes in the resolution comment with a link to the folder; then the pointer is added and the item closed.", "files": [], "expectations": [ "Output puts the prototype files in the item's own folder on the map's dossier branch, not a new branch per item", "Output pushes with fetch, rebase and a plain non-force push, retrying on rejection", "Output does not force-push", - "The resolution comment carries the prototype's verdict" + "The resolution comment carries the prototype's verdict", + "Output names /prototype:pressure-test, in a mode for checking that an outside vendor fits (vendor-fit or a close variant of that name), as the skill that proved the Knock behavior" ] }, { @@ -395,6 +396,20 @@ "Output does not route the item to /prototype:pressure-test", "Output does not route the item to /planning:design" ] + }, + { + "id": 33, + "name": "selected-service-receiving-user-data-gets-one-data-sharing-item", + "prompt": "/planning:wayfind work 'Map: clinic intake' (#700). Destination: a PRD. The repository holds regulated health software. The claimed item 'Choose the intake vendors' (#702, wayfind: interview) just resolved: Formly will host the patient intake form and receive each patient's name, date of birth and symptoms; Statusly will host the public status page and receive no user data. Finish the item.", + "expected_output": "After graduating #702, work charts one interview item for Formly, the selected service that receives user data, covering which fields cross to it (name, date of birth, symptoms), under what agreement, and, since the repository is regulated, whether a business associate agreement is needed before build. It is one item holding those questions, not one item per question, and its resolution feeds the PRD. Statusly receives no user data, so it gets no such item.", + "files": [], + "expectations": [ + "Output charts one data-sharing interview item for Formly", + "Output charts no data-sharing item for Statusly", + "The Formly item covers which fields cross, under what agreement, and whether a business associate agreement (or the regulated repository's equivalent) is needed before build", + "Output creates one item for those questions, not a separate item per question", + "Output says the item's resolution feeds the PRD" + ] } ] }