T-BGPJ-wizard-direct-kind-flows

State: planning/proposed · Impact: medium · Complexity: small

Goal

Every fast path into the wizard already knows the kind, marketplace and plugin it wants — the tree’s + menu, Home’s “Add plugin” and “Create your marketplace”, and a plugin page’s “Add skill” — yet the wizard still opens on the What step and makes the author re-enter the name and description before it will move. This task makes a seeded kind skip straight to placement, so a fast path is actually fast.

Today

Location	Role today
solutions/determined/experiences/agent-pants/app/utils/wizardSeed.ts#seedFromQuery	Round-trips kind/marketplace/plugin through the URL query; carries no step
solutions/determined/experiences/agent-pants/app/components/ApNewComponentWizard.vue#applySeed	Sets kind, marketplace and plugin from a seed but never touches step; the wizard always opens at step.value === 0 (‘What’)
solutions/determined/experiences/agent-pants/app/components/ApNewComponentWizard.vue#COMPONENT_STEPS	['What', 'Where', 'Details', 'Body', 'Review']; PLUGIN_STEPS and MARKETPLACE_STEPS both also start with ‘What’
solutions/determined/experiences/agent-pants/app/components/ApComponentTree.vue#newHere	The tree’s + menu; builds a seed via plusSeed and navigates with seedUrl(seed)
solutions/determined/experiences/agent-pants/app/pages/apps/agent-pants/index.vue#addPlugin	Home’s “Add plugin” button; seeds { kind: 'plugin', marketplace }
solutions/determined/experiences/agent-pants/app/pages/apps/agent-pants/index.vue#createMarketplace	The empty-vault “Create your marketplace” button; seeds { kind: 'marketplace' }
solutions/determined/experiences/agent-pants/app/pages/apps/agent-pants/plugins/[...path].vue	”Add skill” and “Choose kind to add” seed { kind, marketplace, plugin } for a plugin’s own members
solutions/determined/experiences/agent-pants/app/plugins/register.ts#contributes.commands	agent-pants.new opens the wizard with { new: '1' } and no kind — the one path that should stay on What
solutions/determined/products/agent-pants/tests/e2e/walkthrough.e2e.ts	”Add plugin opens the wizard seeded…” and “Add skill opens the wizard seeded…” both fill the What step’s name/description and click Next before asserting the Where step

Proposed

A seed naming a kind moves step.value past ‘What’ the moment applySeed applies it — to ‘Where’ for a leaf kind or a plugin, to ‘Identity’ for a marketplace — so the wizard opens already on placement. The generic New command, which seeds nothing, still opens on What. Reopening with no seed (reset()) still starts at step.value = 0.

Approach

1. In applySeed, once kind.value is set from a defined seed.kind, set step.value to the index right after ‘What’ in the now-current steps list — 1, since every steps array starts with ‘What’. Do this inside applySeed itself so both applyOrGuess call sites (the tree’s first arrival, and a later seed change) pick it up.
2. Leave reset() unchanged — it already zeroes step.value, so the unseeded New command keeps opening on What.
3. Confirm the existing watch(steps, ...) clamp still holds: switching kind from the What step (reachable only via Back) can shorten the list under a step.value that now starts at 1, and the clamp already handles that case.
4. Update the two Playwright tests that fill the What step before asserting Where: drop the name/description fill and the Next click for a seeded open, and assert the dialog opens directly on “Where does it live?” (or the Identity heading for a marketplace seed).
5. Add one assertion that the unseeded agent-pants.new command still opens on What.

Areas

Area	Note
solutions/determined/experiences/agent-pants/app/components/ApNewComponentWizard.vue	applySeed advances step past What when a kind is seeded
solutions/determined/products/agent-pants/tests/e2e/walkthrough.e2e.ts	Update the two seeded-open tests; add an unseeded-open assertion

Acceptance criteria

• AC-1: Opening the wizard from the tree’s + menu, “Add plugin”, “Create your marketplace”, or a plugin page’s “Add skill”/“Choose kind to add” lands on the Where (or Identity) step with no extra click.
• AC-2: Opening the wizard from the palette’s “Agent Pants: new component” command (no seed) still lands on What.
• AC-3: Switching kind from What via Back still works, and a container choice that shortens the step list never leaves step.value out of range.
• AC-4: The updated Playwright walkthrough spec passes.

Out of scope

• The What step’s own card layout or kind list — the tree’s own kind affordances are T-0XMP-tree-typed-folders-filter-add, not this task.
• Seeding anything beyond kind/marketplace/plugin (e.g. a prefilled name); wizardSeed.ts keeps its current three-field shape.

Dependencies

• none

Discovery context

From the user’s planning request of 2026-09-07: “creating a kind opens the wizard on that kind’s flow.” The assessment solutions/agent-pants/docs/vault/design/workflow-and-ux-assessment.md documents several fast paths (tree +, Add plugin, Add skill) that already narrow the seed to a kind; this task is the one step none of them take yet.

---

← Back to Tasks